CVE-2022-50096: x86/kprobes: Update kcb status flag after singlestepping
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1cbf3882cb372bbe752efd7c3045ca1c9ab40ac6, 663cdda2716b70751df9c7e60b81bd0850fdfe3c, b9c3401f7cac6ae291a16784dadcd1bf116218fe.
Low priority for now. Upgrade to Linux Linux 1cbf3882cb372bbe752efd7c3045ca1c9ab40ac6, 663cdda2716b70751df9c7e60b81bd0850fdfe3c, b9c3401f7cac6ae291a16784dadcd1bf116218fe or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.13 and later · before 5.15.61
- linux linux kernel5.16 and later · before 5.18.18
- linux linux kernel5.19 and later · before 5.19.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.13affected
- ba7d1dae9fe866abe74bb1e849fb85983b7c4c37 and later · before edc2ac7c7265b33660fa0190898966b49966b855affected · git
- 6256e668b7af9d81472e03c6a171630c08f8858a and later · before 1cbf3882cb372bbe752efd7c3045ca1c9ab40ac6affected · git
- 6256e668b7af9d81472e03c6a171630c08f8858a and later · before b9c3401f7cac6ae291a16784dadcd1bf116218feaffected · git
- 6256e668b7af9d81472e03c6a171630c08f8858a and later · before 663cdda2716b70751df9c7e60b81bd0850fdfe3caffected · git
- 6256e668b7af9d81472e03c6a171630c08f8858a and later · before dec8784c9088b131a1523f582c2194cfc8107dc0affected · git
- before 5.13not affected · semver
- 5.15.61 and later · up to and including 5.15.*not affected · semver
- 5.18.18 and later · up to and including 5.18.*not affected · semver
- 5.19.2 and later · up to and including 5.19.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.0.2-1 | 6.0.2-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-50094Jun 18, 2025 · spmi: trace: fix stack-out-of-bound access in SPMI tracing functions28Monitor
- ← EarlierCVE-2022-50095Jun 18, 2025 · posix-cpu-timers: Cleanup CPU timers before freeing them during exec31Monitor
- Later →CVE-2022-50097Jun 18, 2025 · video: fbdev: s3fb: Check the size of screen before memset_io()31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1cbf3882cb372bbe752efd7c3045ca1c9ab40ac6 | Vendor (CNA) |
| Linux Linux | 663cdda2716b70751df9c7e60b81bd0850fdfe3c | Vendor (CNA) |
| Linux Linux | b9c3401f7cac6ae291a16784dadcd1bf116218fe | Vendor (CNA) |
| Linux Linux | dec8784c9088b131a1523f582c2194cfc8107dc0 | Vendor (CNA) |
| Linux Linux | edc2ac7c7265b33660fa0190898966b49966b855 | Vendor (CNA) |
| debian:linux | 6.0.2-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.