CVE-2022-50096: x86/kprobes: Update kcb status flag after singlestepping
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.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can turn a specific internal debugging/probing state mistake into a kernel panic. The practical business impact is availability: affected systems may crash under the right kernel instrumentation conditions. The provided sources do not report data theft, privilege escalation, or active exploitation.
Executive priority
Treat this as an availability risk, not a confirmed compromise signal. Patch during normal kernel maintenance, accelerating for critical systems that use kernel tracing or observability features. Evidence is insufficient to justify emergency response on exploitation grounds.
Technical view
On x86, kprobes failed to set the kprobes control block status to KPROBE_HIT_SSDONE after single-stepping when no post_handler existed. A later INT3 user could then be misclassified by kprobe_int3_handler as kprobe single-step handling, potentially causing a kernel panic.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel builds with x86 kprobes or other INT3 users. The CVE metadata lists Linux kernel versions and stable commit references, but distro-specific package status is not included.
Exploitation context
The source bundle says this may cause a kernel panic. It does not provide evidence of active exploitation, public exploit use, remote reachability, or attacker prerequisites. CISA KEV status is false in the supplied data.
Researcher notes
The key flaw is incorrect kcb status progression after single-stepping without a post_handler. Validation should focus on kernel version lineage and presence of the stable patches, not exploit reproduction. The supplied record lacks CVSS, CWE, and distro package mappings.
Mitigation direction
Review the linked Linux stable commits and vendor kernel advisories.
Update affected Linux kernels through the distribution's supported package channel.
Prioritize systems using kprobes, tracing, observability, or kernel instrumentation.
Monitor crash reports for kernel panics involving kprobes or INT3 handling.
Validation and detection
Inventory Linux kernel versions and map them to vendor advisories.
Check whether running kernels include the referenced stable fixes.
Identify hosts using x86 kprobes, tracing, or related instrumentation.
Review kernel panic logs for kprobe_int3_handler or INT3-related traces.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-50096 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
6Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:02 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.