CVE-2026-45945
Last modified
CVE-2026-45945 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix race condition during PASID entry replacement The Intel VT-d PASID table entry is 512 bits (64 bytes). When replacing an active PASID entry (e.g., during domain replacement), the current implementation calculates a new entry on the stack and copies it to the table using a single structure assignment. struct pasid_entry *pte, new_pte; pte = intel_pasid_get_entry(dev, pasid); pasid_pte_config_first_level(iommu, &new_pte, ...); *pte = new_pte; Because the hardware may fetch the 512-bit PASID entry in multiple 128-bit chunks, updating the entire entry while it is active (Present bit set) risks a "torn" read. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix race condition during PASID entry replacement The Intel VT-d PASID table entry is 512 bits (64 bytes). When replacing an active PASID entry (e.g., during domain replacement), the current implementation calculates a new entry on the stack and copies it to the table using a single structure assignment. struct pasid_entry *pte, new_pte; pte = intel_pasid_get_entry(dev, pasid); pasid_pte_config_first_level(iommu, &new_pte, ...); *pte = new_pte; Because the hardware may fetch the 512-bit PASID entry in multiple 128-bit chunks, updating the entire entry while it is active (Present bit set) risks a "torn" read. In this scenario, the IOMMU hardware could observe an inconsistent state — partially new data and partially old data — leading to unpredictable behavior or spurious faults. Fix this by removing the unsafe "replace" helpers and following the "clear-then-update" flow, which ensures the Present bit is cleared and the required invalidation handshake is completed before the new configuration is applied.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.13, < 6.19.4 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-45945?
How severe is CVE-2026-45945?
How do I fix CVE-2026-45945?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-4594A vulnerability has been found in erupts erupt up to 1.13.3.…7.3
- CVE-2026-45940In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-45941In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-45942In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-45943In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-45944In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-45946In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-45947In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-45948In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-45949In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-4595A vulnerability was determined in code-projects Exam Form Su…2.4
- CVE-2026-45950In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-45945?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
