CVE & CISA-KEV Catalog

CVE-2024-26616

HIGH
7.8
CVSS v3
NVD

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: scrub: avoid use-after-free when chunk length is not 64K aligned [BUG] There is a bug report that, on a ext4-converted btrfs, scrub leads to various problems, including: - "unable to find chunk map" errors BTRFS info (device vdb): scrub: started on devid 1 BTRFS critical (device vdb): unable to find chunk map for logical 2214744064 length 4096 BTRFS critical (device vdb): unable to find chunk map for logical 2214744064 length 45056 This would lead to unrepariable errors. - Use-after-free KASAN reports: ================================================================== BUG: KASAN: slab-use-after-free in __blk_rq_map_sg+0x18f/0x7c0 Read of size 8 at addr ffff8881013c9040 by task btrfs/909 CPU: 0 PID: 909 Comm: btrfs Not tainted 6.7.0-x64v3-dbg #11 c50636e9419a8354555555245df535e380563b2b Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 2023.11-2 12/24/2023 Call Trace: <TASK> dump_stack_lvl+0x43/0x60 print_report+0xcf/0x640 kasan_report+0xa6/0xd0 __blk_rq_map_sg+0x18f/0x7c0 virtblk_prep_rq.isra.0+0x215/0x6a0 [virtio_blk 19a65eeee9ae6fcf02edfad39bb9ddee07dcdaff] virtio_queue_rqs+0xc4/0x310 [virtio_blk 19a65eeee9ae6fcf02edfad39bb9ddee07dcdaff] blk_mq_flush_plug_list.part.0+0x780/0x860 __blk_flush_plug+0x1ba/0x220 blk_finish_plug+0x3b/0x60 submit_initial_group_read+0x10a/0x290 [btrfs e57987a360bed82fe8756dcd3e0de5406ccfe965] flush_scrub_stripes+0x38e/0x430 [btrfs e57987a360bed82fe8756dcd3e0de5406ccfe965] scrub_stripe+0x82a/0xae0 [btrfs e57987a360bed82fe8756dcd3e0de5406ccfe965] scrub_chunk+0x178/0x200 [btrfs e57987a360bed82fe8756dcd3e0de5406ccfe965] scrub_enumerate_chunks+0x4bc/0xa30 [btrfs e57987a360bed82fe8756dcd3e0de5406ccfe965] btrfs_scrub_dev+0x398/0x810 [btrfs e57987a360bed82fe8756dcd3e0de5406ccfe965] btrfs_ioctl+0x4b9/0x3020 [btrfs e57987a360bed82fe8756dcd3e0de5406ccfe965] __x64_sys_ioctl+0xbd/0x100 do_syscall_64+0x5d/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b RIP: 0033:0x7f47e5e0952b - Crash, mostly due to above use-after-free [CAUSE] The converted fs has the following data chunk layout: item 2 key (FIRST_CHUNK_TREE CHUNK_ITEM 2214658048) itemoff 16025 itemsize 80 length 86016 owner 2 stripe_len 65536 type DATA|single For above logical bytenr 2214744064, it's at the chunk end (2214658048 + 86016 = 2214744064). This means btrfs_submit_bio() would split the bio, and trigger endio function for both of the two halves. However scrub_submit_initial_read() would only expect the endio function to be called once, not any more. This means the first endio function would already free the bbio::bio, leaving the bvec freed, thus the 2nd endio call would lead to use-after-free. [FIX] - Make sure scrub_read_endio() only updates bits in its range Since we may read less than 64K at the end of the chunk, we should not touch the bits beyond chunk boundary. - Make sure scrub_submit_initial_read() only to read the chunk range This is done by calculating the real number of sectors we need to read, and add sector-by-sector to the bio. Thankfully the scrub read repair path won't need extra fixes: - scrub_stripe_submit_repair_read() With above fixes, we won't update error bit for range beyond chunk, thus scrub_stripe_submit_repair_read() should never submit any read beyond the chunk.

How to fix

