CVE-2023-52659x86/mm: Ensure input to pfn_to_kaddr() is treated as a 64-bit type
- 5.5MediumCVSS base score
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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. ]
Timeline
ID reserved
By Linux
- 2 months later
· 2 months later
Published
- 24 months later
· 24 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 6c3211796326a9d35618b866826ca556c8f008a8 – < 325956b0173f11e98f90462be4829a8b8b0682ce
- affected 6c3211796326a9d35618b866826ca556c8f008a8 – < 7e1471888a5e6e846e9b4d306e5327db2b58e64e
- affected 6c3211796326a9d35618b866826ca556c8f008a8 – < 814305b5c23cb815ada68d43019f39050472b25f
- affected 6c3211796326a9d35618b866826ca556c8f008a8 – < 8e5647a723c49d73b9f108a8bb38e8c29d3948ea
- affected 6.5
- unaffected < 6.5
- unaffected 6.6.23 – ≤ 6.6.*
- unaffected 6.7.11 – ≤ 6.7.*
- unaffected 6.8.2 – ≤ 6.8.*
- unaffected 6.9 – ≤ *
References
References4
- https://git.kernel.org/stable/c/325956b0173f11e98f90462be4829a8b8b0682ce (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/7e1471888a5e6e846e9b4d306e5327db2b58e64e (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/814305b5c23cb815ada68d43019f39050472b25f (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/8e5647a723c49d73b9f108a8bb38e8c29d3948ea (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2023-57283 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-52659)Record last updated .