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

- 種別: advisory
- 重大度: medium
- 関連技術: python
- CVE: CVE-2026-112935
- 公開日時: 2026-10-28T21:08:08.000Z
- 情報源: GitHub Advisory Database (https://github.com/advisories/GHSA-fq56-3cx3-fjxp)
- パーマリンク: https://vulnpulse.app/items/ghsa-ghsa-fq56-3cx3-fjxp

影響: 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…