Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2024-49887 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

f2fs: fix to don't panic system for no free segment fault injection

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.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2024-49887 is recorded against 2 packages.

  • kernel (from 6.11.0 up to 6.11.3)
  • linux-kernel (from 6.11 up to 6.11.3)

Timeline and source

Published on 21 October 2024 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

CVE-2024-49887 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-10-21
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.11.0 6.11.3
linux-kernel 6.11 6.11.3

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-49887 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2024
✓