Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-35996: cpu: Re-enable CPU mitigations by default for !X86 architectures

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 36b32816fbab267611f073223f1b0b816ec5920f, 38f17d1fbb5bfb56ca1419e2d06376d57a9396f9, 5.15.158.

Low priority for now. Upgrade to Linux Linux 36b32816fbab267611f073223f1b0b816ec5920f, 38f17d1fbb5bfb56ca1419e2d06376d57a9396f9, 5.15.158 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: cpu: Re-enable CPU mitigations by default for !X86 architectures Rename x86's to CPU_MITIGATIONS, define it in generic code, and force it on for all architectures exception x86. A recent commit to turn mitigations off by default if SPECULATION_MITIGATIONS=n kinda sorta missed that "cpu_mitigations" is completely generic, whereas SPECULATION_MITIGATIONS is x86-specific. Rename x86's SPECULATIVE_MITIGATIONS instead of keeping both and have it select CPU_MITIGATIONS, as having two configs for the same thing is unnecessary and confusing. This will also allow x86 to use the knob to manage mitigations that aren't strictly related to speculative execution. Use another Kconfig to communicate to common code that CPU_MITIGATIONS is already defined instead of having x86's menu depend on the common CPU_MITIGATIONS. This allows keeping a single point of contact for all of x86's mitigations, and it's not clear that other architectures *want* to allow disabling mitigations at compile-time.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 20, 2024
Updated
Oct 15, 2026
EPSS
0.2% · 15th percentile
CWE
—

Report tools

JSON

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%

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.

Follow CVE-2024-35996

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel5.15.156 and later · before 5.15.158
  • linux linux kernel6.1.87 and later · before 6.1.90
  • linux linux kernel6.6.28 and later · before 6.6.30
  • linux linux kernel6.8.7 and later · before 6.8.9
  • linux linux kernel6.9

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

    • 30da4180fd768973189dc364648f9c436e57b01d and later · before af6d6a923b40bf6471e44067ac61cc5814b48e7faffected · git
    • 70688450dddaf91e12fd4fc625da3297025932c9 and later · before 36b32816fbab267611f073223f1b0b816ec5920faffected · git
    • 9c09773917fbb77dff85b433e1e89123fc5fb530 and later · before 38f17d1fbb5bfb56ca1419e2d06376d57a9396f9affected · git
    • 2978ee7c973ce81b6e51100ba1e5ae001af624b9 and later · before 8292f4f8dd1b005d0688d726261004f816ef730aaffected · git
    • c4a9babdd5d5a41a74269a2e1aa1647b1b4c45bb and later · before fd8547ebc187037cc69441a15c1441aeaab80f49affected · git
    • f337a6a21e2fd67eadea471e93d05dd37baaa9be and later · before fe42754b94a42d08cf9501790afc25c4f6a5f631affected · git
    • 5.15.156 and later · before 5.15.158affected · semver
    • 6.1.87 and later · before 6.1.90affected · semver
    • 6.6.28 and later · before 6.6.30affected · semver
    • 6.8.7 and later · before 6.8.9affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.90-16.1.90-1
Debian:13linuxbefore 6.8.9-16.8.9-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-35988May 20, 2024 · riscv: Fix TASK_SIZE on 64-bit NOMMU
    22Monitor
  • ← EarlierCVE-2024-35990May 20, 2024 · dma: xilinx_dpdma: Fix locking
    22Monitor
  • Later →CVE-2024-35997May 20, 2024 · HID: i2c-hid: remove I2C_HID_READ_PENDING flag to prevent lock-up
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux36b32816fbab267611f073223f1b0b816ec5920fVendor (CNA)
Linux Linux38f17d1fbb5bfb56ca1419e2d06376d57a9396f9Vendor (CNA)
Linux Linux5.15.158Vendor (CNA)
Linux Linux6.1.90Vendor (CNA)
Linux Linux6.6.30Vendor (CNA)
Linux Linux6.8.9Vendor (CNA)
Linux Linux8292f4f8dd1b005d0688d726261004f816ef730aVendor (CNA)
Linux Linuxaf6d6a923b40bf6471e44067ac61cc5814b48e7fVendor (CNA)
Linux Linuxfd8547ebc187037cc69441a15c1441aeaab80f49Vendor (CNA)
Linux Linuxfe42754b94a42d08cf9501790afc25c4f6a5f631Vendor (CNA)
debian:linux6.1.90-1 · Debian:12Package 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 researchers

Finders, 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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records