CVE-2024-53167 (GCVE-0-2024-53167)
Vulnerability from cvelistv5
Published
2024-12-27 13:49
Modified
2026-10-15 21:41
Summary
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.
Impacted products
Vendor Product Version
Linux Linux Version: d869da91cccb90320e101a2758f1e2b3803ade5c
Version: d869da91cccb90320e101a2758f1e2b3803ade5c
Version: d869da91cccb90320e101a2758f1e2b3803ade5c
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-53167",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-10-15T21:40:55.992319Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-10-15T21:41:46.787Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/nfs/blocklayout/dev.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "3402704a424f34bbcca7f4a4503859357f422217",
              "status": "affected",
              "version": "d869da91cccb90320e101a2758f1e2b3803ade5c",
              "versionType": "git"
            },
            {
              "lessThan": "faa4bacfaeed827a4ca8cb8529a3ce65a9e8ef46",
              "status": "affected",
              "version": "d869da91cccb90320e101a2758f1e2b3803ade5c",
              "versionType": "git"
            },
            {
              "lessThan": "3a4ce14d9a6b868e0787e4582420b721c04ee41e",
              "status": "affected",
              "version": "d869da91cccb90320e101a2758f1e2b3803ade5c",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/nfs/blocklayout/dev.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.11"
            },
            {
              "lessThan": "6.11",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.13",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11.11",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.2",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfs/blocklayout: Don\u0027t 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."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "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()` \u2192 `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\u0027s 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 \u2014 the normal state in enterprise/SAN deployments \u2014 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\u0027s 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 \u2014 either `umount` (leaving the NFS superblock permanently wedged) or the NFS state-manager kernel thread (hanging all NFS I/O for that client) \u2014 and on the many deployments running `panic_on_oops` it is a full system panic, repeatable at the attacker\u0027s will."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:44:15.520Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "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"
        }
      ],
      "title": "nfs/blocklayout: Don\u0027t attempt unregister for invalid block device",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-53167",
    "datePublished": "2024-12-27T13:49:13.201Z",
    "dateReserved": "2024-11-19T17:17:25.005Z",
    "dateUpdated": "2026-10-15T21:41:46.787Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"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\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-10-15T21:40:56.731Z\"}}], \"cna\": {\"title\": \"nfs/blocklayout: Don\u0027t attempt unregister for invalid block device\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 7.5, \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\"}, \"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()` \\u2192 `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\u0027s 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 \\u2014 the normal state in enterprise/SAN deployments \\u2014 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\u0027s 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 \\u2014 either `umount` (leaving the NFS superblock permanently wedged) or the NFS state-manager kernel thread (hanging all NFS I/O for that client) \\u2014 and on the many deployments running `panic_on_oops` it is a full system panic, repeatable at the attacker\u0027s will.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"d869da91cccb90320e101a2758f1e2b3803ade5c\", \"lessThan\": \"3402704a424f34bbcca7f4a4503859357f422217\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"d869da91cccb90320e101a2758f1e2b3803ade5c\", \"lessThan\": \"faa4bacfaeed827a4ca8cb8529a3ce65a9e8ef46\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"d869da91cccb90320e101a2758f1e2b3803ade5c\", \"lessThan\": \"3a4ce14d9a6b868e0787e4582420b721c04ee41e\", \"versionType\": \"git\"}], \"programFiles\": [\"fs/nfs/blocklayout/dev.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"6.11\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"6.11\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.11.11\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.11.*\"}, {\"status\": \"unaffected\", \"version\": \"6.12.2\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.12.*\"}, {\"status\": \"unaffected\", \"version\": \"6.13\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"fs/nfs/blocklayout/dev.c\"], \"defaultStatus\": \"affected\"}], \"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\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnfs/blocklayout: Don\u0027t 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.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.11.11\", \"versionStartIncluding\": \"6.11\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.12.2\", \"versionStartIncluding\": \"6.11\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.13\", \"versionStartIncluding\": \"6.11\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T11:44:15.520Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-53167\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-10-15T21:41:46.787Z\", \"dateReserved\": \"2024-11-19T17:17:25.005Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-12-27T13:49:13.201Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…