CVE-2024-47680 Vulnerability Analysis & Exploit Details

CVE-2024-47680
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2024-47680 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-47680 Details

Status: Analyzed

Last updated: 🕐 24 Oct 2024, 13:28 UTC
Originally published on: 🕛 21 Oct 2024, 12:15 UTC

Time between publication and last update: 3 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-47680 Vulnerability Summary

CVE-2024-47680: In the Linux kernel, the following vulnerability has been resolved: f2fs: check discard support for conventional zones As the helper function f2fs_bdev_support_discard() shows, f2fs checks if the target block devices support discard by calling bdev_max_discard_sectors() and bdev_is_zoned(). This check works well for most cases, but it does not work for conventional zones on zoned block devices. F2fs assumes that zoned block devices support discard, and calls __submit_discard_cmd(). When __submit_discard_cmd() is called for sequential write required zones, it works fine since __submit_discard_cmd() issues zone reset commands instead of discard commands. However, when __submit_discard_cmd() is called for conventional zones, __blkdev_issue_discard() is called even when the devices do not support discard. The inappropriate __blkdev_issue_discard() call was not a problem before the commit 30f1e7241422 ("block: move discard checks into the ioctl handler") because __blkdev_issue_discard() checked if the target devices support discard or not. If not, it returned EOPNOTSUPP. After the commit, __blkdev_issue_discard() no longer checks it. It always returns zero and sets NULL to the given bio pointer. This NULL pointer triggers f2fs_bug_on() in __submit_discard_cmd(). The BUG is recreated with the commands below at the umount step, where /dev/nullb0 is a zoned null_blk with 5GB total size, 128MB zone size and 10 conventional zones. $ mkfs.f2fs -f -m /dev/nullb0 $ mount /dev/nullb0 /mnt $ for ((i=0;i<5;i++)); do dd if=/dev/zero of=/mnt/test bs=65536 count=1600 conv=fsync; done $ umount /mnt To fix the BUG, avoid the inappropriate __blkdev_issue_discard() call. When discard is requested for conventional zones, check if the device supports discard or not. If not, return EOPNOTSUPP.

Assessing the Risk of CVE-2024-47680

Access Complexity Graph

The exploitability of CVE-2024-47680 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-47680

CVE-2024-47680 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-47680, 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-47680, 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-47680 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2024-47680 poses no threat to data integrity.
  • Availability: High
    CVE-2024-47680 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.02% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 94.98% of others.

CVE-2024-47680 References

External References

CWE Common Weakness Enumeration

CWE-476

Vulnerable Configurations

  • 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.11:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:-:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-47680: 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-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...