AI Science Tracker

filelock SoftFileLock stale-marker inode reuse can admit concurrent holders

filelock SoftFileLock, MarkerSoftFileLock, SoftFileLease · AI involvement attributed to Anthropic OSS Scanner

Finding and attribution

A local user able to create files in a shared sticky lock directory can create an empty marker and set its modification time to a future coarse-clock tick. On a filesystem that immediately reuses inode numbers, the next legitimate marker can inherit the same (mtime,inode) pair, and a waiting process may treat it as the aged attacker marker and remove it while its owner holds the lock. Two lock users can then enter the critical section concurrently. The advisory reports ext4/overlayfs-on-ext4 conditions; it also reports zero hits in the maintainer’s 250-attempt ext4 run, while the scanner’s reproducer produced overlaps.

Product: filelock SoftFileLock, MarkerSoftFileLock, SoftFileLease. AI system: Anthropic OSS Scanner. Team / organization: Anthropic.

CVE identifiers: CVE-2026-112906.

AI and human contribution (source account): The maintainer advisory says reported by Anthropic’s OSS Scanner (automated analysis), ANT-2026-RKC48J5B, received 2026-10-15; maintainers reviewed it. This directly attributes automated AI-assisted analysis and preserves that human review/reproduction was mixed.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The advisory documents the flaw and patch; it does not report observed exploitation.

Remediation status: fix documented. Fixed in filelock 4.2.1 (PR #843). A private lock directory or filesystem without immediate inode reuse is a workaround. StrictSoftFileLock does not break a lock through this path.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 17 Oct 2026. AI attribution dated 17 Oct 2026. Sources checked 16 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Medium · highest recorded score 4.7. Documented technical effects: other.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • CVE-2026-112906: CVSS 3.1 · 4.7 (Medium) · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N. filelock maintainer advisory · checked 16 Nov 2026.

CVE-2026-112906: other.
Prerequisites / affected scope: Source records a local cross-account lock-integrity failure under the version and filesystem or permission conditions stated in the summary..
Exploitation evidence: No observed exploitation is reported.. Impact source · checked 16 Nov 2026.

Documented fix: Fixed in filelock 4.2.1 (PR #843). A private lock directory or filesystem without immediate inode reuse is a workaround. StrictSoftFileLock does not break a lock through this path.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases