Linux: Out-of-bounds Read
CVE-2026-53076 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 d138ea2fe01c254413d5a6104eb236e0d5c7dd9a, e19c5ed9f1922a6854073f8651a63fa7be26e9e9, e0378419b0e20178b5d100b27c9cc7e51064202e 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.12% 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 d138ea2fe01c254413d5a6104eb236e0d5c7dd9a or e19c5ed9f1922a6854073f8651a63fa7be26e9e9 or e0378419b0e20178b5d100b27c9cc7e51064202e or 6086079e6d1c32ba4c4b422612b8aebb1129a96c, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.5 or 5.10 or 6.6.141 or 6.12.91, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | d3bec0138bfbe58606fc1d6f57a4cdc1a20218db up to, but not including, d138ea2fe01c254413d5a6104eb236e0d5c7dd9a; d3bec0138bfbe58606fc1d6f57a4cdc1a20218db up to, but not including, e19c5ed9f1922a6854073f8651a63fa7be26e9e9; d3bec0138bfbe58606fc1d6f57a4cdc1a20218db up to, but not including, e0378419b0e20178b5d100b27c9cc7e51064202e; d3bec0138bfbe58606fc1d6f57a4cdc1a20218db up to, but not including, 6086079e6d1c32ba4c4b422612b8aebb1129a96c; d3bec0138bfbe58606fc1d6f57a4cdc1a20218db up to, but not including, 634a793d0e1c822412095d25a1338f8831ad894c; d3bec0138bfbe58606fc1d6f57a4cdc1a20218db up to, but not including, 576afddfee8d1108ee299bf10f581593540d1a36; c602ad2b52dcbca5af08e5137bd5575c039b52e3; ab68b940dd6f7b5f8e2557937162dcb8a0583a05; and 3 more ranges | d138ea2fe01c254413d5a6104eb236e0d5c7dd9a, e19c5ed9f1922a6854073f8651a63fa7be26e9e9, e0378419b0e20178b5d100b27c9cc7e51064202e, 6086079e6d1c32ba4c4b422612b8aebb1129a96c, 634a793d0e1c822412095d25a1338f8831ad894c, 576afddfee8d1108ee299bf10f581593540d1a36 |
| Linux | Linux Kernel | 5.4.78 up to, but not including, 5.5; 5.9.9 up to, but not including, 5.10; 5.10.1 up to, but not including, 6.6.141; 6.7 up to, but not including, 6.12.91; 6.13 up to, but not including, 6.18.33; 6.19 up to, but not including, 7.0.10; 5.10 | 5.5, 5.10, 6.6.141, 6.12.91, 6.18.33, 7.0.10 |
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 CNA.
Official description
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix OOB in pcpu_init_value An out-of-bounds read occurs when copying element from a BPF_MAP_TYPE_CGROUP_STORAGE map to another pcpu map with the same value_size that is not rounded up to 8 bytes. The issue happens when: 1. A CGROUP_STORAGE map is created with value_size not aligned to 8 bytes (e.g., 4 bytes) 2. A pcpu map is created with the same value_size (e.g., 4 bytes) 3. Update element in 2 with data in 1 pcpu_init_value assumes that all sources are rounded up to 8 bytes, and invokes copy_map_value_long to make a data copy, However, the assumption doesn't stand since there are some cases where the source may not be rounded up to 8 bytes, e.g., CGROUP_STORAGE, skb->data. the verifier verifies exactly the size that the source claims, not the size rounded up to 8 bytes by kernel, an OOB happens when the source has only 4 bytes while the copy size(4) is rounded up to 8.
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
- git.kernel.org/stable/c/576afddfee8d1108ee299bf10f581593540d1a36
- git.kernel.org/stable/c/6086079e6d1c32ba4c4b422612b8aebb1129a96c
- git.kernel.org/stable/c/634a793d0e1c822412095d25a1338f8831ad894c
- git.kernel.org/stable/c/e0378419b0e20178b5d100b27c9cc7e51064202e
- git.kernel.org/stable/c/e19c5ed9f1922a6854073f8651a63fa7be26e9e9
Other references
Recent Out-of-bounds Read vulnerabilities
- 8.8 High severity
- 7.8 High severity
- 7.1 High severity
- 9.1 Critical severity
- 7.1 High severity
- 8.1 High severity
Spotted an error? Tell us.