filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own files

filelock has TOCTOU race condition that allows symlink attacks during lock file creation

filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion

filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name

filelock: ReadWriteLock follows a symlink at the lock path into SQLite

filelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its record

filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock path

filelock ReadWriteLock: a crafted lock database makes every acquire stall or hang regardless of timeout

filelock: SoftFileLock stale-break restore follows a swapped-in symbolic link and hard-links a file of the user running the lock into the lock directory

filelock Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLock

filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable marker

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

filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through inode reuse

filelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into directories of the user running the lock

filelock: Symlink swap during SoftFileLock's writability check leaks whether a path exists and is writable by the lock taker