CVE-2026-99135

dm-integrity: fix infinite loop on discard with large tag size

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

dm-integrity: fix infinite loop on discard with large tag size

When integrity_metadata handles a discard, it fills a buffer with
DISCARD_FILLER and writes it over the tags, max_blocks blocks at a
time. If the kmalloc fails, the buffer is the on-stack array
checksums_onstack and max_size is set to HASH_MAX_DIGESTSIZE. So if the
tag size is larger than HASH_MAX_DIGESTSIZE, max_blocks is zero, bi_size
is never decremented and the loop never terminates.

Fix this by using sizeof(checksums_onstack) as max_size. The array has
MAX_TAG_SIZE bytes since commit b93b6643e9b5 ("dm integrity: fix a
crash with unusually large tag size"), so max_blocks is at least 1.

Analysis

AI-generated

Technical impact

The kernel device‑mapper integrity module processes discard requests by writing a filler buffer across tags, blocks at a time. When the buffer allocation fails, the module incorrectly sets the maximum block size to HASH_MAX_DIGESTSIZE; if the configured tag size exceeds that value, the block counter never decrements, causing an infinite loop and a system hang. This flaw can be exercised by any discard operation that triggers the logic with a large tag size, leading to a pure denial of service without data loss.

Affected Systems

All Linux kernel installations that enable the dm-integrity subsystem with tag sizes larger than HASH_MAX_DIGESTSIZE are potentially affected. The vulnerability is fixed by a kernel commit that adjusts the calculation of the maximum block size to use the actual on‑stack array size. Therefore, any kernel version prior to that commit on which the device‑mapper is enabled with large tags is vulnerable.

Risk and Exploitability

Based on the description, it is inferred that the attacker would need to issue a discard command on the target device, which typically requires local or privileged access. The likely attack vector is the execution of a discard operation on a device backed by dm-integrity with large tag sizes, triggering the infinite‑loop condition. A successful exploitation would result in a system hang, meeting the denial‑of‑service impact without compromising confidentiality or integrity. The CVSS score of 4.7 indicates moderate severity. The EPSS score is below 1%, suggesting a low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog, further indicating low exploitation likelihood.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a kernel release that includes the commit fixing the tag size handling
  • Reconfigure dm-integrity to use tag sizes no larger than HASH_MAX_DIGESTSIZE so that max_blocks is never zero
  • Monitor the system for unusually high CPU usage or discarding activity and apply kernel updates as soon as available

Generated by OpenCVE AI on October 30, 2026 at 02:16 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
Weaknesses CWE-835
References
Metrics threat_severity

None

cvssV3_1

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

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Weaknesses CWE-458
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix infinite loop on discard with large tag size When integrity_metadata handles a discard, it fills a buffer with DISCARD_FILLER and writes it over the tags, max_blocks blocks at a time. If the kmalloc fails, the buffer is the on-stack array checksums_onstack and max_size is set to HASH_MAX_DIGESTSIZE. So if the tag size is larger than HASH_MAX_DIGESTSIZE, max_blocks is zero, bi_size is never decremented and the loop never terminates. Fix this by using sizeof(checksums_onstack) as max_size. The array has MAX_TAG_SIZE bytes since commit b93b6643e9b5 ("dm integrity: fix a crash with unusually large tag size"), so max_blocks is at least 1.
Title dm-integrity: fix infinite loop on discard with large tag size
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-458

    DEPRECATED: Incorrect Initialization

  • CWE-835

    Loop with Unreachable Exit Condition ('Infinite Loop')

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:42 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 30, 2026, 1:21 PM
Severity
Moderate
Public date
Oct 28, 2026, 10:34 AM