x86/kprobes: Update kcb status flag after singlestepping
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's x86/kprobes code may fail to update its status after single-stepping when a post-handler is not set. If another INT3 user runs immediately afterward, the kernel may panic. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with x86/kprobes should check their installations; affected versions are not specified.