Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-57951: hrtimers: Handle CPU state correctly on hotplug

Noroxi assessment

Priority: Monitor (action score 31/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.26% (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 14984139f1f2768883332965db566ef26db609e7, 15b453db41d36184cf0ccc21e7df624014ab6a1a, 2f8dea1692eef2b7ba6a256246ed82c365fdc686; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1.

Low priority for now. Upgrade to Linux Linux 14984139f1f2768883332965db566ef26db609e7, 15b453db41d36184cf0ccc21e7df624014ab6a1a, 2f8dea1692eef2b7ba6a256246ed82c365fdc686; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-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: hrtimers: Handle CPU state correctly on hotplug Consider a scenario where a CPU transitions from CPUHP_ONLINE to halfway through a CPU hotunplug down to CPUHP_HRTIMERS_PREPARE, and then back to CPUHP_ONLINE: Since hrtimers_prepare_cpu() does not run, cpu_base.hres_active remains set to 1 throughout. However, during a CPU unplug operation, the tick and the clockevents are shut down at CPUHP_AP_TICK_DYING. On return to the online state, for instance CFS incorrectly assumes that the hrtick is already active, and the chance of the clockevent device to transition to oneshot mode is also lost forever for the CPU, unless it goes back to a lower state than CPUHP_HRTIMERS_PREPARE once. This round-trip reveals another issue; cpu_base.online is not set to 1 after the transition, which appears as a WARN_ON_ONCE in enqueue_hrtimer(). Aside of that, the bulk of the per CPU state is not reset either, which means there are dangling pointers in the worst case. Address this by adding a corresponding startup() callback, which resets the stale per CPU state and sets the online flag. [ tglx: Make the new callback unconditionally available, remove the online modification in the prepare() callback and clear the remaining state in the starting callback instead of the prepare callback ]

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Feb 12, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 18th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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

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

Running WordPress? Scan your site free with WP Lens

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

Running WordPress? Scan your site free with WP Lens

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

Affected versions

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

  • linux linux kernel4.19.302 and later · before 4.20
  • linux linux kernel5.4.264 and later · before 5.4.290
  • linux linux kernel5.10.204 and later · before 5.10.234
  • linux linux kernel5.15.143 and later · before 5.15.177
  • linux linux kernel6.1.68 and later · before 6.1.127
  • linux linux kernel6.6.7 and later · before 6.6.74
  • linux linux kernel6.7 and later · before 6.12.11
  • linux linux kernel6.13

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

    • 9a2fc41acb69dd4e2a58d0c04346c3333c2341fc, 6.7affected
    • 54d0d83a53508d687fd4a225f8aa1f18559562d0 and later · before 95e4f62df23f4df1ce6ef897d44b8e23c260921aaffected · git
    • 7f4c89400d2997939f6971c7981cc780a219e36b and later · before 14984139f1f2768883332965db566ef26db609e7affected · git
    • 6fcbcc6c8e52650749692c7613cbe71bf601670d and later · before 15b453db41d36184cf0ccc21e7df624014ab6a1aaffected · git
    • 75b5016ce325f1ef9c63e5398a1064cf8a7a7354 and later · before 3d41dbf82e10c44e53ea602398ab002baec27e75affected · git
    • 53f408cad05bb987af860af22f4151e5a18e6ee8 and later · before a5cbbea145b400e40540c34816d16d36e0374fbcaffected · git
    • 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 and later · before 38492f6ee883c7b1d33338bf531a62cff69b4b28affected · git
    • 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 and later · before 2f8dea1692eef2b7ba6a256246ed82c365fdc686affected · git
    • 5.4.264 and later · before 5.4.290affected · semver
    • 5.10.204 and later · before 5.10.234affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.128-16.1.128-1
Debian:13linuxbefore 6.12.11-16.12.11-1
openSUSE:Leap 16.0dtb-aarch64before 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-64kbbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-defaultbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-default-basebefore 6.12.0-160000.6.1.160000.2.46.12.0-160000.6.1.160000.2.4
openSUSE:Leap 16.0kernel-docsbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-kvmsmallbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-obs-buildbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-obs-qabefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-rtbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-sourcebefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-symsbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-zfcpdumpbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Enterprise Server 16.0kernel-docsbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Enterprise Server 16.0kernel-kvmsmallbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Enterprise Server 16.0kernel-obs-qabefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Enterprise Server 16.0kernel-symsbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Enterprise Server 16.0kernel-zfcpdumpbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Micro 6.2kernel-64kbbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Micro 6.2kernel-defaultbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Micro 6.2kernel-default-basebefore 6.12.0-160000.6.1.160000.2.46.12.0-160000.6.1.160000.2.4
SUSE:Linux Micro 6.2kernel-rtbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Micro 6.2kernel-sourcebefore 6.12.0-160000.6.16.12.0-160000.6.1

+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-2025-21697Feb 12, 2025 · drm/v3d: Ensure job pointer is set to NULL after job completion
    22Monitor
  • ← EarlierCVE-2025-21699Feb 12, 2025 · gfs2: Truncate address space when flipping GFS2_DIF_JDATA flag
    22Monitor
  • Later →CVE-2025-21694Feb 12, 2025 · fs/proc: fix softlockup in __read_vmcore (part 2)
    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 Linux14984139f1f2768883332965db566ef26db609e7Vendor (CNA)
Linux Linux15b453db41d36184cf0ccc21e7df624014ab6a1aVendor (CNA)
Linux Linux2f8dea1692eef2b7ba6a256246ed82c365fdc686Vendor (CNA)
Linux Linux38492f6ee883c7b1d33338bf531a62cff69b4b28Vendor (CNA)
Linux Linux3d41dbf82e10c44e53ea602398ab002baec27e75Vendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux5.10.234Vendor (CNA)
Linux Linux5.15.177Vendor (CNA)
Linux Linux5.4.290Vendor (CNA)
Linux Linux6.1.127Vendor (CNA)
Linux Linux6.6.74Vendor (CNA)
Linux Linux95e4f62df23f4df1ce6ef897d44b8e23c260921aVendor (CNA)
Linux Linuxa5cbbea145b400e40540c34816d16d36e0374fbcVendor (CNA)
azl3 kernel 6.6.64.2-9 on Azure Linux 3.06.6.76.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.76.1-1 on Azure Linux 3.06.6.76.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.05.15.180.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.176.3-3 on CBL-Mariner 2.05.15.180.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.05.15.180.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.128-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-64kb6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default-base6.12.0-160000.6.1.160000.2.4 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-docs6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-kvmsmall6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-build6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-qa6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-rt6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-source6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-syms6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)

+12

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.

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
high · data can be read
Integrity
high · data or configuration can be modified
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
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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

All records