CVE-2024-26990
What it is
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]
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 6.6.29
- Linux Kernel < 6.8.8
- Linux Kernel 6.9
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-26990.md and follow it. Check whether this project is affected by CVE-2024-26990. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/2673dfb591a359c75080dd5af3da484b89320d22
- https://git.kernel.org/stable/c/cdf811a937471af2d1facdf8ae80e5e68096f1ed
- https://git.kernel.org/stable/c/e20bff0f1b2de9cfe303dd35ff46470104a87404
- https://git.kernel.org/stable/c/2673dfb591a359c75080dd5af3da484b89320d22
- https://git.kernel.org/stable/c/cdf811a937471af2d1facdf8ae80e5e68096f1ed
- https://git.kernel.org/stable/c/e20bff0f1b2de9cfe303dd35ff46470104a87404
References
- https://git.kernel.org/stable/c/2673dfb591a359c75080dd5af3da484b89320d22
- https://git.kernel.org/stable/c/cdf811a937471af2d1facdf8ae80e5e68096f1ed
- https://git.kernel.org/stable/c/e20bff0f1b2de9cfe303dd35ff46470104a87404
- https://git.kernel.org/stable/c/2673dfb591a359c75080dd5af3da484b89320d22
- https://git.kernel.org/stable/c/cdf811a937471af2d1facdf8ae80e5e68096f1ed
- https://git.kernel.org/stable/c/e20bff0f1b2de9cfe303dd35ff46470104a87404
- https://lists.fedoraproject.org/archives/list/[email protected]/message/4EZ6PJW7VOZ224TD7N4JZNU6KV32ZJ53/
- https://lists.fedoraproject.org/archives/list/[email protected]/message/DAMSOZXJEPUOXW33WZYWCVAY7Z5S7OOY/
- https://lists.fedoraproject.org/archives/list/[email protected]/message/GCBZZEC7L7KTWWAS2NLJK6SO3IZIL4WW/