CVE-2024-53167

  1. OpenCVE
  2. Vulnerabilities (CVE)
  3. 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.

5.5 /10

CVSS v3 : MEDIUM

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 3.6

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

References
Link Resource
https://git.kernel.org/stable/c/3402704a424f34bbcca7f4a4503859357f422217 Patch
https://git.kernel.org/stable/c/3a4ce14d9a6b868e0787e4582420b721c04ee41e Patch
https://git.kernel.org/stable/c/faa4bacfaeed827a4ca8cb8529a3ce65a9e8ef46 Patch
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
History

08 Oct 2025, 14:41

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/3402704a424f34bbcca7f4a4503859357f422217 - () https://git.kernel.org/stable/c/3402704a424f34bbcca7f4a4503859357f422217 - Patch
References () https://git.kernel.org/stable/c/3a4ce14d9a6b868e0787e4582420b721c04ee41e - () https://git.kernel.org/stable/c/3a4ce14d9a6b868e0787e4582420b721c04ee41e - Patch
References () https://git.kernel.org/stable/c/faa4bacfaeed827a4ca8cb8529a3ce65a9e8ef46 - () https://git.kernel.org/stable/c/faa4bacfaeed827a4ca8cb8529a3ce65a9e8ef46 - Patch
First Time Linux
Linux linux Kernel
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
CWE CWE-476
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 5.5
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: nfs/blocklayout: No intente anular el registro de un dispositivo de bloque no válido Desde el commit d869da91cccb ("nfs/blocklayout: Reparar la anulación prematura del registro de una clave PR"), un desmontaje de un NFS con diseño SCSI habilitado pNFS puede anular la referencia de un block_device NULL en: 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] Esto sucede porque, aunque pudimos crear el nfs4_deviceid_node, la búsqueda del dispositivo no pudo adjuntar el dispositivo de bloque a pnfs_block_dev. Si nunca encontramos un dispositivo de bloque para registrar, podemos evitar este caso con el indicador PNFS_BDEV_REGISTERED. Mueva el desreferenciador detrás de la prueba para el indicador.

27 Dec 2024, 14:15

Type Values Removed Values Added
New CVE
Information

Published : 2024-12-27 14:15

Updated : 2025-10-08 14:41

NVD link : CVE-2024-53167

Mitre link : CVE-2024-53167

CVE.ORG link : CVE-2024-53167

JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-476

NULL Pointer Dereference