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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2024-26726— btrfs: don't drop extent_map for free space inode on write error

EPSS 0.01% · P0
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2024-26726

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: don't drop extent_map for free space inode on write error
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't drop extent_map for free space inode on write error While running the CI for an unrelated change I hit the following panic with generic/648 on btrfs_holes_spacecache. assertion failed: block_start != EXTENT_MAP_HOLE, in fs/btrfs/extent_io.c:1385 ------------[ cut here ]------------ kernel BUG at fs/btrfs/extent_io.c:1385! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 1 PID: 2695096 Comm: fsstress Kdump: loaded Tainted: G W 6.8.0-rc2+ #1 RIP: 0010:__extent_writepage_io.constprop.0+0x4c1/0x5c0 Call Trace: <TASK> extent_write_cache_pages+0x2ac/0x8f0 extent_writepages+0x87/0x110 do_writepages+0xd5/0x1f0 filemap_fdatawrite_wbc+0x63/0x90 __filemap_fdatawrite_range+0x5c/0x80 btrfs_fdatawrite_range+0x1f/0x50 btrfs_write_out_cache+0x507/0x560 btrfs_write_dirty_block_groups+0x32a/0x420 commit_cowonly_roots+0x21b/0x290 btrfs_commit_transaction+0x813/0x1360 btrfs_sync_file+0x51a/0x640 __x64_sys_fdatasync+0x52/0x90 do_syscall_64+0x9c/0x190 entry_SYSCALL_64_after_hwframe+0x6e/0x76 This happens because we fail to write out the free space cache in one instance, come back around and attempt to write it again. However on the second pass through we go to call btrfs_get_extent() on the inode to get the extent mapping. Because this is a new block group, and with the free space inode we always search the commit root to avoid deadlocking with the tree, we find nothing and return a EXTENT_MAP_HOLE for the requested range. This happens because the first time we try to write the space cache out we hit an error, and on an error we drop the extent mapping. This is normal for normal files, but the free space cache inode is special. We always expect the extent map to be correct. Thus the second time through we end up with a bogus extent map. Since we're deprecating this feature, the most straightforward way to fix this is to simply skip dropping the extent map range for this failed range. I shortened the test by using error injection to stress the area to make it easier to reproduce. With this patch in place we no longer panic with my error injection test.
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 77cef2ec5484564eca6bd12a2b4a1e88fd766fbc ~ 143842584c1237ebc248b2547c29d16bbe400a92 -
LinuxLinux 3.12 -

II. Public POCs for CVE-2024-26726

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-26726

登录查看更多情报信息。

Same Patch Batch · Linux · 2024-04-03 · 94 CVEs total

CVE-2024-26744RDMA/srpt: Support specifying the srpt_service_guid parameter
CVE-2024-26741dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished().
CVE-2024-26739net/sched: act_mirred: don't override retval if we already lost the skb
CVE-2024-26735ipv6: sr: fix possible use-after-free and null-ptr-deref
CVE-2024-26734devlink: fix possible use-after-free and memory leaks in devlink_init()
CVE-2024-26733arp: Prevent overflow in arp_req_get().
CVE-2024-26732net: implement lockless setsockopt(SO_PEEK_OFF)
CVE-2024-26731bpf, sockmap: Fix NULL pointer dereference in sk_psock_verdict_data_ready()
CVE-2024-26736afs: Increase buffer size in afs_update_volume_status()
CVE-2024-26743RDMA/qedr: Fix qedr_create_user_qp error flow
CVE-2024-26742scsi: smartpqi: Fix disable_managed_interrupts
CVE-2024-26747usb: roles: fix NULL pointer issue when put module's reference
CVE-2024-26748usb: cdns3: fix memory double free when handle zero packet
CVE-2024-26749usb: cdns3: fixed memory use after free at cdns3_gadget_ep_disable()
CVE-2024-26751ARM: ep93xx: Add terminator to gpiod_lookup_table
CVE-2024-26752l2tp: pass correct message length to ip6_append_data
CVE-2024-26753crypto: virtio/akcipher - Fix stack overflow on memcpy
CVE-2024-26754gtp: fix use-after-free and null-ptr-deref in gtp_genl_dump_pdp()
CVE-2024-26755md: Don't suspend the array for interrupted reshape
CVE-2024-26756md: Don't register sync_thread for reshape directly

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

IV. Related Vulnerabilities

V. Comments for CVE-2024-26726

No comments yet


Leave a comment