Linux: Out-of-bounds Read
CVE-2026-46130 is a high-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 03348b440f69417dc3a3c71d8271cff6b05f67fb, dac69d1b76049d7e5f565089a6a7f4502a85b9de, d47281b9a4472cfd73122393e79fbe76b651e46a as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.13% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 03348b440f69417dc3a3c71d8271cff6b05f67fb or dac69d1b76049d7e5f565089a6a7f4502a85b9de or d47281b9a4472cfd73122393e79fbe76b651e46a or 3d1b4e2d8ac0a1a1390a117f61ce0ca1c47e3bcb, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.2 or 6.7 or 6.13 or 7.0.7, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 12caa73a28f0ae147ec0356b45091edf2462462b up to, but not including, 03348b440f69417dc3a3c71d8271cff6b05f67fb; fc8943886629e26de34867db302c74d465510826 up to, but not including, dac69d1b76049d7e5f565089a6a7f4502a85b9de; 6df90c02bae468a3a6110bafbc659884d0c4966c up to, but not including, d47281b9a4472cfd73122393e79fbe76b651e46a; 6df90c02bae468a3a6110bafbc659884d0c4966c up to, but not including, 3d1b4e2d8ac0a1a1390a117f61ce0ca1c47e3bcb; 6df90c02bae468a3a6110bafbc659884d0c4966c up to, but not including, 430a05cb926f6bdf53e81460a2c3a553257f3f61; 6bc6ee31113b05db605694491bdeb2b1730142f1; 6.6.72 up to, but not including, 6.6.160; 6.12.10 up to, but not including, 6.12.114; and 2 more ranges | 03348b440f69417dc3a3c71d8271cff6b05f67fb, dac69d1b76049d7e5f565089a6a7f4502a85b9de, d47281b9a4472cfd73122393e79fbe76b651e46a, 3d1b4e2d8ac0a1a1390a117f61ce0ca1c47e3bcb, 430a05cb926f6bdf53e81460a2c3a553257f3f61, 6.6.160 |
| Linux | Linux Kernel | 6.1.125 up to, but not including, 6.2; 6.6.72 up to, but not including, 6.7; 6.12.10 up to, but not including, 6.13; 6.13.1 up to, but not including, 7.0.7; 6.13 | 6.2, 6.7, 6.13, 7.0.7 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Recent Out-of-bounds Read vulnerabilities
- 8.3 High severity
- 8.8 High severity
- 8.8 High severity
- 8.3 High severity
- 8.3 High severity
- 9.6 Critical severity
Spotted an error? Tell us.