In the Linux kernel, the following vulnerability has been resolved: iommufd: Take dma_resv lock before dma_buf_unpin() in release path dma_buf_unpin() requires the caller to hold the exporter's dma_resv lock: void dma_buf_unpin(struct dma_buf_attachment *attach) { ... dma_resv_assert_held(dmabuf->resv); ... } iopt_release_pages() calls dma_buf_unpin() without taking that lock, so every iommufd_ioas_destroy()/iommufd_ioas_unmap() that releases the last reference on a DMABUF-backed iopt_pages triggers a WARN. This was hit while running tools/testing/selftests/iommu/iommufd: WARNING: drivers/dma-buf/dma-buf.c:1137 at dma_buf_unpin+0x62/0x70 RIP: 0010:dma_buf_unpin+0x62/0x70 Call Trace: <TASK> dma_buf_unpin+0x62/0x70 iopt_release_pages+0xe4/0x190 iopt_unmap_iova_range+0x1c7/0x290 iopt_unmap_all+0x1a/0x30 iommufd_ioas_destroy+0x1d/0x50 iommufd_fops_release+0x93/0x150 __fput+0xfc/0x2c0 __x64_sys_close+0x3d/0x80 do_s
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-80633 is a lock ordering bug in the Linux kernel's iommufd subsystem where dma_buf_unpin() is called without holding the required dma_resv lock during resource cleanup. This vulnerability affects system stability and can lead to kernel crashes, data corruption, or potential privilege escalation when iommufd operations release DMA buffer references. Any system running vulnerable kernel versions with iommufd enabled—particularly those using GPU drivers, device passthrough, or other DMA-intensive I/O operations—faces exposure to denial of service attacks or privilege escalation through carefully timed memory operations.
While this CVE currently has no mapped MITRE ATT&CK techniques or CWE classification, practitioners using Casky.ai would benefit from extended reasoning analysis around kernel synchronization failures and resource management anomalies. Though Casky's current skill library shows zero direct matches for this specific vulnerability pattern, the platform's Claude-powered reasoning engine would help security teams identify similar lock-ordering defects by analyzing kernel audit logs for dma_resv synchronization failures, detecting unbalanced lock acquisition patterns, and correlating crash dumps with iommufd cleanup paths. Defenders should monitor kernel panic logs, enable lock debugging (CONFIG_PROVE_LOCKING), and track CVE advisories for their specific kernel versions and iommufd usage patterns.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-80633. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation