CVE-2024-50193: x86/entry_32: Clear CPU buffers after register restore in NMI return
Noroxi assessment
Priority: Monitor (action score 28/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.21% (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 227358e89703c344008119be7e8ffa3fdb5b92de, 43778de19d2ef129636815274644b9c16e78c66b, 48a2440d0f20c826b884e04377ccc1e4696c84e9; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.
Low priority for now. Upgrade to Linux Linux 227358e89703c344008119be7e8ffa3fdb5b92de, 43778de19d2ef129636815274644b9c16e78c66b, 48a2440d0f20c826b884e04377ccc1e4696c84e9; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1 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/entry_32: Clear CPU buffers after register restore in NMI return CPU buffers are currently cleared after call to exc_nmi, but before register state is restored. This may be okay for MDS mitigation but not for RDFS. Because RDFS mitigation requires CPU buffers to be cleared when registers don't have any sensitive data. Move CLEAR_CPU_BUFFERS after RESTORE_ALL_NMI.
- Published
- Nov 8, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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 kernelbefore 5.10.228
- linux linux kernel5.11 and later · before 5.15.169
- linux linux kernel5.16 and later · before 6.1.114
- linux linux kernel6.2 and later · before 6.6.58
- linux linux kernel6.8 and later · before 6.11.5
- linux linux kernel6.12
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
- 51eca9f1fd047b500137d021f882d93f03280118, 6.8affected
- 50f021f0b985629accf10481a6e89af8b9700583 and later · before 6f44a5fc15b5cece0785bc07453db77d99b0a6deaffected · git
- d54de9f2a127090f2017184e8257795b487d5312 and later · before b6400eb0b347821efc57760221f8fb6d63b9548aaffected · git
- 2e3087505ddb8ba2d3d4c81306cca11e868fcdb9 and later · before 43778de19d2ef129636815274644b9c16e78c66baffected · git
- ca13d8cd8dac25558da4ee8df4dc70e8e7f9d762 and later · before 227358e89703c344008119be7e8ffa3fdb5b92deaffected · git
- a0e2dab44d22b913b4c228c8b52b2a104434b0b3 and later · before 64adf22c4bc73ede920baca5defefb70f190cdbcaffected · git
- a0e2dab44d22b913b4c228c8b52b2a104434b0b3 and later · before 48a2440d0f20c826b884e04377ccc1e4696c84e9affected · git
- 5.10.215 and later · before 5.10.228affected · semver
- 5.15.154 and later · before 5.15.169affected · semver
- 6.1.81 and later · before 6.1.114affected · 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.1.115-1 | 6.1.115-1 |
| Debian:13 | linux | before 6.11.5-1 | 6.11.5-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-2024-50191Nov 8, 2024 · ext4: don't set SB_RDONLY after filesystem errors22Monitor
- ← EarlierCVE-2024-50192Nov 8, 2024 · irqchip/gic-v4: Don't allow a VMOVP on a dying VPE18Monitor
- Later →CVE-2024-50194Nov 8, 2024 · arm64: probes: Fix uprobes for big-endian kernels22Monitor
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 | 227358e89703c344008119be7e8ffa3fdb5b92de | Vendor (CNA) |
| Linux Linux | 43778de19d2ef129636815274644b9c16e78c66b | Vendor (CNA) |
| Linux Linux | 48a2440d0f20c826b884e04377ccc1e4696c84e9 | Vendor (CNA) |
| Linux Linux | 5.10.228 | Vendor (CNA) |
| Linux Linux | 5.15.169 | Vendor (CNA) |
| Linux Linux | 6.1.114 | Vendor (CNA) |
| Linux Linux | 6.6.58 | Vendor (CNA) |
| Linux Linux | 6.8 | Vendor (CNA) |
| Linux Linux | 64adf22c4bc73ede920baca5defefb70f190cdbc | Vendor (CNA) |
| Linux Linux | 6f44a5fc15b5cece0785bc07453db77d99b0a6de | Vendor (CNA) |
| Linux Linux | b6400eb0b347821efc57760221f8fb6d63b9548a | Vendor (CNA) |
| azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 | 6.6.64.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 | 6.6.64.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.115-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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
- high · data can be read
- 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
- High
- 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:H/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 (7 more)Show less
- git.kernel.org/stable/c/43778de19d2ef129636815274644b9c16e78c66b
- git.kernel.org/stable/c/48a2440d0f20c826b884e04377ccc1e4696c84e9
- git.kernel.org/stable/c/64adf22c4bc73ede920baca5defefb70f190cdbc
- git.kernel.org/stable/c/6f44a5fc15b5cece0785bc07453db77d99b0a6de
- git.kernel.org/stable/c/b6400eb0b347821efc57760221f8fb6d63b9548a
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.