Kernel memory corruption via incorrect DMA cleanup
Published Aug 15, 2026 · Updated Aug 15, 2026
Improper DMA cleanup in the Linux kernel allows remote attackers to exhaust DMA mappings and crash the system through crypto traffic. The sg_cleanup error path iterates with j but passes list[i] when unmapping, leaking successful mappings and repeatedly unmapping the failed entry. Exposure requires an affected branch using Cavium CPT hardware and its driver; stale mappings can disclose or corrupt kernel memory or cause a panic.
Summary
What happened
Improper DMA cleanup in the Linux kernel allows remote attackers to exhaust DMA mappings and crash the system through crypto traffic. The sg_cleanup error path iterates with j but passes list[i] when unmapping, leaking successful mappings and repeatedly unmapping the failed entry. Exposure requires an affected branch using Cavium CPT hardware and its driver; stale mappings can disclose or corrupt kernel memory or cause a panic.
The record
- CVE
- CVE-2026-74279
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.11
- Affected versionversion=c694b233295b99c33dd5ac28aede9f171f5a6862 <23c6174e48f66fc10b998b0acdb406cb0caf5c80
- Affected versionversion=c694b233295b99c33dd5ac28aede9f171f5a6862 <23d3a7e896a1fe2d7a6bcb42f093948b79f8a198
- Affected versionversion=c694b233295b99c33dd5ac28aede9f171f5a6862 <28141f95ae93b18f9bfde953cb787fcb151fb9da
- Affected versionversion=c694b233295b99c33dd5ac28aede9f171f5a6862 <3b8a1e1f4e4071a62b20374028744e8cc8310d48
- Affected versionversion=c694b233295b99c33dd5ac28aede9f171f5a6862 <8afd1007ef79898a6e010eaade97097e49405fce
- Affected versionversion=c694b233295b99c33dd5ac28aede9f171f5a6862 <9dbf173bd32d5f81b005008b682bfb50aa093455
- Affected versionversion=c694b233295b99c33dd5ac28aede9f171f5a6862 <d319b83b97b3585550d9ae592dfa78c755b6129e
- Affected versionversion=c694b233295b99c33dd5ac28aede9f171f5a6862 <fb4d57b83356d4bd411b45ede3024e0ff42c9b5e
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo