CVE-2026-112911

Description

A flaw was found in filelock. This vulnerability allows a local attacker to manipulate lock state by pre-creating a protocol directory within a shared parent directory. When filelock adopts this untrusted directory, the attacker can alter the protocol state and admit unauthorized concurrent lock holders. This behavior bypasses mutual exclusion protections, potentially leading to concurrent access and data corruption.

Statement

This vulnerability is rated as Moderate impact because successful exploitation requires an unprivileged local attacker to pre-create directory structures in a shared, world-writable location before the victim process initializes the lock. In standard Red Hat environments, workloads operating within isolated container filesystems or using dedicated, user-restricted directories are not exposed to this flaw. Impact is limited to multi-user systems where tasks place file locks in shared temporary locations like /tmp, potentially allowing a local actor to bypass mutual exclusion and induce race conditions.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score6.3N/A6.3
Attack VectorLocalN/ALocal
Attack ComplexityHighN/AHigh
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H

cve.org: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (Other)

When an attacker can control a lock, the program may wait indefinitely until the attacker releases the lock, causing a denial of service to other users of the program. This is especially problematic if there is a blocking operation on the lock.

Frequently Asked Questions

Want to get errata notifications? Sign up here.