Vulnerability · Published May 17, 2024 · Assigned by Linux

CVE-2023-52659x86/mm: Ensure input to pfn_to_kaddr() is treated as a 64-bit type

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 13% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 87.5% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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. ]

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.7.12-1DEBIAN-CVE-2023-52659
Debian:14linux6.7.12-1DEBIAN-CVE-2023-52659
Ubuntu:24.04:LTSlinux6.8.0-35.35USN-6816-1
Ubuntu:24.04:LTSlinux6.8.0-35.35UBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-52659
Ubuntu:24.04:LTSlinux-aws6.8.0-1009.9UBUNTU-CVE-2023-52659
Ubuntu:24.04:LTSlinux-aws6.8.0-1009.9USN-6817-1
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-52659
Ubuntu:24.04:LTSlinux-azure6.8.0-1008.8USN-6817-3
Ubuntu:24.04:LTSlinux-azure6.8.0-1008.8UBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-52659
Ubuntu:24.04:LTSlinux-gcp6.8.0-1008.9USN-6817-1
Ubuntu:24.04:LTSlinux-gcp6.8.0-1008.9UBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2023-52659
Ubuntu:24.04:LTSlinux-gke6.8.0-1004.7USN-6817-3
Ubuntu:24.04:LTSlinux-gke6.8.0-1004.7UBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2023-52659
Ubuntu:24.04:LTSlinux-ibm6.8.0-1006.6USN-6816-1
Ubuntu:24.04:LTSlinux-ibm6.8.0-1006.6UBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2023-52659
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-35.35.1USN-6816-1
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-35.35.1UBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2023-52659
Ubuntu:24.04:LTSlinux-oem-6.86.8.0-1006.6USN-6817-2
Ubuntu:24.04:LTSlinux-oem-6.86.8.0-1006.6UBUNTU-CVE-2023-52659
Ubuntu:24.04:LTSlinux-oracle6.8.0-1006.6USN-6878-1
Ubuntu:24.04:LTSlinux-oracle6.8.0-1006.6UBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2023-52659
Ubuntu:24.04:LTSlinux-raspi6.8.0-1005.5USN-6816-1
Ubuntu:24.04:LTSlinux-raspi6.8.0-1005.5UBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-52659
Ubuntu:24.04:LTSlinux-riscv6.8.0-35.35.1UBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-52659
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2023-52659

Affected products (as reported)

VendorProductVersions
Linux Linux 6c3211796326a9d35618b866826ca556c8f008a8 – before 325956b0173f11e98f90462be4829a8b8b0682ce6c3211796326a9d35618b866826ca556c8f008a8 – before 7e1471888a5e6e846e9b4d306e5327db2b58e64e6c3211796326a9d35618b866826ca556c8f008a8 – before 814305b5c23cb815ada68d43019f39050472b25f6c3211796326a9d35618b866826ca556c8f008a8 – before 8e5647a723c49d73b9f108a8bb38e8c29d3948ea
Linux Linux 6.5

References