CVE-2024-53167 Vulnerability Analysis & Exploit Details

CVE-2024-53167
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2024-53167 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2024-53167 Details

Status: Modified

Last updated: 🕚 04 Aug 2026, 11:22 UTC
Originally published on: 🕑 27 Dec 2024, 14:15 UTC

Time between publication and last update: 584 days

CVSS Release: version 3

CVSS3 Source

416baaa9-dc9f-4396-8d5f-8c081fb06d67

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2024-53167 Vulnerability Summary

CVE-2024-53167: In the Linux kernel, the following vulnerability has been resolved: nfs/blocklayout: Don't attempt unregister for invalid block device Since commit d869da91cccb ("nfs/blocklayout: Fix premature PR key unregistration") an unmount of a pNFS SCSI layout-enabled NFS may dereference a NULL block_device in: bl_unregister_scsi+0x16/0xe0 [blocklayoutdriver] bl_free_device+0x70/0x80 [blocklayoutdriver] bl_free_deviceid_node+0x12/0x30 [blocklayoutdriver] nfs4_put_deviceid_node+0x60/0xc0 [nfsv4] nfs4_deviceid_purge_client+0x132/0x190 [nfsv4] unset_pnfs_layoutdriver+0x59/0x60 [nfsv4] nfs4_destroy_server+0x36/0x70 [nfsv4] nfs_free_server+0x23/0xe0 [nfs] deactivate_locked_super+0x30/0xb0 cleanup_mnt+0xba/0x150 task_work_run+0x59/0x90 syscall_exit_to_user_mode+0x217/0x220 do_syscall_64+0x8e/0x160 This happens because even though we were able to create the nfs4_deviceid_node, the lookup for the device was unable to attach the block device to the pnfs_block_dev. If we never found a block device to register, we can avoid this case with the PNFS_BDEV_REGISTERED flag. Move the deref behind the test for the flag.

Assessing the Risk of CVE-2024-53167

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2024-53167 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

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-53167, 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-53167, 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-53167 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2024-53167 poses no threat to data integrity.
  • Availability: High
    CVE-2024-53167 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.045% (probability of exploit)

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

CVE-2024-53167 References

External References

CWE Common Weakness Enumeration

CWE-476

Vulnerable Configurations

  • 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:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.1:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-53167: 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-2026-90474 – MCPHub before 1.0.32 contains an authentication bypass vulnerability in its embedded OAuth 2.0 authorization server where client authentication is ...
  • CVE-2026-90473 – msgpack-java through 0.9.12 contains an integer overflow vulnerability in MessageUnpacker.skipValue() when processing MAP32 containers with large e...
  • CVE-2026-90472 – msgpack-java through 0.9.12 contains a stack overflow vulnerability in MessageUnpacker.unpackValue() that recursively deserializes arrays and maps ...
  • CVE-2026-89172 – Improper protection of physical side channels vulnerability in Microchip AN1044, Microchip AN953, and Microchip SW300052. This issue affects AN104...
  • CVE-2026-85200 – The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_aj...