Time-of-check Time-of-use (TOCTOU) Race Condition in filelock - CVE-2026-112935
Published: November 2, 2026
Vulnerability details
The vulnerability allows a local user to bypass mutual exclusion and compromise the integrity of data protected by a file lock by causing two processes to hold the same lock simultaneously.
The vulnerability exists due to a time-of-check time-of-use race condition in filelock's break_lock_file stale-lock handling when checking a marker's inode number and modification time after closing its file descriptor. A local user can create a stale marker in a writable lock directory, set its modification time into the future, and unlink it after a contender reads it, causing a successor's live marker with the reused inode number to be deleted and allowing concurrent access to protected data.
Exploitation requires a filesystem with immediate inode-number reuse, such as ext4 or xfs, and at least two contending processes belonging to the lock user.