Vulnerability · Published Oct 21, 2024 · Assigned by Linux
CVE-2024-49887f2fs: fix to don't panic system for no free segment fault injection
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 18% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to don't panic system for no free segment fault injection f2fs: fix to don't panic system for no free segment fault injection syzbot reports a f2fs bug as below: F2FS-fs (loop0): inject no free segment in get_new_segment of __allocate_new_segment+0x1ce/0x940 fs/f2fs/segment.c:3167 F2FS-fs (loop0): Stopped filesystem due to reason: 7 ------------[ cut here ]------------ kernel BUG at fs/f2fs/segment.c:2748! CPU: 0 UID: 0 PID: 5109 Comm: syz-executor304 Not tainted 6.11.0-rc6-syzkaller-00363-g89f5e14d05b4 #0 RIP: 0010:get_new_segment fs/f2fs/segment.c:2748 [inline] RIP: 0010:new_curseg+0x1f61/0x1f70 fs/f2fs/segment.c:2836 Call Trace: __allocate_new_segment+0x1ce/0x940 fs/f2fs/segment.c:3167 f2fs_allocate_new_section fs/f2fs/segment.c:3181 [inline] f2fs_allocate_pinning_section+0xfa/0x4e0 fs/f2fs/segment.c:3195 f2fs_expand_inode_data+0x5d6/0xbb0 fs/f2fs/file.c:1799 f2fs_fallocate+0x448/0x960 fs/f2fs/file.c:1903 vfs_fallocate+0x553/0x6c0 fs/open.c:334 do_vfs_ioctl+0x2592/0x2e50 fs/ioctl.c:886 __do_sys_ioctl fs/ioctl.c:905 [inline] __se_sys_ioctl+0x81/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:get_new_segment fs/f2fs/segment.c:2748 [inline] RIP: 0010:new_curseg+0x1f61/0x1f70 fs/f2fs/segment.c:2836 The root cause is when we inject no free segment fault into f2fs, we should not panic system, fix it.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:13 | linux | 6.11.4-1 | DEBIAN-CVE-2024-49887 |
| Debian:14 | linux | 6.11.4-1 | DEBIAN-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux | 6.8.0-64.67 | USN-7651-1 |
| Ubuntu:24.04:LTS | linux | 6.8.0-64.67 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1032.34 | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1032.34 | USN-7651-1 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1032.34~22.04.1 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1032.34~22.04.1 | USN-7651-3 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1034.39 | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1034.39 | USN-7737-1 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | 6.11.0-1012.12~24.04.1 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1034.39~22.04.1 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1034.39~22.04.1 | USN-7737-1 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | 6.8.0-1022.23 | USN-7737-1 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | 6.8.0-1022.23 | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1033.35 | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1033.35 | USN-7651-4 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | 6.11.0-1011.11~24.04.1 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1033.35~22.04.1 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1033.35~22.04.1 | USN-7651-4 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1028.32 | USN-7651-3 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1028.32 | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1015.17 | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1015.17 | USN-7651-3 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-64.67~22.04.1 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-64.67~22.04.1 | USN-7653-1 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1029.29 | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1029.29 | USN-7651-2 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1029.29~22.04.1 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1029.29~22.04.1 | USN-7651-2 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-64.67.1 | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-64.67.1 | USN-7651-2 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-64.67.1~22.04.1 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-64.67.1~22.04.1 | USN-7651-2 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1031.34 | USN-7651-3 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1031.34 | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | 6.11.0-1007.7 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1031.34~22.04.1 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1031.34~22.04.1 | USN-7651-3 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1031.34.1 | USN-7651-3 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1031.34.1 | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1008.8 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | 6.11.0-1015.15 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | 6.8.0-1031.31 | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | 6.8.0-1031.31 | USN-7651-1 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1029.30 | USN-7651-3 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1029.30 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1029.30~22.04.1 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1029.30~22.04.1 | USN-7651-3 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1031.35 | USN-7651-6 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1031.35 | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-64.67~22.04.1 | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2024-49887 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2024-49887 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 8b10d3653735e117bc1954ade80d75ad7b46b801 – before 9f6e7a0512a57387d36f5e9e9635d6668cac13dd8b10d3653735e117bc1954ade80d75ad7b46b801 – before 645ec43760e86d3079fee2e8b51fde7060a540d08b10d3653735e117bc1954ade80d75ad7b46b801 – before 65a6ce4726c27b45600303f06496fef46d00b57f |
| Linux | Linux | 6.9 |