Local privilege escalation via incorrect SWIOTLB free
Published Sep 17, 2026 · Updated Sep 18, 2026
Memory corruption in affected Linux kernel builds starting with 6.6 allows local users to gain kernel privileges through ordinary I/O. The swiotlb_init_io_tlb_pool() function reconstructs a direct-map address instead of retaining the remapped DMA atomic-pool address, so swiotlb_free_tlb() frees an address the pool cannot recognize. Exploitation requires an ARM64 realm guest with CONFIG_DMA_DIRECT_REMAP and forced unencrypted DMA; the bad free can corrupt allocator metadata, expose stale mappings, or crash the guest.
Summary
What happened
Memory corruption in affected Linux kernel builds starting with 6.6 allows local users to gain kernel privileges through ordinary I/O. The swiotlb_init_io_tlb_pool() function reconstructs a direct-map address instead of retaining the remapped DMA atomic-pool address, so swiotlb_free_tlb() frees an address the pool cannot recognize. Exploitation requires an ARM64 realm guest with CONFIG_DMA_DIRECT_REMAP and forced unencrypted DMA; the bad free can corrupt allocator metadata, expose stale mappings, or crash the guest.
The record
- CVE
- CVE-2026-90387
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 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=6.6
- Affected versionversion=79636caad3618e2b38457f6e298c9b31ba82b489 <35e0103177826430b5df888b1506239d41e76ab5
- Affected versionversion=79636caad3618e2b38457f6e298c9b31ba82b489 <45507dcb0847e96add4455274b12df0eca6590b4
- Affected versionversion=79636caad3618e2b38457f6e298c9b31ba82b489 <57d29044d0f29a76c6ec0c112c8c7371d5608dc7
- Affected versionversion=79636caad3618e2b38457f6e298c9b31ba82b489 <68bf3ebd8e7020dae58e8aa14c7d482738bff9a8
- Affected versionversion=79636caad3618e2b38457f6e298c9b31ba82b489 <c1f4d7763cdf1b9e0d35c14aa6f52d0512a36319
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started