CVE-2026-46130

dm-verity-fec: fix reading parity bytes split across blocks (take 3)

HIGH
7.1
CVSS Score
Published: May 28, 2026 at 09:35 AM UTC
Updated: October 21, 2026 at 01:19 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: dm-verity-fec: fix reading parity bytes split across blocks (take 3) fec_decode_bufs() assumes that the parity bytes of the first RS codeword it decodes are never split across parity blocks. This assumption is false. Consider v->fec->block_size == 4096 && v->fec->roots == 17 && fio->nbufs == 1, for example. In that case, each call to fec_decode_bufs() consumes v->fec->roots * (fio->nbufs << DM_VERITY_FEC_BUF_RS_BITS) = 272 parity bytes. Considering that the parity data for each message block starts on a block boundary, the byte alignment in the parity data will iterate through 272*i mod 4096 until the 3 parity blocks have been consumed. On the 16th call (i=15), the alignment will be 4080 bytes into the first block. Only 16 bytes remain in that block, but 17 parity bytes will be needed. The code reads out-of-bounds from the parity block buffer. Fortunately this doesn't normally happen, since it can occur only for certain non-default values of fec_roots *and* when the maximum number of buffers couldn't be allocated due to low memory. For example with block_size=4096 only the following cases are affected: fec_roots=17: nbufs in [1, 3, 5, 15] fec_roots=19: nbufs in [1, 229] fec_roots=21: nbufs in [1, 3, 5, 13, 15, 39, 65, 195] fec_roots=23: nbufs in [1, 89] Regardless, fix it by refactoring how the parity blocks are read.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.1.125 ≤ v < 6.26.12.10 ≤ v < 6.136.13.1 ≤ v < 7.0.76.6.72 ≤ v < 6.712caa73a28f0ae147ec0356b45091edf2462462b6.1.1256.12.106.136.13 rc76.6.726bc6ee31113b05db605694491bdeb2b1730142f16df90c02bae468a3a6110bafbc659884d0c4966cfc8943886629e26de34867db302c74d465510826
Vendor states this is fixed in 3d1b4e2d8ac0a1a1390a117f61ce0ca1c47e3bcb (fixed)
Vendor states this is fixed in 430a05cb926f6bdf53e81460a2c3a553257f3f61 (fixed)
Vendor states this is fixed in d47281b9a4472cfd73122393e79fbe76b651e46a (fixed)
Vendor states this is fixed in 6.12.114 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.160 (unaffected)
Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.0.7 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusUNDERGOING ANALYSIS
CWE
CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card