filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders

影響: pip:filelock >= 3.22.0, <= 4.2.0 → 4.2.1

The stale-lock break shared by SoftFileLock, MarkerSoftFileLock and SoftFileLease (and their async variants, and a FileLock that has fallen back to a soft lock on ENOSYS, the "not implemented" error) recognises the marker it judged stale by two values. The marker is the lock file at , whose presence says a process holds the lock. The values are its inode number (the kernel's identity for a file, independent of its name) and its modification time (mtime) not being newer. The check runs after the…

Read on GitHub Advisory Database

On 10/29/2026, 06:08 AM, GitHub Advisory Database published "filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders" (type: Advisory). Severity is "Medium" (medium). Related technologies: Python. CVE: CVE-2026-112935.