CVE-2023-52659
What it is
In the Linux kernel, the following vulnerability has been resolved: x86/mm: Ensure input to pfn_to_kaddr() is treated as a 64-bit type On 64-bit platforms, the pfn_to_kaddr() macro requires that the input value is 64 bits in order to ensure that valid address bits don't get lost when shifting that input by PAGE_SHIFT to calculate the physical address to provide a virtual address for. One such example is in pvalidate_pages() (used by SEV-SNP guests), where the GFN in the struct used for page-state change requests is a 40-bit bit-field, so attempts to pass this GFN field directly into pfn_to_kaddr() ends up causing guest crashes when dealing with addresses above the 1TB range due to the above. Fix this issue with SEV-SNP guests, as well as any similar cases that might cause issues in current/future code, by using an inline function, instead of a macro, so that the input is implicitly cast to the expected 64-bit input type prior to performing the shift operation. While it might be argued that the issue is on the caller side, other archs/macros have taken similar approaches to deal with instances like this, such as ARM explicitly casting the input to phys_addr_t: e48866647b48 ("ARM: 8396/1: use phys_addr_t in pfn_to_kaddr()") A C inline function is even better though. [ mingo: Refined the changelog some more & added __always_inline. ]
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of 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: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 6.6.23
- Linux Kernel < 6.7.11
- Linux Kernel < 6.8.2
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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-2023-52659.md and follow it. Check whether this project is affected by CVE-2023-52659. 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/325956b0173f11e98f90462be4829a8b8b0682ce
- https://git.kernel.org/stable/c/7e1471888a5e6e846e9b4d306e5327db2b58e64e
- https://git.kernel.org/stable/c/814305b5c23cb815ada68d43019f39050472b25f
- https://git.kernel.org/stable/c/8e5647a723c49d73b9f108a8bb38e8c29d3948ea
- https://git.kernel.org/stable/c/325956b0173f11e98f90462be4829a8b8b0682ce
- https://git.kernel.org/stable/c/7e1471888a5e6e846e9b4d306e5327db2b58e64e
- https://git.kernel.org/stable/c/814305b5c23cb815ada68d43019f39050472b25f
- https://git.kernel.org/stable/c/8e5647a723c49d73b9f108a8bb38e8c29d3948ea
References
- https://git.kernel.org/stable/c/325956b0173f11e98f90462be4829a8b8b0682ce
- https://git.kernel.org/stable/c/7e1471888a5e6e846e9b4d306e5327db2b58e64e
- https://git.kernel.org/stable/c/814305b5c23cb815ada68d43019f39050472b25f
- https://git.kernel.org/stable/c/8e5647a723c49d73b9f108a8bb38e8c29d3948ea
- https://git.kernel.org/stable/c/325956b0173f11e98f90462be4829a8b8b0682ce
- https://git.kernel.org/stable/c/7e1471888a5e6e846e9b4d306e5327db2b58e64e
- https://git.kernel.org/stable/c/814305b5c23cb815ada68d43019f39050472b25f
- https://git.kernel.org/stable/c/8e5647a723c49d73b9f108a8bb38e8c29d3948ea