CVE & CISA-KEV Catalog

CVE-2024-40962

MEDIUM
5.5
CVSS v3
NVD

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: allocate dummy checksums for zoned NODATASUM writes Shin'ichiro reported that when he's running fstests' test-case btrfs/167 on emulated zoned devices, he's seeing the following NULL pointer dereference in 'btrfs_zone_finish_endio()': Oops: general protection fault, probably for non-canonical address 0xdffffc0000000011: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000088-0x000000000000008f] CPU: 4 PID: 2332440 Comm: kworker/u80:15 Tainted: G W 6.10.0-rc2-kts+ #4 Hardware name: Supermicro Super Server/X11SPi-TF, BIOS 3.3 02/21/2020 Workqueue: btrfs-endio-write btrfs_work_helper [btrfs] RIP: 0010:btrfs_zone_finish_endio.part.0+0x34/0x160 [btrfs] RSP: 0018:ffff88867f107a90 EFLAGS: 00010206 RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff893e5534 RDX: 0000000000000011 RSI: 0000000000000004 RDI: 0000000000000088 RBP: 0000000000000002 R08: 0000000000000001 R09: ffffed1081696028 R10: ffff88840b4b0143 R11: ffff88834dfff600 R12: ffff88840b4b0000 R13: 0000000000020000 R14: 0000000000000000 R15: ffff888530ad5210 FS: 0000000000000000(0000) GS:ffff888e3f800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f87223fff38 CR3: 00000007a7c6a002 CR4: 00000000007706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <TASK> ? __die_body.cold+0x19/0x27 ? die_addr+0x46/0x70 ? exc_general_protection+0x14f/0x250 ? asm_exc_general_protection+0x26/0x30 ? do_raw_read_unlock+0x44/0x70 ? btrfs_zone_finish_endio.part.0+0x34/0x160 [btrfs] btrfs_finish_one_ordered+0x5d9/0x19a0 [btrfs] ? __pfx_lock_release+0x10/0x10 ? do_raw_write_lock+0x90/0x260 ? __pfx_do_raw_write_lock+0x10/0x10 ? __pfx_btrfs_finish_one_ordered+0x10/0x10 [btrfs] ? _raw_write_unlock+0x23/0x40 ? btrfs_finish_ordered_zoned+0x5a9/0x850 [btrfs] ? lock_acquire+0x435/0x500 btrfs_work_helper+0x1b1/0xa70 [btrfs] ? __schedule+0x10a8/0x60b0 ? __pfx___might_resched+0x10/0x10 process_one_work+0x862/0x1410 ? __pfx_lock_acquire+0x10/0x10 ? __pfx_process_one_work+0x10/0x10 ? assign_work+0x16c/0x240 worker_thread+0x5e6/0x1010 ? __pfx_worker_thread+0x10/0x10 kthread+0x2c3/0x3a0 ? trace_irq_enable.constprop.0+0xce/0x110 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x31/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Enabling CONFIG_BTRFS_ASSERT revealed the following assertion to trigger: assertion failed: !list_empty(&ordered->list), in fs/btrfs/zoned.c:1815 This indicates, that we're missing the checksums list on the ordered_extent. As btrfs/167 is doing a NOCOW write this is to be expected. Further analysis with drgn confirmed the assumption: >>> inode = prog.crashed_thread().stack_trace()[11]['ordered'].inode >>> btrfs_inode = drgn.container_of(inode, "struct btrfs_inode", \ "vfs_inode") >>> print(btrfs_inode.flags) (u32)1 As zoned emulation mode simulates conventional zones on regular devices, we cannot use zone-append for writing. But we're only attaching dummy checksums if we're doing a zone-append write. So for NOCOW zoned data writes on conventional zones, also attach a dummy checksum.

How to fix

