CVE-2025-38216: iommu/vt-d: Restore context entry setup order for aliased devices

Published Jul 4, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

iommu/vt-d: Restore context entry setup order for aliased devices

Commit 2031c469f816 ("iommu/vt-d: Add support for static identity domain") changed the context entry setup during domain attachment from a set-and-check policy to a clear-and-reset approach. This inadvertently introduced a regression affecting PCI aliased devices behind PCIe-to-PCI bridges.

Specifically, keyboard and touchpad stopped working on several Apple Macbooks with below messages:

kernel: platform pxa2xx-spi.3: Adding to iommu group 20 kernel: input: Apple SPI Keyboard as /devices/pci0000:00/0000:00:1e.3/pxa2xx-spi.3/spimaster/spi2/spi-APP000D:00/input/input0 kernel: DMAR: DRHD: handling fault status reg 3 kernel: DMAR: [DMA Read NOPASID] Request device [00:1e.3] fault addr 0xffffa000 [fault reason 0x06] PTE Read access is not set kernel: DMAR: DRHD: handling fault status reg 3 kernel: DMAR: [DMA Read NOPASID] Request device [00:1e.3] fault addr 0xffffa000 [fault reason 0x06] PTE Read access is not set kernel: applespi spi-APP000D:00: Error writing to device: 01 0e 00 00 kernel: DMAR: DRHD: handling fault status reg 3 kernel: DMAR: [DMA Read NOPASID] Request device [00:1e.3] fault addr 0xffffa000 [fault reason 0x06] PTE Read access is not set kernel: DMAR: DRHD: handling fault status reg 3 kernel: applespi spi-APP000D:00: Error writing to device: 01 0e 00 00

Fix this by restoring the previous context setup order.

Affected Software

3 affected components
Linux Kernel
Linux Linux kernel>=6.12<6.12.35
Linux Linux kernel>=6.13<6.15.4

Event History

Jul 4, 2025
CVE Published
via MITRE·01:37 PM
Data Sourced
via MITRE·01:37 PM
DescriptionSeverity
Data Sourced
via NVD·02:15 PM
RemedyDescriptionSeverityAffected Software
Nov 4, 58546
Event
via MITRE·06:58 PM

Frequently Asked Questions

1

What is the severity of CVE-2025-38216?

CVE-2025-38216 has been classified with a critical severity level due to its impact on the Linux kernel's IOMMU functionality.

2

How do I fix CVE-2025-38216?

To fix CVE-2025-38216, update your Linux kernel to the latest version that includes the security patches addressing this vulnerability.

3

What systems are affected by CVE-2025-38216?

CVE-2025-38216 affects systems running the Linux kernel that utilize IOMMU for device virtualization.

4

When was CVE-2025-38216 discovered?

CVE-2025-38216 was discovered as part of ongoing security assessments and has been reported recently in the context of kernel updates.

5

What type of vulnerability is CVE-2025-38216?

CVE-2025-38216 is a configuration and context management vulnerability within the IOMMU functionality of the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203