CVE-2024-26990
Last modified
CVE-2024-26990 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Write-protect L2 SPTEs in TDP MMU when clearing dirty status Check kvm_mmu_page_ad_need_write_protect() when deciding whether to write-protect or clear D-bits on TDP MMU SPTEs, so that the TDP MMU accounts for any role-specific reasons for disabling D-bit dirty logging. Specifically, TDP MMU SPTEs must be write-protected when the TDP MMU is being used to run an L2 (i.e. L1 has disabled EPT) and PML is enabled. KVM always disables PML when running L2, even when L1 and L2 GPAs are in the some domain, so failing to write-protect TDP MMU SPTEs will cause writes made by L2 to not be reflected in the dirty log. [sean: massage shortlog and changelog, tweak ternary op formatting]. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Write-protect L2 SPTEs in TDP MMU when clearing dirty status Check kvm_mmu_page_ad_need_write_protect() when deciding whether to write-protect or clear D-bits on TDP MMU SPTEs, so that the TDP MMU accounts for any role-specific reasons for disabling D-bit dirty logging. Specifically, TDP MMU SPTEs must be write-protected when the TDP MMU is being used to run an L2 (i.e. L1 has disabled EPT) and PML is enabled. KVM always disables PML when running L2, even when L1 and L2 GPAs are in the some domain, so failing to write-protect TDP MMU SPTEs will cause writes made by L2 to not be reflected in the dirty log. [sean: massage shortlog and changelog, tweak ternary op formatting]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.4, < 6.6.29 | — |
| Linux | Linux Kernel | >= 6.7, < 6.8.8 | — |
| Linux | Linux Kernel | 6.9 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-26990?
How severe is CVE-2024-26990?
How do I fix CVE-2024-26990?
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 2024
- CVE-2024-26984In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26985In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26986In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26987In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26988In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-26989In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-26991In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26992In the Linux kernel, the following vulnerability has been re…3.3
- CVE-2024-26993In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26994In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26995In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-26996In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2024-26990?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
