CVE-2024-49882
ext4: fix double brelse() the buffer of the extents path
Reported by linux · Published October 21, 2024
In the Linux kernel, the following vulnerability has been resolved: ext4: fix double brelse() the buffer of the extents path In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows: split2 map split1 |--------|-------|--------| ext4_ext_map_blocks ext4_ext_handle_unwritten_extents ext4_split_convert_extents // path->p_depth == 0 ext4_split_extent // 1. do split1 ext4_split_extent_at |ext4_ext_insert_extent | ext4_ext_create_new_leaf | ext4_ext_grow_indepth | le16_add_cpu(&neh->eh_depth, 1) | ext4_find_extent | // return -ENOMEM |// get error and try zeroout |path = ext4_find_extent | path->p_depth = 1 |ext4_ext_try_to_merge | ext4_ext_try_to_merge_up | path->p_depth = 0 | brelse(path[1].p_bh) ---> not set to NULL here |// zeroout success // 2. update path ext4_find_extent // 3. do split2 ext4_split_extent_at ext4_ext_insert_extent ext4_ext_create_new_leaf ext4_ext_grow_indepth le16_add_cpu(&neh->eh_depth, 1) ext4_find_extent path[0].p_bh = NULL; path->p_depth = 1 read_extent_tree_block ---> return err // path[1].p_bh is still the old value ext4_free_ext_path ext4_ext_drop_refs // path->p_depth == 1 brelse(path[1].p_bh) ---> brelse a buffer twice Finally got the following WARRNING when removing the buffer from lru: ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace: <TASK> __find_get_block+0x6e7/0x810 bdev_getblk+0x2b/0x480 __ext4_get_inode_loc+0x48a/0x1240 ext4_get_inode_loc+0xb2/0x150 ext4_reserve_inode_write+0xb7/0x230 __ext4_mark_inode_dirty+0x144/0x6a0 ext4_ext_insert_extent+0x9c8/0x3230 ext4_ext_map_blocks+0xf45/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ============================================
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-headers | Amazon Linux | 4.14.355-276.639.amzn2 |
| perf | Amazon Linux | 4.14.355-276.639.amzn2 |
| python3-perf | Amazon Linux | 6.1.115-126.197.amzn2023 |
| kernel-devel | Amazon Linux | 4.14.355-276.639.amzn2 |
| kernel-libbpf | Amazon Linux | 6.1.115-126.197.amzn2023 |
| kernel | Amazon Linux | 6.1.115-126.197.amzn2023 |
| linux_kernel | linux | 6.11.3, 6.10.14, 6.6.55, 6.1.113, 5.15.168, 5.10.227, 5.4.285, 4.19.323 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | ecb94f5fdf4b72547fca022421a9dca1672bddd4, ecb94f5fdf4b72547fca022421a9dca1672bddd4, ecb94f5fdf4b72547fca022421a9dca1672bddd4 |
| Linux | Linux | 3.7, 0, 4.19.323 |
| amazon:2 | kernel-headers | 0 |
| amazon:2 | perf | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2 | kernel-devel | 0 |
| amazon:2023 | kernel-libbpf | 0 |
| amazon:2023 | kernel | 0 |
| linux | linux_kernel | 3.7, 3.7, 3.7 |
| amazon:2023 | kernel-headers | 0 |
| Linux | Linux | *, 3.7, 0 |
| amazon:2023 | bpftool | 0 |
| amazon:2 | kernel | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2 | kernel-livepatch-4.14.355-276.639 | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | kernel-libbpf-static | 0 |
| amazon:2 | kernel-tools | 0 |
| amazon:2023 | kernel-devel | 0 |
…and 6 more
Timeline
- Oct 21, 2024 CVE Published
- Oct 22, 2024 EPSS Score (30 in total, the first dated here)
- Oct 23, 2024 Coalition ESS Score (12 in total, the first dated here)
- Dec 16, 2025 PoC Published
- Jan 2, 2026 Security Advisory (449 in total, the first dated here)
- Mar 30, 2026 Distribution Patch (381 in total, the first dated here)
- Aug 4, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-49882
vulnetix vdb fixes CVE-2024-49882
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-49882/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart