CVE-2024-26814: Linux kernel · vfio/fsl-mc: Block calling interrupt handler without trigger
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1065.71~20.04.1 : update Linux kernel when convenient.
Data as of 12 Nov 2026, 18:50 UTC
- Patch
- Available – fixed in 5.15.0-1065.71~20.04.1, 5.15.0-1068.77~20.04.1, 5.15.0-1065.73~20.04.1 +39
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6816-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6817-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6817-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6817-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6878-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6917-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6919-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6927-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-ibmpkg:deb/ubuntu/linux-ibm?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: vfio/fsl-mc: Block calling interrupt handler without trigger The eventfd_ctx trigger pointer of the vfio_fsl_mc_irq object is initially NULL and may become NULL if the user sets the trigger eventfd to -1. The interrupt handler itself is guaranteed that trigger is always valid between request_irq() and free_irq(), but the loopback testing mechanisms to invoke the handler function need to test the trigger. The triggering and setting ioctl paths both make use of igate and are therefore mutually exclusive. The vfio-fsl-mc driver does not make use of irqfds, nor does it support any sort of masking operations, therefore unlike vfio-pci and vfio-platform, the flow can remain essentially unchanged.
References
- ubuntu.com/security/CVE-2024-26814 (opens in a new tab)
- git.kernel.org/stable/c/083e750c9f5f4c3bf61161330fb84d7c8e8bb417 (opens in a new tab)
- git.kernel.org/stable/c/ee0bd4ad780dfbb60355b99f25063357ab488267 (opens in a new tab)
- git.kernel.org/stable/c/de87511fb0404d23b6da5f4660383b6ed095e28d (opens in a new tab)
- git.kernel.org/stable/c/6ec0d88166dac43f29e96801c0927d514f17add9 (opens in a new tab)
- git.kernel.org/stable/c/7447d911af699a15f8d050dfcb7c680a86f87012 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-26814 (opens in a new tab)
- ubuntu.com/security/notices/USN-6816-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6817-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6817-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6817-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6878-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6917-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6919-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6927-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7019-1 (opens in a new tab)