Skip to content
major vulnerability· requires attention

Affects the Linux kernel, a ubiquitous OS kernel; kernel memory corruption/privilege escalation impacts many organizations and warrants broad attention.

Systems

CVE-2026-89995

8.8
High
EPSS 0.32%Patch availableSep 19, 2026

Linux kernel dma-direct bug can cause kernel memory corruption

common questions

Is CVE-2026-89995 being exploited?

Not confirmed. CVE-2026-89995 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.

How severe is CVE-2026-89995?

CVE-2026-89995 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-89995?

Yes. A fix has been recorded for CVE-2026-89995. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-89995 affect?

CVE-2026-89995 affects Linux kernel (dma-direct API), Linux distributions using affected kernel versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-89995?

Apply vendor kernel updates or upgrade to fixed stable kernel

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (dma-direct API)Linux distributions using affected kernel versions
impact

Kernel memory corruption via dma_direct_alloc_from_pool type mismatch, enabling crashes, local privilege escalation, or arbitrary kernel code execution

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 5b138c534fda57c2ebc1e6de72578aa1d70788a6 and < c3fdb94da43ff23287f85664174c45c45e881a3f
  • affected>= 5b138c534fda57c2ebc1e6de72578aa1d70788a6 and < 408ff2d5bf555bd3f4c84a2edb95c0690bf9edc8
  • affected>= 5b138c534fda57c2ebc1e6de72578aa1d70788a6 and < feeb2ef775081a6c188cdd10e7a45369a07ce531
  • affected>= 5b138c534fda57c2ebc1e6de72578aa1d70788a6 and < 94a04ad732c9f8b9554270fc4038a06737de5c22
  • affected5.10
vendor says fixed in< 5.10, >= 6.12.110 and <= 6.12.*, >= 6.18.51 and <= 6.18.*, >= 7.2.5 and <= 7.2.*, >= 7.3-rc1 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free