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.
Security readout for executives and security teams
Plain-English summary
A Linux dm-verity forward-error-correction flaw can read beyond a parity-block buffer during recovery. It requires particular non-default FEC settings and a low-memory allocation outcome, so exposure appears narrow. The sources do not establish the resulting security impact or severity.
Executive priority
Track as a targeted kernel remediation rather than an emergency based on current evidence. Promptly assess appliances and embedded systems using dm-verity FEC, then patch confirmed exposures through supported vendor updates. Escalate if vendors report meaningful impact or exploitation.
Technical view
fec_decode_bufs() incorrectly assumes the first Reed-Solomon codeword's parity bytes never cross parity-block boundaries. With certain fec_roots and reduced buffer counts caused by low memory, required parity bytes span blocks and trigger an out-of-bounds read. The referenced kernel changes refactor parity-block reading.
Likely exposure
Potentially exposed systems run an affected Linux kernel, use dm-verity FEC with susceptible non-default fec_roots values, and encounter low memory that reduces allocated buffers. Systems without dm-verity FEC or these conditions are unlikely to reach the flaw. Confirm exact affected versions with vendor guidance because the supplied version data is unusual.
Exploitation context
The bundle reports no CISA KEV listing and provides no evidence of active exploitation or a public exploit. Triggering requires a specific storage configuration and memory-allocation condition. Whether an attacker can reliably control those conditions is not established by the sources.
Researcher notes
The documented example uses 4096-byte blocks, fec_roots=17, and one buffer: 272 parity bytes are consumed per call, eventually leaving 16 bytes where 17 are required. Other susceptible root and buffer-count combinations are listed. No CVSS, CWE, concrete impact, or attacker-controlled path is supplied.
Mitigation direction
Apply a vendor-supported kernel update containing the referenced dm-verity FEC correction.
Check distribution advisories for exact affected and fixed package versions.
Prioritize systems using dm-verity FEC with non-default fec_roots settings.
Avoid unsupported configuration changes unless approved by the platform or device vendor.
Validation and detection
Inventory kernel versions on systems and embedded devices using dm-verity.
Determine whether dm-verity FEC is enabled and record its block size and fec_roots.
Compare deployed kernels with vendor advisories and the referenced stable fixes.
Confirm updated systems contain the corrected parity-block reading logic.
Review testing for low-memory recovery paths involving dm-verity FEC.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-46130 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 28, 2026, 09:35 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.