UNIX Hard Link in filelock - CVE-2026-112934
Published: November 2, 2026
Vulnerability details
The vulnerability allows a local user to cause a denial of service, disrupt lock exclusivity, and conditionally corrupt files writable by the locking process.
The vulnerability exists due to improper validation of reopened file types and identities in the holder-record refresh mechanism used by SoftReadWriteLock and AsyncSoftReadWriteLock when refreshing records during acquisition polling or heartbeats. A local user can rename a FIFO or hard link over a holder record in a lock tree they control to block acquisition beyond its timeout, stall heartbeats without notifying the holder of eviction, or overwrite the beginning of a target file with holder-record data.
The hard-link variant additionally requires a kernel policy that permits creating hard links to files owned by another user.