Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2024-35949— btrfs: make sure that WRITTEN is set on all metadata blocks

EPSS 0.01% · P2

Affected Version Matrix 8

VendorProductVersion RangeStatus
LinuxLinux85d8a826c7cde17f9cca9c4debecb4538bdb6573< 9dff3e36ea89e8003516841c27c45af562b6ef44affected
85d8a826c7cde17f9cca9c4debecb4538bdb6573< ef3ba8ce8cf7075b716aa4afcefc3034215878eeaffected
85d8a826c7cde17f9cca9c4debecb4538bdb6573< e03418abde871314e1a3a550f4c8afb7b89cb273affected
6.5affected
< 6.5unaffected
6.6.85≤ 6.6.*unaffected
6.8.10≤ 6.8.*unaffected
6.9≤ *unaffected
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2024-35949

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
btrfs: make sure that WRITTEN is set on all metadata blocks
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: make sure that WRITTEN is set on all metadata blocks We previously would call btrfs_check_leaf() if we had the check integrity code enabled, which meant that we could only run the extended leaf checks if we had WRITTEN set on the header flags. This leaves a gap in our checking, because we could end up with corruption on disk where WRITTEN isn't set on the leaf, and then the extended leaf checks don't get run which we rely on to validate all of the item pointers to make sure we don't access memory outside of the extent buffer. However, since 732fab95abe2 ("btrfs: check-integrity: remove CONFIG_BTRFS_FS_CHECK_INTEGRITY option") we no longer call btrfs_check_leaf() from btrfs_mark_buffer_dirty(), which means we only ever call it on blocks that are being written out, and thus have WRITTEN set, or that are being read in, which should have WRITTEN set. Add checks to make sure we have WRITTEN set appropriately, and then make sure __btrfs_check_leaf() always does the item checking. This will protect us from file systems that have been corrupted and no longer have WRITTEN set on some of the blocks. This was hit on a crafted image tweaking the WRITTEN bit and reported by KASAN as out-of-bound access in the eb accessors. The example is a dir item at the end of an eb. [2.042] BTRFS warning (device loop1): bad eb member start: ptr 0x3fff start 30572544 member offset 16410 size 2 [2.040] general protection fault, probably for non-canonical address 0xe0009d1000000003: 0000 [#1] PREEMPT SMP KASAN NOPTI [2.537] KASAN: maybe wild-memory-access in range [0x0005088000000018-0x000508800000001f] [2.729] CPU: 0 PID: 2587 Comm: mount Not tainted 6.8.2 #1 [2.729] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 [2.621] RIP: 0010:btrfs_get_16+0x34b/0x6d0 [2.621] RSP: 0018:ffff88810871fab8 EFLAGS: 00000206 [2.621] RAX: 0000a11000000003 RBX: ffff888104ff8720 RCX: ffff88811b2288c0 [2.621] RDX: dffffc0000000000 RSI: ffffffff81dd8aca RDI: ffff88810871f748 [2.621] RBP: 000000000000401a R08: 0000000000000001 R09: ffffed10210e3ee9 [2.621] R10: ffff88810871f74f R11: 205d323430333737 R12: 000000000000001a [2.621] R13: 000508800000001a R14: 1ffff110210e3f5d R15: ffffffff850011e8 [2.621] FS: 00007f56ea275840(0000) GS:ffff88811b200000(0000) knlGS:0000000000000000 [2.621] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [2.621] CR2: 00007febd13b75c0 CR3: 000000010bb50000 CR4: 00000000000006f0 [2.621] Call Trace: [2.621] <TASK> [2.621] ? show_regs+0x74/0x80 [2.621] ? die_addr+0x46/0xc0 [2.621] ? exc_general_protection+0x161/0x2a0 [2.621] ? asm_exc_general_protection+0x26/0x30 [2.621] ? btrfs_get_16+0x33a/0x6d0 [2.621] ? btrfs_get_16+0x34b/0x6d0 [2.621] ? btrfs_get_16+0x33a/0x6d0 [2.621] ? __pfx_btrfs_get_16+0x10/0x10 [2.621] ? __pfx_mutex_unlock+0x10/0x10 [2.621] btrfs_match_dir_item_name+0x101/0x1a0 [2.621] btrfs_lookup_dir_item+0x1f3/0x280 [2.621] ? __pfx_btrfs_lookup_dir_item+0x10/0x10 [2.621] btrfs_get_tree+0xd25/0x1910 [ copy more details from report ]
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于指针可以访问缓冲区之外的内存。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 85d8a826c7cde17f9cca9c4debecb4538bdb6573 ~ 9dff3e36ea89e8003516841c27c45af562b6ef44 -
LinuxLinux 6.5 -

II. Public POCs for CVE-2024-35949

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-35949

登录查看更多情报信息。

Same Patch Batch · Linux · 2024-05-20 · 62 CVEs total

CVE-2024-35969ipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr
CVE-2024-35955kprobes: Fix possible use-after-free issue on kprobe registration
CVE-2024-35952drm/ast: Fix soft lockup
CVE-2024-35953accel/ivpu: Fix deadlock in context_xa
CVE-2024-35954scsi: sg: Avoid sg device teardown race
CVE-2024-35964Bluetooth: ISO: Fix not validating setsockopt user input
CVE-2024-35965Bluetooth: L2CAP: Fix not validating setsockopt user input
CVE-2024-35966Bluetooth: RFCOMM: Fix not validating setsockopt user input
CVE-2024-35968pds_core: Fix pdsc_check_pci_health function to use work thread
CVE-2024-35967Bluetooth: SCO: Fix not validating setsockopt user input
CVE-2024-35963Bluetooth: hci_sock: Fix not validating setsockopt user input
CVE-2024-35971net: ks8851: Handle softirqs at the end of IRQ thread to fix hang
CVE-2024-35970af_unix: Clear stale u->oob_skb.
CVE-2024-35973geneve: fix header validation in geneve[6]_xmit_skb
CVE-2024-35972bnxt_en: Fix possible memory leak in bnxt_rdma_aux_device_init()
CVE-2024-35974block: fix q->blkg_list corruption during disk rebind
CVE-2024-35975octeontx2-pf: Fix transmit scheduler resource leak
CVE-2024-35976xsk: validate user input for XDP_{UMEM|COMPLETION}_FILL_RING
CVE-2024-35977platform/chrome: cros_ec_uart: properly fix race condition
CVE-2024-35979raid1: fix use-after-free for original bio in raid1_write_request()

Showing top 20 of 62 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2024-35949

No comments yet


Leave a comment