CVE-2024-26785: iommufd: Fix protection fault in iommufd_test_syz_conv_iova
In the Linux kernel, the following vulnerability has been resolved:
iommufd: Fix protection fault in iommufd_test_syz_conv_iova
Syzkaller reported the following bug:
general protection fault, probably for non-canonical address 0xdffffc0000000038: 0000 [#1] SMP KASAN
KASAN: null-ptr-deref in range [0x00000000000001c0-0x00000000000001c7]
Call Trace:
lock_acquire
lock_acquire+0x1ce/0x4f0
down_read+0x93/0x4a0
iommufd_test_syz_conv_iova+0x56/0x1f0
iommufd_test_access_rw.isra.0+0x2ec/0x390
iommufd_test+0x1058/0x1e30
iommufd_fops_ioctl+0x381/0x510
vfs_ioctl
__do_sys_ioctl
__se_sys_ioctl
__x64_sys_ioctl+0x170/0x1e0
do_syscall_x64
do_syscall_64+0x71/0x140
This is because the new iommufd_access_change_ioas() sets access->ioas to
NULL during its process, so the lock might be gone in a concurrent racing
context.
Fix this by doing the same access->ioas sanity as iommufd_access_rw() and
iommufd_access_pin_pages() functions do.
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can let a low-privileged local user crash affected systems by hitting a race in iommufd handling. The known impact is availability loss, not data theft or privilege escalation. The source record says the issue is resolved in upstream stable commits, but distro-specific affected ranges require vendor confirmation.
Executive priority
Treat this as a normal-priority kernel availability fix. It is not evidence of internet-wide compromise, but it can affect service stability on multi-user or workload-hosting systems. Patch through standard kernel maintenance windows, faster for shared compute, developer workstations, and container hosts.
Technical view
CVE-2024-26785 is a local Linux kernel iommufd race where iommufd_access_change_ioas() can temporarily set access->ioas to NULL while another path expects its lock. Syzkaller observed a KASAN null-pointer dereference and general protection fault through iommufd_test_syz_conv_iova. CVSS is 5.5, local, low privilege, availability high.
Likely exposure
Exposure is limited to affected Linux kernel builds with reachable iommufd ioctl/test paths. The provided data names Linux kernel versions around 6.6 to 6.8 and kernel stable commits, but does not establish distro package status, default configuration, or cloud provider exposure.
Exploitation context
The CVE is not listed as CISA KEV in the bundle, and no cited source states active exploitation. The bug was reported by Syzkaller, suggesting automated kernel fuzzing discovery. Practical abuse would require local low-privileged access and a vulnerable kernel path.
Researcher notes
The strongest evidence is the kernel CVE description and stable commit references. The bundle does not provide exploit proof, distro matrices, or operational mitigations beyond applying the resolved upstream fixes. Avoid overstating CWE-120 because the described failure is a race leading to NULL dereference.
Mitigation direction
Update affected Linux kernels using distribution or vendor packages.
Prioritize systems where untrusted local users or workloads can run code.
Track the referenced upstream stable commits in kernel maintenance branches.
Confirm whether your distro backported the fix into older kernel package versions.
If patching is delayed, reduce local shell and container access where feasible.
Validation and detection
Inventory Linux kernel versions across servers, desktops, and container hosts.
Check distro advisories for CVE-2024-26785 fixed package versions.
Compare custom kernels against the referenced upstream stable commits.
Review crash telemetry for kernel general protection faults involving iommufd.
Document whether iommufd-related features are enabled or used locally.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-120 · source CWE mapping
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.