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

Published Dec 27, 2024
·
Updated

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 blockdevice in:

blunregisterscsi+0x16/0xe0 [blocklayoutdriver] blfreedevice+0x70/0x80 [blocklayoutdriver] blfreedeviceidnode+0x12/0x30 [blocklayoutdriver] nfs4putdeviceidnode+0x60/0xc0 [nfsv4] nfs4deviceidpurgeclient+0x132/0x190 [nfsv4] unsetpnfslayoutdriver+0x59/0x60 [nfsv4] nfs4destroyserver+0x36/0x70 [nfsv4] nfsfreeserver+0x23/0xe0 [nfs] deactivatelockedsuper+0x30/0xb0 cleanupmnt+0xba/0x150 taskworkrun+0x59/0x90 syscallexittousermode+0x217/0x220 dosyscall64+0x8e/0x160

This happens because even though we were able to create the nfs4deviceidnode, the lookup for the device was unable to attach the block device to the pnfsblockdev.

If we never found a block device to register, we can avoid this case with the PNFSBDEVREGISTERED flag. Move the deref behind the test for the flag.

Affected Software

4 affected componentsFixes available
Linux Linux kernel
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.22-16.12.25-1
Linux Linux kernel>=6.11<6.11.11
Linux Linux kernel>=6.12<6.12.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1
  2. Configuration

    Ensure the kernel dereferences/unregisters the pNFS SCSI block device only after testing the PNFS_BDEV_REGISTERED flag (so an unmount does not attempt unregister for an invalid/NULL block device).

    Linux kernel pNFS blocklayout (nfs/blocklayout) PNFS_BDEV_REGISTERED flag = Use PNFS_BDEV_REGISTERED to guard block device unregistration/cleanup

Event History

Dec 27, 2024
CVE Published
via MITRE·01:49 PM
Data Sourced
via MITRE·01:49 PM
DescriptionSeverity
Data Sourced
via NVD·02:15 PM
Description
Data Sourced
via NVD·02:15 PM
RemedySeverityWeaknessAffected Software
Mar 28, 2025
Data Sourced
via Ubuntu·01:02 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-53167?

CVE-2024-53167 has been classified as a medium severity vulnerability.

2

What impact does CVE-2024-53167 have on affected systems?

CVE-2024-53167 may cause dereferencing issues during the unmount of a pNFS SCSI layout-enabled NFS.

3

How do I fix CVE-2024-53167?

To mitigate CVE-2024-53167, update the Linux kernel to the latest stable version that includes the fix.

4

Which versions of the Linux kernel are affected by CVE-2024-53167?

CVE-2024-53167 affects versions of the Linux kernel prior to the fix being applied in the stable update.

5

Is CVE-2024-53167 part of any known exploitation attempts?

As of now, there are no known active exploitation attempts specific to CVE-2024-53167.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203