dbcve.org
Linux KernelOperating system · Linux

CVE-2024-26810

HIGH · 7.8 CVSS v3.1 Published 2024-04-05
Fix available
A fix is available. Upgrade to 5.4.274 / 5.10.215 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Lock external INTx masking ops Mask operations through config space changes to DisINTx may race INTx configuration changes via ioctl. Create wrappers that add locking for paths outside of the core interrupt code. In particular, irq_type is updated holding igate, therefore testing is_intx() requires holding igate. For example clearing DisINTx from config space can otherwise race changes of the interrupt configuration. This aligns interfaces which may trigger the INTx eventfd into two camps, one side serialized by igate and the other only enabled while INTx is configured. A subsequent patch introduces synchronization for the latter flows.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-362

Two operations that should be atomic can interleave, so an attacker who wins a narrow timing window reaches an inconsistent, exploitable state. These bugs are subtle and easy to miss in review. Fixing them properly means correct locking or atomic operations around the shared resource.

General guidance for the race condition class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 3.6, < 5.4.274>= 5.5, < 5.10.215>= 5.11, < 5.15.154>= 5.16, < 6.1.84>= 6.2, < 6.6.24>= 6.7, < 6.7.12>= 6.8, < 6.8.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.4.274 / 5.10.215 / 5.15.154 or later
Fixed in 5.4.2745.10.2155.15.154
Recommended fix High confidence

Linux Kernel 5.4.274, 5.10.215, 5.15.154, or 6.1.84 (depending on which branch you are on)

  1. Identify the current running kernel version using `uname -r`
  2. Determine which branch the current kernel belongs to based on the version number
  3. Upgrade to the appropriate fixed kernel version for your branch: for 5.4.x upgrade to >= 5.4.274, for 5.10.x upgrade to >= 5.10.215, for 5.15.x upgrade to >= 5.15.154, for 6.1.x upgrade to >= 6.1.84
  4. Update the kernel package using the distribution's package manager (e.g., `apt-get update && apt-get install linux-image-<version>` for Debian/Ubuntu, `yum update kernel` for RHEL/CentOS, or `zypper update kernel` for SUSE)
  5. Reboot the system to load the fixed kernel
  6. Verify the new kernel version is running with `uname -r`
Caveat Kernel upgrades may require rebooting services and could have compatibility implications with custom kernel modules or specific driver requirements; ensure backup and test in staging if possible

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-26810 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data