Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-42096: x86: stop playing stack games in profile_pc()

MediumCVSS 5.5 · v3.1—No exploit Fix available

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.23% (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 093d9603b60093a9aaae942db56107f6432a5dca, 161cef818545ecf980f0e2ebaf8ba7326ce53c2b, 16222beb9f8e5ceb0beeb5cbe54bef16df501a92.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 093d9603b60093a9aaae942db56107f6432a5dca, 161cef818545ecf980f0e2ebaf8ba7326ce53c2b, 16222beb9f8e5ceb0beeb5cbe54bef16df501a92 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: stop playing stack games in profile_pc() The 'profile_pc()' function is used for timer-based profiling, which isn't really all that relevant any more to begin with, but it also ends up making assumptions based on the stack layout that aren't necessarily valid. Basically, the code tries to account the time spent in spinlocks to the caller rather than the spinlock, and while I support that as a concept, it's not worth the code complexity or the KASAN warnings when no serious profiling is done using timers anyway these days. And the code really does depend on stack layout that is only true in the simplest of cases. We've lost the comment at some point (I think when the 32-bit and 64-bit code was unified), but it used to say: Assume the lock function has either no stack frame or a copy of eflags from PUSHF. which explains why it just blindly loads a word or two straight off the stack pointer and then takes a minimal look at the values to just check if they might be eflags or the return pc: Eflags always has bits 22 and up cleared unlike kernel addresses but that basic stack layout assumption assumes that there isn't any lock debugging etc going on that would complicate the code and cause a stack frame. It causes KASAN unhappiness reported for years by syzkaller [1] and others [2]. With no real practical reason for this any more, just remove the code. Just for historical interest, here's some background commits relating to this code from 2006: 0cb91a229364 ("i386: Account spinlocks to the caller during profiling for !FP kernels") 31679f38d886 ("Simplify profile_pc on x86-64") and a code unification from 2009: ef4512882dbe ("x86: time_32/64.c unify profile_pc") but the basics of this thing actually goes back to before the git tree.

Published
Jul 29, 2024
Updated
Oct 15, 2026
EPSS
0.2% · 14th percentile

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-42096

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

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

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 65ebdde16e7f5da99dbf8a548fb635837d78384eaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 27c3be840911b15a3f24ed623f86153c825b6b29affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 49c09ca35a5f521d7fa18caf62fdf378f15e8aa4affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2d07fea561d64357fb7b3f3751e653bf20306d77affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 161cef818545ecf980f0e2ebaf8ba7326ce53c2baffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 16222beb9f8e5ceb0beeb5cbe54bef16df501a92affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a3b65c8cbc139bfce9541bc81c1bb766e5ba3f68affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 093d9603b60093a9aaae942db56107f6432a5dcaaffected · git
    • before 2.6.12not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.98-16.1.98-1
Debian:13linuxbefore 6.9.8-16.9.8-1

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-42093Jul 29, 2024 · net/dpaa2: Avoid explicit cpumask var allocation on stack
    29Monitor
  • ← EarlierCVE-2024-42094Jul 29, 2024 · net/iucv: Avoid explicit cpumask var allocation on stack
    28Monitor
  • Later →CVE-2024-42097Jul 29, 2024 · ALSA: emux: improve patch ioctl data validation
    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 Linux093d9603b60093a9aaae942db56107f6432a5dcaVendor (CNA)
Linux Linux161cef818545ecf980f0e2ebaf8ba7326ce53c2bVendor (CNA)
Linux Linux16222beb9f8e5ceb0beeb5cbe54bef16df501a92Vendor (CNA)
Linux Linux27c3be840911b15a3f24ed623f86153c825b6b29Vendor (CNA)
Linux Linux2d07fea561d64357fb7b3f3751e653bf20306d77Vendor (CNA)
Linux Linux49c09ca35a5f521d7fa18caf62fdf378f15e8aa4Vendor (CNA)
Linux Linux65ebdde16e7f5da99dbf8a548fb635837d78384eVendor (CNA)
Linux Linuxa3b65c8cbc139bfce9541bc81c1bb766e5ba3f68Vendor (CNA)
debian:linux6.1.98-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.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-50302113 days apartHID: core: zero-initialize the report bufferKEV
    52Plan
  • CVE-2024-4768584 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()
    36Monitor
  • CVE-2024-3689860 days apartgpiolib: cdev: fix uninitialised kfifo
    31Monitor
  • CVE-2021-4755366 days apartsched/scs: Reset task stack state in bringup_cpu()
    31Monitor
  • CVE-2024-2702289 days apartfork: defer linking file vma until vma is fully initialized
    31Monitor
  • CVE-2024-50143101 days apartudf: fix uninit-value use in udf_get_fileshortad
    31Monitor

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

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

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.

References

All records