CVE-2024-49887 Vulnerability Analysis & Exploit Details

CVE-2024-49887
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2024-49887 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2024-49887 Details

Status: Analyzed

Last updated: 🕝 13 Nov 2024, 14:50 UTC
Originally published on: 🕕 21 Oct 2024, 18:15 UTC

Time between publication and last update: 22 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE-2024-49887 Vulnerability Summary

CVE-2024-49887: 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.

Assessing the Risk of CVE-2024-49887

Access Complexity Graph

The exploitability of CVE-2024-49887 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-49887

CVE-2024-49887 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-49887, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-49887, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2024-49887 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2024-49887 poses no threat to data integrity.
  • Availability: High
    CVE-2024-49887 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.042% (probability of exploit)

EPSS Percentile: 5.07% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 94.93% of others.

CVE-2024-49887 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.9:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.2:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-49887: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-4382 – A flaw was found in systems utilizing LUKS-encrypted disks with GRUB configured for TPM-based auto-decryption. When GRUB is set to automatically de...
  • CVE-2025-4206 – The WordPress CRM, Email & Marketing Automation for WordPress | Award Winner — Groundhogg plugin for WordPress is vulnerable to arbitrary file dele...
  • CVE-2025-3897 – The EUCookieLaw plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 2.7.2 via the 'file_get_contents' f...
  • CVE-2025-3528 – A flaw was found in the Mirror Registry. The quay-app container shipped as part of the Mirror Registry for OpenShift has write access to the `/etc/...
  • CVE-2025-1087 – Kong Insomnia Desktop Application before 11.0.2 contains a template injection vulnerability that allows attackers to execute arbitrary code. The vu...