CVE-2024-40962: btrfs: zoned: allocate dummy checksums for zoned NODATASUM writes
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 'btrfszonefinishendio()':
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 btrfsworkhelper [btrfs] RIP: 0010:btrfszonefinishendio.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> ? diebody.cold+0x19/0x27 ? dieaddr+0x46/0x70 ? excgeneralprotection+0x14f/0x250 ? asmexcgeneralprotection+0x26/0x30 ? dorawreadunlock+0x44/0x70 ? btrfszonefinishendio.part.0+0x34/0x160 [btrfs] btrfsfinishoneordered+0x5d9/0x19a0 [btrfs] ? pfxlockrelease+0x10/0x10 ? dorawwritelock+0x90/0x260 ? pfxdorawwritelock+0x10/0x10 ? pfxbtrfsfinishoneordered+0x10/0x10 [btrfs] ? rawwriteunlock+0x23/0x40 ? btrfsfinishorderedzoned+0x5a9/0x850 [btrfs] ? lockacquire+0x435/0x500 btrfsworkhelper+0x1b1/0xa70 [btrfs] ? schedule+0x10a8/0x60b0 ? pfxmightresched+0x10/0x10 processonework+0x862/0x1410 ? pfxlockacquire+0x10/0x10 ? pfxprocessonework+0x10/0x10 ? assignwork+0x16c/0x240 workerthread+0x5e6/0x1010 ? pfxworkerthread+0x10/0x10 kthread+0x2c3/0x3a0 ? traceirqenable.constprop.0+0xce/0x110 ? pfxkthread+0x10/0x10 retfromfork+0x31/0x70 ? pfxkthread+0x10/0x10 retfromforkasm+0x1a/0x30 </TASK>
Enabling CONFIGBTRFSASSERT revealed the following assertion to trigger:
assertion failed: !listempty(&ordered->list), in fs/btrfs/zoned.c:1815
This indicates, that we're missing the checksums list on the orderedextent. As btrfs/167 is doing a NOCOW write this is to be expected.
Further analysis with drgn confirmed the assumption:
>>> inode = prog.crashedthread().stacktrace()[11]['ordered'].inode >>> btrfsinode = drgn.containerof(inode, "struct btrfsinode", \ "vfsinode") >>> print(btrfsinode.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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-40962?
CVE-2024-40962 has been classified with a severity rating indicating potential impacts on systems running vulnerable versions of the Linux kernel.
How can I fix CVE-2024-40962?
To fix CVE-2024-40962, upgrade the Linux kernel to a version that addresses this vulnerability, such as those released after the patches.
What versions of the Linux kernel are affected by CVE-2024-40962?
CVE-2024-40962 affects various versions of the Linux kernel, specifically between 6.5 and 6.6.36, as well as specific release candidates like 6.10-rc1 to 6.10-rc4.
Is CVE-2024-40962 related to data integrity issues?
Yes, CVE-2024-40962 is related to potential data integrity issues due to NULL pointer dereferences when handling zoned NODATASUM writes in the btrfs file system.
Who reported the vulnerability identified as CVE-2024-40962?
The vulnerability CVE-2024-40962 was reported by a researcher named Shin'ichiro.