Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-31076: genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline

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.25% (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 59f86a2908380d09cdc726461c0fbb8d8579c99f, 6752dfcfff3ac3e16625ebd3f0ad9630900e7e76, 9eeda3e0071a329af1eba15f4e57dc39576bb420.

Low priority for now. Upgrade to Linux Linux 59f86a2908380d09cdc726461c0fbb8d8579c99f, 6752dfcfff3ac3e16625ebd3f0ad9630900e7e76, 9eeda3e0071a329af1eba15f4e57dc39576bb420 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: genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline The absence of IRQD_MOVE_PCNTXT prevents immediate effectiveness of interrupt affinity reconfiguration via procfs. Instead, the change is deferred until the next instance of the interrupt being triggered on the original CPU. When the interrupt next triggers on the original CPU, the new affinity is enforced within __irq_move_irq(). A vector is allocated from the new CPU, but the old vector on the original CPU remains and is not immediately reclaimed. Instead, apicd->move_in_progress is flagged, and the reclaiming process is delayed until the next trigger of the interrupt on the new CPU. Upon the subsequent triggering of the interrupt on the new CPU, irq_complete_move() adds a task to the old CPU's vector_cleanup list if it remains online. Subsequently, the timer on the old CPU iterates over its vector_cleanup list, reclaiming old vectors. However, a rare scenario arises if the old CPU is outgoing before the interrupt triggers again on the new CPU. In that case irq_force_complete_move() is not invoked on the outgoing CPU to reclaim the old apicd->prev_vector because the interrupt isn't currently affine to the outgoing CPU, and irq_needs_fixup() returns false. Even though __vector_schedule_cleanup() is later called on the new CPU, it doesn't reclaim apicd->prev_vector; instead, it simply resets both apicd->move_in_progress and apicd->prev_vector to 0. As a result, the vector remains unreclaimed in vector_matrix, leading to a CPU vector leak. To address this issue, move the invocation of irq_force_complete_move() before the irq_needs_fixup() call to reclaim apicd->prev_vector, if the interrupt is currently or used to be affine to the outgoing CPU. Additionally, reclaim the vector in __vector_schedule_cleanup() as well, following a warning message, although theoretically it should never see apicd->move_in_progress with apicd->prev_cpu pointing to an offline CPU.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jun 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 17th 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-31076

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.13 and later · before 4.19.316
  • linux linux kernel4.20 and later · before 5.4.278
  • linux linux kernel5.5 and later · before 5.10.219
  • linux linux kernel5.11 and later · before 5.15.161
  • linux linux kernel5.16 and later · before 6.1.93
  • linux linux kernel6.2 and later · before 6.6.33
  • linux linux kernel6.7 and later · before 6.9.4

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

    • 4.13affected
    • f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b and later · before a40209d355afe4ed6d533507838c9e5cd70a76d8affected · git
    • f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b and later · before f5f4675960609d8c5ee95f027fbf6ce380f98372affected · git
    • f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b and later · before 6752dfcfff3ac3e16625ebd3f0ad9630900e7e76affected · git
    • f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b and later · before 9eeda3e0071a329af1eba15f4e57dc39576bb420affected · git
    • f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b and later · before e9c96d01d520498b169ce734a8ad1142bef86a30affected · git
    • f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b and later · before 59f86a2908380d09cdc726461c0fbb8d8579c99faffected · git
    • f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b and later · before ebfb16fc057a016abb46a9720a54abf0d4f6abe1affected · git
    • f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b and later · before a6c11c0a5235fb144a65e0cb2ffd360ddc1f6c32affected · git
    • before 4.13not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:11linuxbefore 5.10.221-15.10.221-1
Debian:12linuxbefore 6.1.94-16.1.94-1
Debian:13linuxbefore 6.9.7-16.9.7-1
Red Hat:rhel_eus:8.8::baseosbpftoolbefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseosbpftool-debuginfobefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernelbefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-abi-stablelistsbefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-corebefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debugbefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-corebefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-debuginfobefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-develbefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-modulesbefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-modules-extrabefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfobefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-aarch64before 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-ppc64lebefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-s390xbefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-develbefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-docbefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-modulesbefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-modules-extrabefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-toolsbefore 0:4.18.0-477.81.1.el8_80:4.18.0-477.81.1.el8_8

+96

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-2023-52883Jun 20, 2024 · drm/amdgpu: Fix possible null pointer dereference
    30Monitor
  • ← EarlierCVE-2023-52884Jun 21, 2024 · Input: cyapa - add missing input core locking to suspend/resume functions
    17Monitor
  • Later →CVE-2024-33619Jun 21, 2024 · efi: libstub: only free priv.runtime_map when allocated
    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 Linux59f86a2908380d09cdc726461c0fbb8d8579c99fVendor (CNA)
Linux Linux6752dfcfff3ac3e16625ebd3f0ad9630900e7e76Vendor (CNA)
Linux Linux9eeda3e0071a329af1eba15f4e57dc39576bb420Vendor (CNA)
Linux Linuxa40209d355afe4ed6d533507838c9e5cd70a76d8Vendor (CNA)
Linux Linuxa6c11c0a5235fb144a65e0cb2ffd360ddc1f6c32Vendor (CNA)
Linux Linuxe9c96d01d520498b169ce734a8ad1142bef86a30Vendor (CNA)
Linux Linuxebfb16fc057a016abb46a9720a54abf0d4f6abe1Vendor (CNA)
Linux Linuxf5f4675960609d8c5ee95f027fbf6ce380f98372Vendor (CNA)
debian:linux6.1.94-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage 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.

EPSS, last 120 days

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