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

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2025-40100— btrfs: do not assert we found block group item when creating free space tree

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于未正确处理空块组情况,可能导致断言失败。

AI Predicted 6.5 Difficulty: Moderate EPSS 0.20% · P9

Possible ATT&CK Techniques 1 AI

T1496 · Resource Hijacking

Affected Version Matrix 12

VendorProduct Version RangeStatus
Linux Linux a5ed91828518ab076209266c2bc510adabd078df< 4f4b9ca73f84130d9fbb0fc02306ce94ce8bdbe6 affected
a5ed91828518ab076209266c2bc510adabd078df< 289498da343b05c886f19b4269429606f86dd17b affected
a5ed91828518ab076209266c2bc510adabd078df< 3fdcfd91b93f930d87843156c7c8cc5fbcf9b144 affected
a5ed91828518ab076209266c2bc510adabd078df< eb145463f22d7d32d426b29fe9810de9e792b6ba affected
a5ed91828518ab076209266c2bc510adabd078df< a5a51bf4e9b7354ce7cd697e610d72c1b33fd949 affected
4.5 affected
< 4.5 unaffected
6.1.158≤ 6.1.* unaffected
… +4 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2025-40100

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: do not assert we found block group item when creating free space tree
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: do not assert we found block group item when creating free space tree Currently, when building a free space tree at populate_free_space_tree(), if we are not using the block group tree feature, we always expect to find block group items (either extent items or a block group item with key type BTRFS_BLOCK_GROUP_ITEM_KEY) when we search the extent tree with btrfs_search_slot_for_read(), so we assert that we found an item. However this expectation is wrong since we can have a new block group created in the current transaction which is still empty and for which we still have not added the block group's item to the extent tree, in which case we do not have any items in the extent tree associated to the block group. The insertion of a new block group's block group item in the extent tree happens at btrfs_create_pending_block_groups() when it calls the helper insert_block_group_item(). This typically is done when a transaction handle is released, committed or when running delayed refs (either as part of a transaction commit or when serving tickets for space reservation if we are low on free space). So remove the assertion at populate_free_space_tree() even when the block group tree feature is not enabled and update the comment to mention this case. Syzbot reported this with the following stack trace: BTRFS info (device loop3 state M): rebuilding free space tree assertion failed: ret == 0 :: 0, in fs/btrfs/free-space-tree.c:1115 ------------[ cut here ]------------ kernel BUG at fs/btrfs/free-space-tree.c:1115! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 1 UID: 0 PID: 6352 Comm: syz.3.25 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 RIP: 0010:populate_free_space_tree+0x700/0x710 fs/btrfs/free-space-tree.c:1115 Code: ff ff e8 d3 (...) RSP: 0018:ffffc9000430f780 EFLAGS: 00010246 RAX: 0000000000000043 RBX: ffff88805b709630 RCX: fea61d0e2e79d000 RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000 RBP: ffffc9000430f8b0 R08: ffffc9000430f4a7 R09: 1ffff92000861e94 R10: dffffc0000000000 R11: fffff52000861e95 R12: 0000000000000001 R13: 1ffff92000861f00 R14: dffffc0000000000 R15: 0000000000000000 FS: 00007f424d9fe6c0(0000) GS:ffff888125afc000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fd78ad212c0 CR3: 0000000076d68000 CR4: 00000000003526f0 Call Trace: <TASK> btrfs_rebuild_free_space_tree+0x1ba/0x6d0 fs/btrfs/free-space-tree.c:1364 btrfs_start_pre_rw_mount+0x128f/0x1bf0 fs/btrfs/disk-io.c:3062 btrfs_remount_rw fs/btrfs/super.c:1334 [inline] btrfs_reconfigure+0xaed/0x2160 fs/btrfs/super.c:1559 reconfigure_super+0x227/0x890 fs/super.c:1076 do_remount fs/namespace.c:3279 [inline] path_mount+0xd1a/0xfe0 fs/namespace.c:4027 do_mount fs/namespace.c:4048 [inline] __do_sys_mount fs/namespace.c:4236 [inline] __se_sys_mount+0x313/0x410 fs/namespace.c:4213 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f424e39066a Code: d8 64 89 02 (...) RSP: 002b:00007f424d9fde68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00007f424d9fdef0 RCX: 00007f424e39066a RDX: 0000200000000180 RSI: 0000200000000380 RDI: 0000000000000000 RBP: 0000200000000180 R08: 00007f424d9fdef0 R09: 0000000000000020 R10: 0000000000000020 R11: 0000000000000246 R12: 0000200000000380 R13: 00007f424d9fdeb0 R14: 0000000000000000 R15: 00002000000002c0 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]---
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
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

Vendor Product Affected Versions CPE Subscribe
Linux Linux a5ed91828518ab076209266c2bc510adabd078df ~ 4f4b9ca73f84130d9fbb0fc02306ce94ce8bdbe6 -
Linux Linux 4.5 -

II. Public POCs for CVE-2025-40100

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-40100

请登录查看更多情报信息。

Same Patch Batch · Linux · 2025-10-30 · 20 CVEs total

CVE-2025-40099 9.4 CRITICAL cifs: parse_dfs_referrals: prevent oob on malformed input
CVE-2025-40095 7.8 HIGH usb: gadget: f_rndis: Refactor bind path to use __free()
CVE-2025-40105 7.8 HIGH vfs: Don't leak disconnected dentries on umount
CVE-2025-40104 7.8 HIGH ixgbevf: fix mailbox API compatibility by negotiating supported features
CVE-2025-40096 7.8 HIGH drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies
CVE-2025-40094 7.8 HIGH usb: gadget: f_acm: Refactor bind path to use __free()
CVE-2025-40093 7.8 HIGH usb: gadget: f_ecm: Refactor bind path to use __free()
CVE-2025-40092 7.8 HIGH usb: gadget: f_ncm: Refactor bind path to use __free()
CVE-2025-40090 7.5 HIGH ksmbd: fix recursive locking in RPC handle list access
CVE-2025-40087 7.5 HIGH NFSD: Define a proc_layoutcommit for the FlexFiles layout type
CVE-2025-40088 7.1 HIGH hfsplus: fix slab-out-of-bounds read in hfsplus_strcasecmp()
CVE-2025-40086 drm/xe: Don't allow evicting of BOs in same VM in array of VM binds
CVE-2025-40091 ixgbe: fix too early devlink_free() in ixgbe_remove()
CVE-2025-40097 ALSA: hda: Fix missing pointer check in hda_component_manager_init function
CVE-2025-40098 ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state()
CVE-2025-40089 cxl/features: Add check for no entries in cxl_feature_info
CVE-2025-40101 btrfs: fix memory leaks when rejecting a non SINGLE data profile without an RST
CVE-2025-40102 KVM: arm64: Prevent access to vCPU events before init
CVE-2025-40103 smb: client: Fix refcount leak for cifs_sb_tlink

IV. Related Vulnerabilities

V. Comments for CVE-2025-40100

No comments yet


Leave a comment