Remediation Available
linuxDebian
Fixed in:6.9.7-1CVE-2024-40962
Fixed in:6.9.7-1CVE-2024-40962
linuxUbuntu
Fixed in:6.8.0-44.44USN-6999-1
linux-awsUbuntu
Fixed in:6.8.0-1015.16USN-6999-1
linux-azureUbuntu
Fixed in:6.8.0-1014.16USN-7004-1
linux-gcpUbuntu
Fixed in:6.8.0-1014.16USN-6999-1
linux-gkeUbuntu
Fixed in:6.8.0-1010.13USN-6999-1
linux-hwe-6.8Ubuntu
Fixed in:6.8.0-45.45~22.04.1USN-7029-1
linux-ibmUbuntu
Fixed in:6.8.0-1012.12USN-6999-1
linux-image-6.8.0-1010-gkeUbuntu
Fixed in:6.8.0-1010.13USN-6999-1
linux-image-6.8.0-1011-raspiUbuntu
Fixed in:6.8.0-1011.12USN-6999-2
linux-image-6.8.0-1012-ibmUbuntu
Fixed in:6.8.0-1012.12USN-6999-1
linux-image-6.8.0-1012-oemUbuntu
Fixed in:6.8.0-1012.12USN-6999-1
linux-image-6.8.0-1012-oracleUbuntu
Fixed in:6.8.0-1012.12USN-6999-1
linux-image-6.8.0-1012-oracle-64kUbuntu
Fixed in:6.8.0-1012.12USN-6999-1
linux-image-6.8.0-1013-nvidiaUbuntu
Fixed in:6.8.0-1013.14~22.04.1USN-7005-2
Fixed in:6.8.0-1013.14USN-7005-1
linux-image-6.8.0-1013-nvidia-64kUbuntu
Fixed in:6.8.0-1013.14~22.04.1USN-7005-2
Fixed in:6.8.0-1013.14USN-7005-1
linux-image-6.8.0-1013-nvidia-lowlatencyUbuntu
Fixed in:6.8.0-1013.14.1USN-7005-1
linux-image-6.8.0-1013-nvidia-lowlatency-64kUbuntu
Fixed in:6.8.0-1013.14.1USN-7005-1
linux-image-6.8.0-1014-azureUbuntu
Fixed in:6.8.0-1014.16USN-7004-1
linux-image-6.8.0-1014-azure-fdeUbuntu
Fixed in:6.8.0-1014.16USN-7004-1
linux-image-6.8.0-1014-gcpUbuntu
Fixed in:6.8.0-1014.16USN-6999-1
linux-image-6.8.0-1015-awsUbuntu
Fixed in:6.8.0-1015.16USN-6999-1
linux-image-6.8.0-44-genericUbuntu
Fixed in:6.8.0-44.44USN-6999-1
linux-image-6.8.0-44-generic-64kUbuntu
Fixed in:6.8.0-44.44USN-6999-1
linux-image-6.8.0-44-lowlatencyUbuntu
Fixed in:6.8.0-44.44.1~22.04.1USN-7008-1
Fixed in:6.8.0-44.44.1USN-6999-1
linux-image-6.8.0-44-lowlatency-64kUbuntu
Fixed in:6.8.0-44.44.1~22.04.1USN-7008-1
Fixed in:6.8.0-44.44.1USN-6999-1
linux-image-6.8.0-45-genericUbuntu
Fixed in:6.8.0-45.45~22.04.1USN-7029-1
linux-image-6.8.0-45-generic-64kUbuntu
Fixed in:6.8.0-45.45~22.04.1USN-7029-1
linux-image-awsUbuntu
Fixed in:6.8.0-1015.16USN-6999-1
linux-image-azureUbuntu
Fixed in:6.8.0-1014.16USN-7004-1
linux-image-azure-fdeUbuntu
Fixed in:6.8.0-1014.16USN-7004-1
linux-image-gcpUbuntu
Fixed in:6.8.0-1014.16USN-6999-1
linux-image-genericUbuntu
Fixed in:6.8.0-44.44USN-6999-1
linux-image-generic-64kUbuntu
Fixed in:6.8.0-44.44USN-6999-1
linux-image-generic-64k-hwe-22.04Ubuntu
Fixed in:6.8.0-45.45~22.04.1USN-7029-1
linux-image-generic-64k-hwe-24.04Ubuntu
Fixed in:6.8.0-44.44USN-6999-1
linux-image-generic-hwe-22.04Ubuntu
Fixed in:6.8.0-45.45~22.04.1USN-7029-1
linux-image-generic-hwe-24.04Ubuntu
Fixed in:6.8.0-44.44USN-6999-1
linux-image-generic-lpaeUbuntu
Fixed in:6.8.0-44.44USN-6999-1
linux-image-gkeUbuntu
Fixed in:6.8.0-1010.13USN-6999-1
linux-image-ibmUbuntu
Fixed in:6.8.0-1012.12USN-6999-1
linux-image-ibm-classicUbuntu
Fixed in:6.8.0-1012.12USN-6999-1
linux-image-ibm-lts-24.04Ubuntu
Fixed in:6.8.0-1012.12USN-6999-1
linux-image-kvmUbuntu
Fixed in:6.8.0-44.44USN-6999-1
linux-image-lowlatencyUbuntu
Fixed in:6.8.0-44.44.1USN-6999-1
linux-image-lowlatency-64kUbuntu
Fixed in:6.8.0-44.44.1USN-6999-1
linux-image-lowlatency-64k-hwe-22.04Ubuntu
Fixed in:6.8.0-44.44.1~22.04.1USN-7008-1
linux-image-lowlatency-hwe-22.04Ubuntu
Fixed in:6.8.0-44.44.1~22.04.1USN-7008-1
linux-image-nvidiaUbuntu
Fixed in:6.8.0-1013.13USN-7005-1
linux-image-nvidia-6.8Ubuntu
Fixed in:6.8.0-1013.14~22.04.1USN-7005-2
linux-image-nvidia-64kUbuntu
Fixed in:6.8.0-1013.13USN-7005-1
linux-image-nvidia-64k-6.8Ubuntu
Fixed in:6.8.0-1013.14~22.04.1USN-7005-2
linux-image-nvidia-lowlatencyUbuntu
Fixed in:6.8.0-1013.14.1USN-7005-1
linux-image-nvidia-lowlatency-64kUbuntu
Fixed in:6.8.0-1013.14.1USN-7005-1
linux-image-oem-22.04Ubuntu
Fixed in:6.8.0-45.45~22.04.1USN-7029-1
linux-image-oem-22.04aUbuntu
Fixed in:6.8.0-45.45~22.04.1USN-7029-1
linux-image-oem-22.04bUbuntu
Fixed in:6.8.0-45.45~22.04.1USN-7029-1
linux-image-oem-22.04cUbuntu
Fixed in:6.8.0-45.45~22.04.1USN-7029-1
linux-image-oem-22.04dUbuntu
Fixed in:6.8.0-45.45~22.04.1USN-7029-1
linux-image-oracleUbuntu
Fixed in:6.8.0-1012.12USN-6999-1
linux-image-oracle-64kUbuntu
Fixed in:6.8.0-1012.12USN-6999-1
linux-image-raspiUbuntu
Fixed in:6.8.0-1011.12USN-6999-2
linux-image-virtualUbuntu
Fixed in:6.8.0-44.44USN-6999-1
linux-image-virtual-hwe-22.04Ubuntu
Fixed in:6.8.0-45.45~22.04.1USN-7029-1
linux-image-virtual-hwe-24.04Ubuntu
Fixed in:6.8.0-44.44USN-6999-1
linux-lowlatencyUbuntu
Fixed in:6.8.0-44.44.1USN-6999-1
linux-lowlatency-hwe-6.8Ubuntu
Fixed in:6.8.0-44.44.1~22.04.1USN-7008-1
linux-nvidiaUbuntu
Fixed in:6.8.0-1013.14USN-7005-1
linux-nvidia-6.8Ubuntu
Fixed in:6.8.0-1013.14~22.04.1USN-7005-2
linux-nvidia-lowlatencyUbuntu
Fixed in:6.8.0-1013.14.1USN-7005-1
linux-oem-6.8Ubuntu
Fixed in:6.8.0-1012.12USN-6999-1
linux-oracleUbuntu
Fixed in:6.8.0-1012.12USN-6999-1
linux-raspiUbuntu
Fixed in:6.8.0-1011.12USN-6999-2

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

ConfidentialityNone
IntegrityNone
AvailabilityHigh

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

Exploit Intelligence

0.24%probability of exploitation in 30 days
15thpercentile

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

References

Related Vulnerabilities

Other CWE-476 (NULL Pointer Dereference) vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2023-21758High7.592%-Fix
CVE-2023-21547High7.588%-Fix
CVE-2014-3470Medium4.386%-Fix
CVE-2021-44224High8.282%-Fix
CVE-2016-0742High7.582%-Fix
CVE-2009-1386Medium5.080%-Fix
Embed a live status badge for CVE-2024-40962
CVE-2024-40962 severity badge

Markdown

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

HTML

<a href="https://tridentstack.com/cve/CVE-2024-40962"><img src="https://tridentstack.com/cve/badge/CVE-2024-40962.svg" alt="CVE-2024-40962"></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 2025-01-07.