Vulnerability · Published Oct 21, 2024 · Assigned by Linux

CVE-2024-47736erofs: handle overlapped pclusters out of crafted images properly

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 8% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 92.2% 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: erofs: handle overlapped pclusters out of crafted images properly syzbot reported a task hang issue due to a deadlock case where it is waiting for the folio lock of a cached folio that will be used for cache I/Os. After looking into the crafted fuzzed image, I found it's formed with several overlapped big pclusters as below: Ext: logical offset | length : physical offset | length 0: 0.. 16384 | 16384 : 151552.. 167936 | 16384 1: 16384.. 32768 | 16384 : 155648.. 172032 | 16384 2: 32768.. 49152 | 16384 : 537223168.. 537239552 | 16384 ... Here, extent 0/1 are physically overlapped although it's entirely _impossible_ for normal filesystem images generated by mkfs. First, managed folios containing compressed data will be marked as up-to-date and then unlocked immediately (unlike in-place folios) when compressed I/Os are complete. If physical blocks are not submitted in the incremental order, there should be separate BIOs to avoid dependency issues. However, the current code mis-arranges z_erofs_fill_bio_vec() and BIO submission which causes unexpected BIO waits. Second, managed folios will be connected to their own pclusters for efficient inter-queries. However, this is somewhat hard to implement easily if overlapped big pclusters exist. Again, these only appear in fuzzed images so let's simply fall back to temporary short-lived pages for correctness. Additionally, it justifies that referenced managed folios cannot be truncated for now and reverts part of commit 2080ca1ed3e4 ("erofs: tidy up `struct z_erofs_bvec`") for simplicity although it shouldn't be any difference.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.170-1DEBIAN-CVE-2024-47736
Debian:13linux6.11.2-1DEBIAN-CVE-2024-47736
Debian:14linux6.11.2-1DEBIAN-CVE-2024-47736
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux6.8.0-60.63UBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux6.8.0-60.63USN-7513-1
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-aws6.8.0-1029.31USN-7513-1
Ubuntu:24.04:LTSlinux-aws6.8.0-1029.31UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1029.31~22.04.1USN-7513-1
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1029.31~22.04.1UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-azure6.8.0-1029.34UBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-azure6.8.0-1029.34USN-7513-3
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-azure-6.116.11.0-1012.12~24.04.1UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1029.34~22.04.1USN-7513-3
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1029.34~22.04.1UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-azure-nvidia6.8.0-1016.17UBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-azure-nvidia6.8.0-1016.17USN-7522-1
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-gcp6.8.0-1030.32USN-7515-2
Ubuntu:24.04:LTSlinux-gcp6.8.0-1030.32UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-gcp-6.116.11.0-1011.11~24.04.1UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1030.32~22.04.1USN-7515-2
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1030.32~22.04.1UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-gke6.8.0-1025.29USN-7515-1
Ubuntu:24.04:LTSlinux-gke6.8.0-1025.29UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1012.14USN-7515-2
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1012.14UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-60.63~22.04.1USN-7513-4
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-60.63~22.04.1UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-ibm6.8.0-1026.26UBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-ibm6.8.0-1026.26USN-7513-1
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1026.26~22.04.1UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-60.63.1UBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-60.63.1USN-7513-1
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-60.63.1~22.04.1USN-7513-1
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-60.63.1~22.04.1UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1028.31UBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1028.31USN-7514-1
Ubuntu:24.04:LTSlinux-nvidia-6.116.11.0-1007.7UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1028.31~22.04.1USN-7514-1
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1028.31~22.04.1UBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1028.31.1USN-7514-1
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1028.31.1UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1008.8UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-oem-6.116.11.0-1015.15UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-oem-6.86.8.0-1028.28UBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-oem-6.86.8.0-1028.28USN-7513-3
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-oracle6.8.0-1026.27USN-7513-1
Ubuntu:24.04:LTSlinux-oracle6.8.0-1026.27UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1026.27~22.04.1UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1026.27~22.04.1USN-7513-5
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-raspi6.8.0-1028.32UBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-raspi6.8.0-1028.32USN-7524-1
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-riscv6.8.0-60.63.1UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-62.65~22.04.1UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2024-47736
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1017.18UBUNTU-CVE-2024-47736
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2024-47736

Affected products (as reported)

VendorProductVersions
Linux Linux 8e6c8fa9f2e95c88a642521a5da19a8e31748846 – before c1172e65aad4b115392ea4c6e61e56e5b9b69df48e6c8fa9f2e95c88a642521a5da19a8e31748846 – before 1bf7e414cac303c9aec1be67872e19be8b64980c8e6c8fa9f2e95c88a642521a5da19a8e31748846 – before b9b30af0e86ffb485301ecd83b9129c9dfb7ebf88e6c8fa9f2e95c88a642521a5da19a8e31748846 – before 9cfa199bcbbbba31cbf97b2786f44f4464f3f29a8e6c8fa9f2e95c88a642521a5da19a8e31748846 – before 9e2f9d34dd12e6e5b244ec488bcebd0c2d566c50
Linux Linux 5.13

References