CVE-2026-89448Hinoki check available

PCIe isolation bypass via omitted tboot ACS request

Published Sep 11, 2026 · Updated Sep 11, 2026

Security-feature bypass in affected Linux kernels allows attackers to weaken PCIe device isolation on Intel VT-d systems. The detect_intel_iommu() path omits tboot when deciding whether to call pci_request_acs(), yet tboot_force_iommu() later enables the IOMMU. Exposure requires an Intel TXT/tboot launch with ACS disabled by options or platform state, leaving PCIe peer traffic without the intended isolation and enabling DMA attacks.

CVSS severityUnavailable
Unscored
EPSS probability0.14%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Security-feature bypass in affected Linux kernels allows attackers to weaken PCIe device isolation on Intel VT-d systems. The detect_intel_iommu() path omits tboot when deciding whether to call pci_request_acs(), yet tboot_force_iommu() later enables the IOMMU. Exposure requires an Intel TXT/tboot launch with ACS disabled by options or platform state, leaving PCIe peer traffic without the intended isolation and enabling DMA attacks.

The record

CVE
CVE-2026-89448
Published
Sep 11, 2026
Updated
Sep 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1200
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Sep 11, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 11, 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.

  1. Affected versionversion=2.6.33
  2. Affected versionversion=5d990b627537e59a3a2f039ff588a4750e9c1a6a <45705a6bfdb283f7b3b509010fd617b72f942537
  3. Affected versionversion=5d990b627537e59a3a2f039ff588a4750e9c1a6a <607432b2618b61df81134be0ef2562b8300c1216
  4. Affected versionversion=5d990b627537e59a3a2f039ff588a4750e9c1a6a <87bc611c6c98a41c00feb7b06b0c297dd141a2ae
  5. Affected versionversion=5d990b627537e59a3a2f039ff588a4750e9c1a6a <aaeb81241e802c86be69394f72d49fde3f861fbb

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=2.6.33; version=5d990b627537e59a3a2f039ff588a4750e9c1a6a <45705a6bfdb283f7b3b509010fd617b72f942537; version=5d990b627537e59a3a2f039ff588a4750e9c1a6a <607432b2618b61df81134be0ef2562b8300c1216; version=5d990b627537e59a3a2f039ff588a4750e9c1a6a <87bc611c6c98a41c00feb7b06b0c297dd141a2ae; version=5d990b627537e59a3a2f039ff588a4750e9c1a6a <aaeb81241e802c86be69394f72d49fde3f861fbb

Published CVSS scores

No CVSS assessment is available in this record.

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1200Hardware Additions

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