CVE-2026-23361

Host memory corruption via MSI-X unmap race

Published Mar 25, 2026 · Updated Mar 25, 2026

Race condition in the Linux kernel PCI endpoint code allows local users to corrupt host memory or trigger IOMMU errors during MSI-X delivery. dw_pcie_ep_raise_msix_irq() issues a posted writel() and immediately unmaps its outbound ATU entry without flushing the write, so completion can occur after the mapping disappears. Reachability requires a DesignWare PCIe endpoint using MSI-X; losing the race can misdirect the write into host memory or produce IOMMU translation faults.

CVSS severity7.8
High
EPSS probability0.13%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Race condition in the Linux kernel PCI endpoint code allows local users to corrupt host memory or trigger IOMMU errors during MSI-X delivery. dw_pcie_ep_raise_msix_irq() issues a posted writel() and immediately unmaps its outbound ATU entry without flushing the write, so completion can occur after the mapping disappears. Reachability requires a DesignWare PCIe endpoint using MSI-X; losing the race can misdirect the write into host memory or produce IOMMU translation faults.

The record

CVE
CVE-2026-23361
Published
Mar 25, 2026
Updated
Mar 25, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
CWE-787
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Mar 25, 2026CVE publishedPublication date reported by the CVE source.
  2. Mar 25, 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=4.19
  2. Affected versionversion=beb4641a787df79a1423a8789d185b6b78fcbfea <6f60a783860c77b309f7d81003b6a0c73feca49e
  3. Affected versionversion=beb4641a787df79a1423a8789d185b6b78fcbfea <a7afb8f810c04845fdfc58c57d9cf0cc5f23ced0
  4. Affected versionversion=beb4641a787df79a1423a8789d185b6b78fcbfea <c22533c66ccae10511ad6a7afc34bb26c47577e3
  5. Affected versionversion=beb4641a787df79a1423a8789d185b6b78fcbfea <eaa6a56801ddd2d9b4980f19e7fe002b00994804

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=4.19; version=beb4641a787df79a1423a8789d185b6b78fcbfea <6f60a783860c77b309f7d81003b6a0c73feca49e; version=beb4641a787df79a1423a8789d185b6b78fcbfea <a7afb8f810c04845fdfc58c57d9cf0cc5f23ced0; version=beb4641a787df79a1423a8789d185b6b78fcbfea <c22533c66ccae10511ad6a7afc34bb26c47577e3; version=beb4641a787df79a1423a8789d185b6b78fcbfea <eaa6a56801ddd2d9b4980f19e7fe002b00994804

Published CVSS scores

7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-787Out-of-bounds Write

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