96 matches found
Filelock: SoftFileLock Removes A Live Holder's Marker When Another User Forges The PID In A Writable Marker
"SoftFileLock", "MarkerSoftFileLock", "SoftFileLease", their async variants and a "FileLock" that has fallen back to a soft lock on "ENOSYS" decide from the record inside the marker file whether its owner is gone. The marker is the file whose presence says a process holds the lock. They do not...
Filelock: SoftFileLock Stale-lock Break Removes A Live Lock File On A Reused Inode Number And Admits Two Holders
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 "",...
Filelock: Symlink Swap During SoftFileLock's Writability Check Leaks Whether A Path Exists And Is Writable By The Lock T
"raiseonnotwritablefile" is the check that "SoftFileLock" and the locks sharing its acquire path run before every attempt. It looks at the lock path with "os.lstat", so that it judges a planted symlink a file that points at another path by itself. When the node has no owner-write bit, it then cal...
EUVD-2026-105029
filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable marker...
GHSA-RFPC-QCW5-3PC4 filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable marker
SoftFileLock, MarkerSoftFileLock, SoftFileLease, their async variants and a FileLock that has fallen back to a soft lock on ENOSYS decide from the record inside the marker file whether its owner is gone. The marker is the file whose presence says a process holds the lock. They do not check who...
filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable marker
SoftFileLock, MarkerSoftFileLock, SoftFileLease, their async variants and a FileLock that has fallen back to a soft lock on ENOSYS decide from the record inside the marker file whether its owner is gone. The marker is the file whose presence says a process holds the lock. They do not check who...
EUVD-2026-105019
filelock: Symlink swap during SoftFileLock's writability check leaks whether a path exists and is writable by the lock taker...
filelock: Symlink swap during SoftFileLock's writability check leaks whether a path exists and is writable by the lock taker
raiseonnotwritablefile is the check that SoftFileLock and the locks sharing its acquire path run before every attempt. It looks at the lock path with os.lstat, so that it judges a planted symlink a file that points at another path by itself. When the node has no owner-write bit, it then calls...
GHSA-9J6Q-WVJ5-JGJG filelock: Symlink swap during SoftFileLock's writability check leaks whether a path exists and is writable by the lock taker
raiseonnotwritablefile is the check that SoftFileLock and the locks sharing its acquire path run before every attempt. It looks at the lock path with os.lstat, so that it judges a planted symlink a file that points at another path by itself. When the node has no owner-write bit, it then calls...
GHSA-FQ56-3CX3-FJXP filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders
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 presenc...
EUVD-2026-105025
filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders...
filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders
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 presenc...
Filelock: SoftFileLock Stale-break Restore Follows A Swapped-in Symbolic Link And Hard-links A File Of The User Running
When a soft-lock stale break finds that the marker the lock file at "" it renamed aside was a live one recreated by a successor, the restore branch of "breaklockfile" checks the break name with "lstat" a check that reads a name without following a symbolic link and then calls "os.linkbreakpath,...
Filelock: On Windows An Oplock On A Soft Lock's Marker Holds SoftFileLock.acquire() Past Its Timeout And Blocks The Stal
On Windows the soft locks "SoftFileLock", "MarkerSoftFileLock", "SoftFileLease", their async forms, and a "FileLock" that fell back to a soft lock read their marker by path. The marker is the lock file whose presence says a process holds the lock. Each "acquire" attempt that finds a marker opens ...
Filelock: SoftFileLock Evicts A Fresh Lock File Whose Watched Age Another Local User's Pre-dated File Passed On Through
"SoftFileLock" and "MarkerSoftFileLock" evict an unparsable marker the lock file at "", whose presence says a process holds the lock once a waiting contender has watched it unchanged for two seconds. "SoftFileLease" expires a lease the same way. The watch tells two looks apart by the marker's...
filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through inode reuse
SoftFileLock and MarkerSoftFileLock evict an unparsable marker the lock file at , whose presence says a process holds the lock once a waiting contender has watched it unchanged for two seconds. SoftFileLease expires a lease the same way. The watch tells two looks apart by the marker's modificatio...
EUVD-2026-105015
filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through inode reuse...
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
When a soft-lock stale break finds that the marker the lock file at it renamed aside was a live one recreated by a successor, the restore branch of breaklockfile checks the break name with lstat a check that reads a name without following a symbolic link and then calls os.linkbreakpath, lockfile ...
EUVD-2026-105020
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...
SUSE CVE-2026-112906
filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the...