CVE-2026-99136

dm-crypt: fix a tiny race condition in crypt_dec_pending

Published Oct 28, 2026 CVSS 3.1 · 7 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

dm-crypt: fix a tiny race condition in crypt_dec_pending

crypt_dec_pending reads io->error before calling atomic_dec_and_test.
Another context, for example crypt_endio called from an interrupt, may
set io->error and drop its reference between the read and the
decrement. crypt_dec_pending then drops the last reference and completes
the bio with the stale status - so a read that failed and was never
decrypted, or a write that failed, is reported as successful.

The read was placed before the decrement by commit b35f8caa0890 ("dm
crypt: wait for endio to complete before destruction"), because that
commit freed dm_crypt_io before calling bio_endio. This is no longer the
case, dm_crypt_io lives in the per-bio data now.

Read io->error after atomic_dec_and_test instead. atomic_dec_and_test is
fully ordered, so no additional barrier is needed.

Analysis

AI-generated

Technical impact

A race condition in the Linux dm‑crypt subsystem occurs when the function crypt_dec_pending reads the I/O error status before decrementing a reference counter. Because the operation may be interrupted, a stale error value can remain and cause a failed read or write to be reported as successful. This improper status reporting can lead to data integrity problems or mis‑trust in the encryption layer. The weakness is a classic race condition (CWE-366).

Affected Systems

All versions of the Linux kernel that contain the dm‑crypt module prior to the fix commit are affected. The specific affected releases are not enumerated in the advisory, but the issue applies to any kernel using the legacy dm‑crypt implementation.

Risk and Exploitability

The CVSS score is 7 and the EPSS score is < 1%. Based on these metrics, the severity is medium to high and the likelihood of exploitation remains low. The vulnerability is internal to the kernel and does not provide direct code execution or privilege escalation. It is inferred that a malicious actor would need to manipulate concurrent encrypted I/O operations to trigger the race condition, making exploitation unlikely in typical use. The issue is not listed in CISA KEV, indicating no widespread incidents have been reported.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a kernel update that includes the dm‑crypt race condition fix.
  • Check system logs for any instances where encrypted I/O reports success after failure and remediate corresponding data integrity issues.
  • If an immediate update is not feasible, schedule maintenance to upgrade the kernel when operational constraints allow, and consider reducing concurrent cryptographic I/O to lower the chance of the race condition.

Generated by OpenCVE AI on October 31, 2026 at 13:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
Debian DLA Debian DLA DLA-4906-1 linux security update
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 2.5, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N'}

cvssV3_1

{'score': 7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-362
Type Values Removed Values Added
Weaknesses CWE-366
References
Metrics threat_severity

None

cvssV3_1

{'score': 2.5, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N'}

threat_severity

Low

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Weaknesses CWE-362
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: dm-crypt: fix a tiny race condition in crypt_dec_pending crypt_dec_pending reads io->error before calling atomic_dec_and_test. Another context, for example crypt_endio called from an interrupt, may set io->error and drop its reference between the read and the decrement. crypt_dec_pending then drops the last reference and completes the bio with the stale status - so a read that failed and was never decrypted, or a write that failed, is reported as successful. The read was placed before the decrement by commit b35f8caa0890 ("dm crypt: wait for endio to complete before destruction"), because that commit freed dm_crypt_io before calling bio_endio. This is no longer the case, dm_crypt_io lives in the per-bio data now. Read io->error after atomic_dec_and_test instead. atomic_dec_and_test is fully ordered, so no additional barrier is needed.
Title dm-crypt: fix a tiny race condition in crypt_dec_pending
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-366

    Race Condition within a Thread

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 31, 2026, 12:43 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 31, 2026, 1:17 PM
Severity
Low
Public date
Oct 28, 2026, 10:34 AM