{"id":"CVE-2024-53167","state":"PUBLISHED","title":"nfs/blocklayout: Don't attempt unregister for invalid block device","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnfs/blocklayout: Don't attempt unregister for invalid block device\n\nSince commit d869da91cccb (\"nfs/blocklayout: Fix premature PR key\nunregistration\") an unmount of a pNFS SCSI layout-enabled NFS may\ndereference a NULL block_device in:\n\n  bl_unregister_scsi+0x16/0xe0 [blocklayoutdriver]\n  bl_free_device+0x70/0x80 [blocklayoutdriver]\n  bl_free_deviceid_node+0x12/0x30 [blocklayoutdriver]\n  nfs4_put_deviceid_node+0x60/0xc0 [nfsv4]\n  nfs4_deviceid_purge_client+0x132/0x190 [nfsv4]\n  unset_pnfs_layoutdriver+0x59/0x60 [nfsv4]\n  nfs4_destroy_server+0x36/0x70 [nfsv4]\n  nfs_free_server+0x23/0xe0 [nfs]\n  deactivate_locked_super+0x30/0xb0\n  cleanup_mnt+0xba/0x150\n  task_work_run+0x59/0x90\n  syscall_exit_to_user_mode+0x217/0x220\n  do_syscall_64+0x8e/0x160\n\nThis happens because even though we were able to create the\nnfs4_deviceid_node, the lookup for the device was unable to attach the\nblock device to the pnfs_block_dev.\n\nIf we never found a block device to register, we can avoid this case with\nthe PNFS_BDEV_REGISTERED flag.  Move the deref behind the test for the\nflag.","publishedAt":"2024-12-27T13:49:13.201Z","updatedAt":"2026-10-15T21:41:46.787Z","severity":{"score":7.5,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","source":"Linux"},"assigner":"Linux","products":["Linux Linux"],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"d869da91cccb90320e101a2758f1e2b3803ade5c","status":"affected","lessThan":"3402704a424f34bbcca7f4a4503859357f422217","versionType":"git"},{"version":"d869da91cccb90320e101a2758f1e2b3803ade5c","status":"affected","lessThan":"faa4bacfaeed827a4ca8cb8529a3ce65a9e8ef46","versionType":"git"},{"version":"d869da91cccb90320e101a2758f1e2b3803ade5c","status":"affected","lessThan":"3a4ce14d9a6b868e0787e4582420b721c04ee41e","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/nfs/blocklayout/dev.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.11","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.11","versionType":"semver"},{"version":"6.11.11","status":"unaffected","lessThanOrEqual":"6.11.*","versionType":"semver"},{"version":"6.12.2","status":"unaffected","lessThanOrEqual":"6.12.*","versionType":"semver"},{"version":"6.13","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/nfs/blocklayout/dev.c"]}],"references":["https://git.kernel.org/stable/c/3402704a424f34bbcca7f4a4503859357f422217","https://git.kernel.org/stable/c/faa4bacfaeed827a4ca8cb8529a3ce65a9e8ef46","https://git.kernel.org/stable/c/3a4ce14d9a6b868e0787e4582420b721c04ee41e"],"weaknesses":[],"ingestedAt":"2026-10-29T20:08:04.920Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2024/53xxx/CVE-2024-53167.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2024-53167","state":"PUBLISHED","datePublished":"2024-12-27T13:49:13.201Z","dateUpdated":"2026-10-15T21:41:46.787Z","assignerShortName":"Linux","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateReserved":"2024-11-19T17:17:25.005Z"},"containers":{"cna":{"title":"nfs/blocklayout: Don't attempt unregister for invalid block device","descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnfs/blocklayout: Don't attempt unregister for invalid block device\n\nSince commit d869da91cccb (\"nfs/blocklayout: Fix premature PR key\nunregistration\") an unmount of a pNFS SCSI layout-enabled NFS may\ndereference a NULL block_device in:\n\n  bl_unregister_scsi+0x16/0xe0 [blocklayoutdriver]\n  bl_free_device+0x70/0x80 [blocklayoutdriver]\n  bl_free_deviceid_node+0x12/0x30 [blocklayoutdriver]\n  nfs4_put_deviceid_node+0x60/0xc0 [nfsv4]\n  nfs4_deviceid_purge_client+0x132/0x190 [nfsv4]\n  unset_pnfs_layoutdriver+0x59/0x60 [nfsv4]\n  nfs4_destroy_server+0x36/0x70 [nfsv4]\n  nfs_free_server+0x23/0xe0 [nfs]\n  deactivate_locked_super+0x30/0xb0\n  cleanup_mnt+0xba/0x150\n  task_work_run+0x59/0x90\n  syscall_exit_to_user_mode+0x217/0x220\n  do_syscall_64+0x8e/0x160\n\nThis happens because even though we were able to create the\nnfs4_deviceid_node, the lookup for the device was unable to attach the\nblock device to the pnfs_block_dev.\n\nIf we never found a block device to register, we can avoid this case with\nthe PNFS_BDEV_REGISTERED flag.  Move the deref behind the test for the\nflag."}],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"d869da91cccb90320e101a2758f1e2b3803ade5c","status":"affected","lessThan":"3402704a424f34bbcca7f4a4503859357f422217","versionType":"git"},{"version":"d869da91cccb90320e101a2758f1e2b3803ade5c","status":"affected","lessThan":"faa4bacfaeed827a4ca8cb8529a3ce65a9e8ef46","versionType":"git"},{"version":"d869da91cccb90320e101a2758f1e2b3803ade5c","status":"affected","lessThan":"3a4ce14d9a6b868e0787e4582420b721c04ee41e","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/nfs/blocklayout/dev.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.11","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.11","versionType":"semver"},{"version":"6.11.11","status":"unaffected","lessThanOrEqual":"6.11.*","versionType":"semver"},{"version":"6.12.2","status":"unaffected","lessThanOrEqual":"6.12.*","versionType":"semver"},{"version":"6.13","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/nfs/blocklayout/dev.c"]}],"references":[{"url":"https://git.kernel.org/stable/c/3402704a424f34bbcca7f4a4503859357f422217"},{"url":"https://git.kernel.org/stable/c/faa4bacfaeed827a4ca8cb8529a3ce65a9e8ef46"},{"url":"https://git.kernel.org/stable/c/3a4ce14d9a6b868e0787e4582420b721c04ee41e"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:N - The malformed device description arrives in a GETDEVICEINFO reply from the remote NFS server, which the client decodes in `bl_alloc_deviceid_node()`; the same server can also remotely trigger the free path via SEQUENCE state-revocation flags leading to `pnfs_destroy_all_layouts()` → `nfs4_deviceid_purge_client()`. No local access to the victim client is needed.\nAC:L - The server fully controls the SCSI designator, and any well-formed NAA/EUI64 designator not matching a local `/dev/disk/by-id/` entry deterministically leaves `bdev_file` NULL; LAYOUT_SCSI is the client's highest-preference layout type and `blocklayoutdriver` autoloads, so no special victim configuration or timing is required.\nPR:N - The attacker acts as the NFS server (or a MITM/compromised trusted server) and holds no credentials or account on the victim client; the client itself initiates the exchange and consumes the reply with no authorization check on the device description.\nUI:N - On an already-established pNFS-capable NFSv4.1 mount — the normal state in enterprise/SAN deployments — a malicious or compromised server can hand out the bad SCSI deviceid and then revoke recallable state to force the purge with no action by any user.\nS:U - The NULL dereference occurs in kernel context within the NFS client and its impact is confined to the kernel's own security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:N - The dereference is at a fixed low offset from NULL (`f_mapping` at ~0x18 in `struct file`), which is unmapped under `mmap_min_addr`; no memory contents are read out or disclosed to the attacker.\nI:N - The bug provides only a read of an unmapped low address, yielding no write primitive or control over kernel data; no memory is modified before the fault.\nA:H - The oops kills the faulting task — either `umount` (leaving the NFS superblock permanently wedged) or the NFS state-manager kernel thread (hanging all NFS I/O for that client) — and on the many deployments running `panic_on_oops` it is a full system panic, repeatable at the attacker's will."}]}],"providerMetadata":{"shortName":"Linux","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateUpdated":"2026-08-05T11:44:15.520Z"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11","versionEndExcluding":"6.11.11"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11","versionEndExcluding":"6.12.2"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11","versionEndExcluding":"6.13"}]}]}],"x_generator":{"engine":"bippy-1.2.0"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"id":"CVE-2024-53167","role":"CISA Coordinator","options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}],"version":"2.0.3","timestamp":"2026-10-15T21:40:55.992319Z"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-10-15T21:41:46.787Z"}}]}}}