BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-53167High confidence

nfs/blocklayout: Don't attempt unregister for invalid block device

Linux · Linux

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

2 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-51839

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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.

What

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.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → NULL Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-476
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20250101Security Bulletin 01 Jan 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 01 Jan 2025, published on 1 January 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2024-53117 Référence CVE CVE-2024-53118 https://www.cve.org/CVERecord?id=CVE-2024-53118 Référence CVE CVE-2024-53120 https://www.cve.org/CVERecord?id=CVE-2024-53120 Référence CVE CVE-2024-53123 https://www.cve.org/CVERecord?id=CVE-2024-53123 Référence CVE CVE-2024-53134 https://www.cve.org/CVERecord?id=CVE-2024-53134 Référence CVE CVE-2024-53136 https://www.cve.org/CVERecord?id=CVE-2024-53136 Référence CVE CVE-2024-53151 https://www.cve.org/CVERecord?id=CVE-2024-53151 Référence CVE CVE-2024-53160 https://www.cve.org/CVERecord?id=CVE-2024-53160 Référence CVE CVE-2024-53166 https://www.cve.org/CVERecord?id=CVE-2024-53166 Référence CVE CVE-2024-53167 https://www.cve.org/CVERecord?id=CVE-2024-53167 Référence CVE CVE-2024-53169 https://www.cve.org/CVERecord?id=CVE-2024-53169 Référence CVE CVE-2024-53170 https://www.cve.org/CVERecord?id=CVE-2024-53170 Référence CVE CVE-2024-53175 https://www.cve.org/CVERecord?id=CVE-2024-53175 Référence CVE CVE-2024-53176 https://www.cve.org/CVERecord?id=CVE-2024-53176 Référence CVE CVE-2024-53178 https://www.cve.org/CVERecord?id=CVE-2024-53178 Référence CVE CVE-2024-53185 https://www.cve.org/CVERecord?id=CVE-2024-53185 Référence CVE CVE-2024-53189 https://www.cve.org/CVERecord?id=CVE-2024-53189 Référence CVE CVE-2024-53202 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0185Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-53157 Référence CVE CVE-2024-53158 https://www.cve.org/CVERecord?id=CVE-2024-53158 Référence CVE CVE-2024-53160 https://www.cve.org/CVERecord?id=CVE-2024-53160 Référence CVE CVE-2024-53161 https://www.cve.org/CVERecord?id=CVE-2024-53161 Référence CVE CVE-2024-53162 https://www.cve.org/CVERecord?id=CVE-2024-53162 Référence CVE CVE-2024-53163 https://www.cve.org/CVERecord?id=CVE-2024-53163 Référence CVE CVE-2024-53164 https://www.cve.org/CVERecord?id=CVE-2024-53164 Référence CVE CVE-2024-53165 https://www.cve.org/CVERecord?id=CVE-2024-53165 Référence CVE CVE-2024-53166 https://www.cve.org/CVERecord?id=CVE-2024-53166 Référence CVE CVE-2024-53167 https://www.cve.org/CVERecord?id=CVE-2024-53167 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=CVE-2024-53168 Référence CVE CVE-2024-53169 https://www.cve.org/CVERecord?id=CVE-2024-53169 Référence CVE CVE-2024-53170 https://www.cve.org/CVERecord?id=CVE-2024-53170 Référence CVE CVE-2024-53171 https://www.cve.org/CVERecord?id=CVE-2024-53171 Référence CVE CVE-2024-53172 https://www.cve.org/CVERecord?id=CVE-2024-53172 Référence CVE CVE-2024-53173 https://www.cve.org/CVERecord?id=CVE-2024-53173 Référence CVE CVE-2024-53174 https://www.cve.org/CVERecord?id=CVE-2024-53174 Référence CVE CVE-2024-53175 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0152Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-53156 Référence CVE CVE-2024-53157 https://www.cve.org/CVERecord?id=CVE-2024-53157 Référence CVE CVE-2024-53158 https://www.cve.org/CVERecord?id=CVE-2024-53158 Référence CVE CVE-2024-53160 https://www.cve.org/CVERecord?id=CVE-2024-53160 Référence CVE CVE-2024-53161 https://www.cve.org/CVERecord?id=CVE-2024-53161 Référence CVE CVE-2024-53162 https://www.cve.org/CVERecord?id=CVE-2024-53162 Référence CVE CVE-2024-53163 https://www.cve.org/CVERecord?id=CVE-2024-53163 Référence CVE CVE-2024-53165 https://www.cve.org/CVERecord?id=CVE-2024-53165 Référence CVE CVE-2024-53166 https://www.cve.org/CVERecord?id=CVE-2024-53166 Référence CVE CVE-2024-53167 https://www.cve.org/CVERecord?id=CVE-2024-53167 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=CVE-2024-53168 Référence CVE CVE-2024-53169 https://www.cve.org/CVERecord?id=CVE-2024-53169 Référence CVE CVE-2024-53170 https://www.cve.org/CVERecord?id=CVE-2024-53170 Référence CVE CVE-2024-53171 https://www.cve.org/CVERecord?id=CVE-2024-53171 Référence CVE CVE-2024-53172 https://www.cve.org/CVERecord?id=CVE-2024-53172 Référence CVE CVE-2024-53173 https://www.cve.org/CVERecord?id=CVE-2024-53173 Référence CVE CVE-2024-53174 https://www.cve.org/CVERecord?id=CVE-2024-53174 Référence CVE CVE-2024-53175 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028772Linux の Linux Kernel における NULL ポインタデリファレンスに関する脆弱性

Linux の Linux Kernel には、NULL ポインタデリファレンスに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Linux: d869da91cccb90320e101a2758f1e2b3803ade5c < 3402704a424f34bbcca7f4a4503859357f422217, d869da91cccb90320e101a2758f1e2b3803ade5c < faa4bacfaeed827a4ca8cb8529a3ce65a9e8ef46, d869da91cccb90320e101a2758f1e2b3803ade5c < 3a4ce14d9a6b868e0787e4582420b721c04ee41e, 6.11
Fixed
Linux: < 6.11, 6.11.11 ≤ 6.11.*, 6.12.2 ≤ 6.12.*, 6.13 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 27 Dec 2024 · Last source change 5 Aug 2026, 11:44 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-51839
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-51839↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-53167 · cve.blacktree.nl