Impact
An inadvertent use of uninitialized memory in the Linux kernel’s lock manager caused NLMv4 file handles that are shorter than the defined hashing size to be hashed inconsistently, leading to lock lookup failures and disruption of NFS lock operations; the core weakness is improper initialization of hashing input, which can result in lock state inconsistencies and potential denial of service for clients reliant on NFS locking.
Affected Systems
All Linux kernel releases that were compiled before the inclusion of commit 3de744ee4e45, which introduced the patch that clears uninitialized tail bytes when hashing file handles, are affected; any deployment that uses the NLMv4 protocol with the lock manager (lockd) enabled without this patch is vulnerable.
Risk and Exploitability
The flaw can be triggered by an NLMv4 client that sends a file handle shorter than LOCKD_FH_HASH_SIZE, causing consistent lock state lookup failures; the EPSS score of < 1% indicates a very low probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog, so no confirmed exploits are known, though the kernel nature and potential to break NFS lock services make it a significant risk in comparable threat scenarios. The CVSS score of 9.8 indicates critical severity, underscoring the importance of promptly addressing the issue.
OpenCVE Enrichment