Remediation Available
linuxDebian
Fixed in:6.6.15-1CVE-2024-26616
Fixed in:6.6.15-1CVE-2024-26616
linuxUbuntu
Fixed in:6.5.0-41.41USN-6818-1
linux-awsUbuntu
Fixed in:6.5.0-1021.21USN-6819-2
linux-azureUbuntu
Fixed in:6.5.0-1022.23USN-6819-1
linux-azure-6.5Ubuntu
Fixed in:6.5.0-1022.23~22.04.1USN-6819-1
linux-gcpUbuntu
Fixed in:6.5.0-1022.24USN-6818-1
linux-gcp-6.5Ubuntu
Fixed in:6.5.0-1022.24~22.04.1USN-6818-1
linux-hwe-6.5Ubuntu
Fixed in:6.5.0-41.41~22.04.2USN-6818-4
linux-image-6.5.0-1015-starfiveUbuntu
Fixed in:6.5.0-1015.16~22.04.1USN-6819-1
Fixed in:6.5.0-1015.16USN-6819-1
linux-image-6.5.0-1017-laptopUbuntu
Fixed in:6.5.0-1017.20USN-6818-2
linux-image-6.5.0-1018-raspiUbuntu
Fixed in:6.5.0-1018.21USN-6818-1
linux-image-6.5.0-1021-awsUbuntu
Fixed in:6.5.0-1021.21USN-6819-2
linux-image-6.5.0-1021-nvidiaUbuntu
Fixed in:6.5.0-1021.22USN-6818-3
linux-image-6.5.0-1021-nvidia-64kUbuntu
Fixed in:6.5.0-1021.22USN-6818-3
linux-image-6.5.0-1022-azureUbuntu
Fixed in:6.5.0-1022.23~22.04.1USN-6819-1
Fixed in:6.5.0-1022.23USN-6819-1
linux-image-6.5.0-1022-azure-fdeUbuntu
Fixed in:6.5.0-1022.23~22.04.1USN-6819-1
Fixed in:6.5.0-1022.23USN-6819-1
linux-image-6.5.0-1022-gcpUbuntu
Fixed in:6.5.0-1022.24~22.04.1USN-6818-1
Fixed in:6.5.0-1022.24USN-6818-1
linux-image-6.5.0-1024-oemUbuntu
Fixed in:6.5.0-1024.25USN-6819-3
linux-image-6.5.0-1024-oracleUbuntu
Fixed in:6.5.0-1024.24~22.04.1USN-6819-4
Fixed in:6.5.0-1024.24USN-6819-2
linux-image-6.5.0-1024-oracle-64kUbuntu
Fixed in:6.5.0-1024.24~22.04.1USN-6819-4
Fixed in:6.5.0-1024.24USN-6819-2
linux-image-6.5.0-41-genericUbuntu
Fixed in:6.5.0-41.41~22.04.2USN-6818-4
Fixed in:6.5.0-41.41USN-6818-1
linux-image-6.5.0-41-generic-64kUbuntu
Fixed in:6.5.0-41.41~22.04.2USN-6818-4
Fixed in:6.5.0-41.41USN-6818-1
linux-image-6.5.0-41-lowlatencyUbuntu
Fixed in:6.5.0-41.41.1~22.04.1USN-6818-1
Fixed in:6.5.0-41.41.1USN-6818-1
linux-image-6.5.0-41-lowlatency-64kUbuntu
Fixed in:6.5.0-41.41.1~22.04.1USN-6818-1
Fixed in:6.5.0-41.41.1USN-6818-1
linux-image-awsUbuntu
Fixed in:6.5.0.1021.21USN-6819-2
linux-image-azureUbuntu
Fixed in:6.5.0.1022.23~22.04.1USN-6819-1
Fixed in:6.5.0.1022.26USN-6819-1
linux-image-azure-fdeUbuntu
Fixed in:6.5.0.1022.23~22.04.1USN-6819-1
Fixed in:6.5.0.1022.26USN-6819-1
linux-image-gcpUbuntu
Fixed in:6.5.0.1022.24~22.04.1USN-6818-1
Fixed in:6.5.0.1022.24USN-6818-1
linux-image-genericUbuntu
Fixed in:6.5.0.41.41USN-6818-1
linux-image-generic-64kUbuntu
Fixed in:6.5.0.41.41USN-6818-1
linux-image-generic-64k-hwe-22.04Ubuntu
Fixed in:6.5.0.41.41~22.04.2USN-6818-4
linux-image-generic-hwe-22.04Ubuntu
Fixed in:6.5.0.41.41~22.04.2USN-6818-4
linux-image-generic-lpaeUbuntu
Fixed in:6.5.0.41.41USN-6818-1
linux-image-kvmUbuntu
Fixed in:6.5.0.41.41USN-6818-1
linux-image-laptop-23.10Ubuntu
Fixed in:6.5.0.1017.20USN-6818-2
linux-image-lowlatencyUbuntu
Fixed in:6.5.0.41.41.1USN-6818-1
linux-image-lowlatency-64kUbuntu
Fixed in:6.5.0.41.41.1USN-6818-1
linux-image-lowlatency-64k-hwe-22.04Ubuntu
Fixed in:6.5.0.41.41.1~22.04.1USN-6818-1
linux-image-lowlatency-hwe-22.04Ubuntu
Fixed in:6.5.0.41.41.1~22.04.1USN-6818-1
linux-image-nvidia-6.5Ubuntu
Fixed in:6.5.0.1021.29USN-6818-3
linux-image-nvidia-64k-6.5Ubuntu
Fixed in:6.5.0.1021.29USN-6818-3
linux-image-nvidia-64k-hwe-22.04Ubuntu
Fixed in:6.5.0.1021.29USN-6818-3
linux-image-nvidia-hwe-22.04Ubuntu
Fixed in:6.5.0.1021.29USN-6818-3
linux-image-oem-22.04Ubuntu
Fixed in:6.5.0.1024.26USN-6819-3
linux-image-oem-22.04aUbuntu
Fixed in:6.5.0.1024.26USN-6819-3
linux-image-oem-22.04bUbuntu
Fixed in:6.5.0.1024.26USN-6819-3
linux-image-oem-22.04cUbuntu
Fixed in:6.5.0.1024.26USN-6819-3
linux-image-oem-22.04dUbuntu
Fixed in:6.5.0.1024.26USN-6819-3
linux-image-oracleUbuntu
Fixed in:6.5.0.1024.24~22.04.1USN-6819-4
Fixed in:6.5.0.1024.26USN-6819-2
linux-image-oracle-64kUbuntu
Fixed in:6.5.0.1024.24~22.04.1USN-6819-4
Fixed in:6.5.0.1024.26USN-6819-2
linux-image-raspiUbuntu
Fixed in:6.5.0.1018.19USN-6818-1
linux-image-raspi-nolpaeUbuntu
Fixed in:6.5.0.1018.19USN-6818-1
linux-image-starfiveUbuntu
Fixed in:6.5.0.1015.16~22.04.1USN-6819-1
Fixed in:6.5.0.1015.17USN-6819-1
linux-image-virtualUbuntu
Fixed in:6.5.0.41.41USN-6818-1
linux-image-virtual-hwe-22.04Ubuntu
Fixed in:6.5.0.41.41~22.04.2USN-6818-4
linux-laptopUbuntu
Fixed in:6.5.0-1017.20USN-6818-2
linux-lowlatencyUbuntu
Fixed in:6.5.0-41.41.1USN-6818-1
linux-lowlatency-hwe-6.5Ubuntu
Fixed in:6.5.0-41.41.1~22.04.1USN-6818-1
linux-nvidia-6.5Ubuntu
Fixed in:6.5.0-1021.22USN-6818-3
linux-oem-6.5Ubuntu
Fixed in:6.5.0-1024.25USN-6819-3
linux-oracleUbuntu
Fixed in:6.5.0-1024.24USN-6819-2
linux-oracle-6.5Ubuntu
Fixed in:6.5.0-1024.24~22.04.1USN-6819-4
linux-raspiUbuntu
Fixed in:6.5.0-1018.21USN-6818-1
linux-starfiveUbuntu
Fixed in:6.5.0-1015.16USN-6819-1
linux-starfive-6.5Ubuntu
Fixed in:6.5.0-1015.16~22.04.1USN-6819-1

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploit Intelligence

0.29%probability of exploitation in 30 days
21stpercentile

Low risk: more likely to be exploited than 21% of all known CVEs.

References

Related Vulnerabilities

Other CWE-416 (Use After Free) vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2019-0708Critical9.8100%KEV + Ransom-
CVE-2021-31166Critical9.8100%KEVFix
CVE-2015-5119Critical9.899%KEV-
CVE-2010-3962High8.197%KEV-
CVE-2015-0313Critical9.896%KEVFix
CVE-2017-9798High7.595%-Fix
Embed a live status badge for CVE-2024-26616
CVE-2024-26616 severity badge

Markdown

[![CVE-2024-26616](https://tridentstack.com/cve/badge/CVE-2024-26616.svg)](https://tridentstack.com/cve/CVE-2024-26616)

HTML

<a href="https://tridentstack.com/cve/CVE-2024-26616"><img src="https://tridentstack.com/cve/badge/CVE-2024-26616.svg" alt="CVE-2024-26616"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

Start free

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-12-12.