---
title: "CVE-2026-90388: Linux Kernel - Memory Allocation Handling Flaw"
description: "Linux kernel contains a memory allocation handling flaw in iommu/dma non-blocking, non-coherent allocation path, caused by improper failure detection in dma_alloc_from_pool(), letting kernel potentially mismanage IOMMU mappings, exploit requires kernel code execution."
url: https://panop.io/threat-heartbeat/CVE-2026-90388/
---

# CVE-2026-90388 Linux Kernel - Memory Allocation Handling Flaw

Linux kernel contains a memory allocation handling flaw in iommu/dma non-blocking, non-coherent allocation path, caused by improper failure detection in dma\_alloc\_from\_pool(), letting kernel potentially mismanage IOMMU mappings, exploit requires kernel code execution.

CVSS base score 7.8 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.16% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-90388)

## Details

Type

Memory Allocation Handling Flaw

Impact

Denial Of Service, Privilege Escalation

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Published

17 September 2026

Updated

15 October 2026

## Vendor fix

Update to the latest Linux kernel version containing the fix.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-90388](https://nvd.nist.gov/vuln/detail/CVE-2026-90388)
- [https://git.kernel.org/stable/c/ac9cd0a669b8be5d178dbd471b0d68039dac58b5](https://git.kernel.org/stable/c/ac9cd0a669b8be5d178dbd471b0d68039dac58b5)
- [https://git.kernel.org/stable/c/af95a0ebc0a0db0762be75f51eadf770bad01aaa](https://git.kernel.org/stable/c/af95a0ebc0a0db0762be75f51eadf770bad01aaa)
- [https://git.kernel.org/stable/c/d56c3f955b21e5764c1497e295a5b5d0b3a40470](https://git.kernel.org/stable/c/d56c3f955b21e5764c1497e295a5b5d0b3a40470)
- [https://git.kernel.org/stable/c/db46cb9da83a507d86d2bb080bdb09c865da3d0a](https://git.kernel.org/stable/c/db46cb9da83a507d86d2bb080bdb09c865da3d0a)
- [https://git.kernel.org/stable/c/fb0b39287ba894dbdfac2901c51788b63f5c2291](https://git.kernel.org/stable/c/fb0b39287ba894dbdfac2901c51788b63f5c2291)
- [https://git.kernel.org/stable/c/06dffc96693083dda3412311406e558cf27f1574](https://git.kernel.org/stable/c/06dffc96693083dda3412311406e558cf27f1574)
- [https://git.kernel.org/stable/c/8c486293ddd0af60991408149fc3e964ea888dc4](https://git.kernel.org/stable/c/8c486293ddd0af60991408149fc3e964ea888dc4)
- [https://git.kernel.org/stable/c/a4ace31d732b657d774e31fb444c0c27d42c78e5](https://git.kernel.org/stable/c/a4ace31d732b657d774e31fb444c0c27d42c78e5)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)