CVE-2022-50096 x86/kprobes: Update kcb status flag after singlestepping
A flaw in Linux kernel kprobes handling can cause a kernel panic when another INT3 user executes immediately after singlestepping.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-50096?
CVE-2022-50096 is a medium-severity denial of service vulnerability in Linux kernel, published on 18 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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.
Which versions are affected by CVE-2022-50096?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2022-50096?
Apply the vendor's patch.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2022-50096 being exploited?
There is no known exploitation of CVE-2022-50096 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as DEBIAN-CVE-2022-50096, GHSA-v2vw-5j5p-f93j, UBUNTU-CVE-2022-50096.