CVE-2026-45944
Last modified
CVE-2026-45944 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Clear Present bit before tearing down context entry When tearing down a context entry, the current implementation zeros the entire 128-bit entry using multiple 64-bit writes. This creates a window where the hardware can fetch a "torn" entry — where some fields are already zeroed while the 'Present' bit is still set — leading to unpredictable behavior or spurious faults. While x86 provides strong write ordering, the compiler may reorder writes to the two 64-bit halves of the context entry. 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: Clear Present bit before tearing down context entry When tearing down a context entry, the current implementation zeros the entire 128-bit entry using multiple 64-bit writes. This creates a window where the hardware can fetch a "torn" entry — where some fields are already zeroed while the 'Present' bit is still set — leading to unpredictable behavior or spurious faults. While x86 provides strong write ordering, the compiler may reorder writes to the two 64-bit halves of the context entry. Even without compiler reordering, the hardware fetch is not guaranteed to be atomic with respect to multiple CPU writes. Align with the "Guidance to Software for Invalidations" in the VT-d spec (Section 6.5.3.3) by implementing the recommended ownership handshake: 1. Clear only the 'Present' (P) bit of the context entry first to signal the transition of ownership from hardware to software. 2. Use dma_wmb() to ensure the cleared bit is visible to the IOMMU. 3. Perform the required cache and context-cache invalidation to ensure hardware no longer has cached references to the entry. 4. Fully zero out the entry only after the invalidation is complete. Also, add a dma_wmb() to context_set_present() to ensure the entry is fully initialized before the 'Present' bit becomes visible.
Metrics
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 2.6.24, < 6.18.14 |
| Linux | Linux Kernel | >= 6.19, < 6.19.4 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-45944?
How severe is CVE-2026-45944?
How do I fix CVE-2026-45944?
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-45939In the Linux kernel, the following vulnerability has been re…5.5
- 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-45945In the Linux kernel, the following vulnerability has been re…8.8
- 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
Are you affected by CVE-2026-45944?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
