In the Linux kernel, the following vulnerability has been resolved:
x86/kprobes: Update kcb status flag after singlestepping
Fix kprobes to update kcb (kprobes control block) status flag to
KPROBE_HIT_SSDONE even if the kp->post_handler is not set.
This bug may cause a kernel panic if another INT3 user runs right
after kprobes because kprobe_int3_handler() misunderstands the
INT3 is kprobe's single stepping INT3.
Metrics
Affected Vendors & Products
References
History
Fri, 20 Jun 2025 02:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Wed, 18 Jun 2025 11:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In the Linux kernel, the following vulnerability has been resolved: x86/kprobes: Update kcb status flag after singlestepping Fix kprobes to update kcb (kprobes control block) status flag to KPROBE_HIT_SSDONE even if the kp->post_handler is not set. This bug may cause a kernel panic if another INT3 user runs right after kprobes because kprobe_int3_handler() misunderstands the INT3 is kprobe's single stepping INT3. | |
| Title | x86/kprobes: Update kcb status flag after singlestepping | |
| References |
|
|
Status: PUBLISHED
Assigner: Linux
Published: 2025-06-18T11:02:33.958Z
Updated: 2025-06-18T11:02:33.958Z
Reserved: 2025-06-18T10:57:27.411Z
Link: CVE-2022-50096
No data.
Status : Awaiting Analysis
Published: 2025-06-18T11:15:38.850
Modified: 2025-06-18T13:47:40.833
Link: CVE-2022-50096