Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26813: vfio/platform: Create persistent IRQ handlers

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 07afdfd8a68f9eea8db0ddc4626c874f29d2ac5e, 09452c8fcbd7817c06e8e3212d99b45917e603a5, 0f8d8f9c2173a541812dd750529f4a415117eb29.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 07afdfd8a68f9eea8db0ddc4626c874f29d2ac5e, 09452c8fcbd7817c06e8e3212d99b45917e603a5, 0f8d8f9c2173a541812dd750529f4a415117eb29 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: vfio/platform: Create persistent IRQ handlers The vfio-platform SET_IRQS ioctl currently allows loopback triggering of an interrupt before a signaling eventfd has been configured by the user, which thereby allows a NULL pointer dereference. Rather than register the IRQ relative to a valid trigger, register all IRQs in a disabled state in the device open path. This allows mask operations on the IRQ to nest within the overall enable state governed by a valid eventfd signal. This decouples @masked, protected by the @locked spinlock from @trigger, protected via the @igate mutex. In doing so, it's guaranteed that changes to @trigger cannot race the IRQ handlers because the IRQ handler is synchronously disabled before modifying the trigger, and loopback triggering of the IRQ via ioctl is safe due to serialization with trigger changes via igate. For compatibility, request_irq() failures are maintained to be local to the SET_IRQS ioctl rather than a fatal error in the open device path. This allows, for example, a userspace driver with polling mode support to continue to work regardless of moving the request_irq() call site. This necessarily blocks all SET_IRQS access to the failed index.

Published
Apr 5, 2024
Updated
Jun 17, 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-26813

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

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

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.1affected
    • 57f972e2b341dd6a73533f9293ec55d584a5d833 and later · before 07afdfd8a68f9eea8db0ddc4626c874f29d2ac5eaffected · git
    • 57f972e2b341dd6a73533f9293ec55d584a5d833 and later · before 09452c8fcbd7817c06e8e3212d99b45917e603a5affected · git
    • 57f972e2b341dd6a73533f9293ec55d584a5d833 and later · before cc5838f19d39a5fef04c468199699d2a4578be3aaffected · git
    • 57f972e2b341dd6a73533f9293ec55d584a5d833 and later · before 7932db06c82c5b2f42a4d1a849d97dba9ce4a362affected · git
    • 57f972e2b341dd6a73533f9293ec55d584a5d833 and later · before 62d4e43a569b67929eb3319780be5359694c8086affected · git
    • 57f972e2b341dd6a73533f9293ec55d584a5d833 and later · before d6bedd6acc0bcb1e7e010bc046032e47f08d379faffected · git
    • 57f972e2b341dd6a73533f9293ec55d584a5d833 and later · before 0f8d8f9c2173a541812dd750529f4a415117eb29affected · git
    • 57f972e2b341dd6a73533f9293ec55d584a5d833 and later · before 675daf435e9f8e5a5eab140a9864dfad6668b375affected · git
    • before 4.1not affected · semver
Affected versions · NVD (7)

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

  • linux linux kernel4.1 and later · before 5.4.274
  • linux linux kernel5.5 and later · before 5.10.215
  • linux linux kernel5.11 and later · before 5.15.154
  • linux linux kernel5.16 and later · before 6.1.84
  • linux linux kernel6.2 and later · before 6.6.24
  • linux linux kernel6.7 and later · before 6.7.12
  • linux linux kernel6.8 and later · before 6.8.3

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.85-16.1.85-1
Debian:13linuxbefore 6.7.12-16.7.12-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-26799Apr 4, 2024 · ASoC: qcom: Fix uninitialized pointer dmactl
    28Monitor
  • ← EarlierCVE-2024-26805Apr 4, 2024 · netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter
    22Monitor
  • Later →CVE-2024-26814Apr 5, 2024 · vfio/fsl-mc: Block calling interrupt handler without trigger
    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 Linux07afdfd8a68f9eea8db0ddc4626c874f29d2ac5eVendor (CNA)
Linux Linux09452c8fcbd7817c06e8e3212d99b45917e603a5Vendor (CNA)
Linux Linux0f8d8f9c2173a541812dd750529f4a415117eb29Vendor (CNA)
Linux Linux62d4e43a569b67929eb3319780be5359694c8086Vendor (CNA)
Linux Linux675daf435e9f8e5a5eab140a9864dfad6668b375Vendor (CNA)
Linux Linux7932db06c82c5b2f42a4d1a849d97dba9ce4a362Vendor (CNA)
Linux Linuxcc5838f19d39a5fef04c468199699d2a4578be3aVendor (CNA)
Linux Linuxd6bedd6acc0bcb1e7e010bc046032e47f08d379fVendor (CNA)
debian:linux6.1.85-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.

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 · variant or chain candidate · 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

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

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

Show all references (8 more)

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

All records