Bug 2536497 (CVE-2026-90332) - CVE-2026-90332 kernel: PCI: dwc: ep: Flush cached MSI write before unmapping the iATU
Summary: CVE-2026-90332 kernel: PCI: dwc: ep: Flush cached MSI write before unmapping ...
Keywords:
Status: NEW
Alias: CVE-2026-90332
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-17 18:13 UTC by OSIDB Bzimport
Modified: 2026-10-13 14:26 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-17 18:13:45 UTC
In the Linux kernel, the following vulnerability has been resolved:

PCI: dwc: ep: Flush cached MSI write before unmapping the iATU

The MSI-X path already flushes any posted MSI-X write before tearing down
its iATU mapping. That was added by commit c22533c66cca ("PCI: dwc: ep:
Flush MSI-X write before unmapping its ATU entry") to make sure the write
reaches the Root Complex before the outbound window that translates it
disappears.

The MSI path has the same problem but no equivalent flush. When the
Endpoint driver caches an MSI target address and later observes that the
Root Complex has changed it, dw_pcie_ep_raise_msi_irq() unmaps the existing
iATU entry and reprograms it for the new address. Between the last MSI
writel() and the unmap there may still be a posted write sitting in the
fabric, and unmapping the iATU entry can drop or misroute that write.

Fix this by reading back from the mapped MSI window before the unmap. The
readback drains any posted MSI writes through the same iATU entry that
mapped them, which is the same logic the MSI-X path uses.

[mani: commit log]


Note You need to log in before you can comment on or make changes to this bug.