Linux: Out-of-bounds Write
CVE-2026-53148 is a high-severity out-of-bounds write vulnerability in Linux, with a CVSS 3.1 base score of 7.8 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 0b334279a82d79fb4723bd4f614305de1ab69caa, 6021d39ccd979713b39b980286020d8f9a45efd1, 89ae04365e01d5ae4aae83044a8bbd2a9aaf8d0d 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.14% 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 0b334279a82d79fb4723bd4f614305de1ab69caa or 6021d39ccd979713b39b980286020d8f9a45efd1 or 89ae04365e01d5ae4aae83044a8bbd2a9aaf8d0d or 5db10c8ad8c09f72c847dfeef3d876098257f505, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.10.259 or 5.15.210 or 6.1.176 or 6.6.143, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | cdae7c07e3e3509eaabc18c1640a55dc5b99c179 up to, but not including, 0b334279a82d79fb4723bd4f614305de1ab69caa; cdae7c07e3e3509eaabc18c1640a55dc5b99c179 up to, but not including, 6021d39ccd979713b39b980286020d8f9a45efd1; cdae7c07e3e3509eaabc18c1640a55dc5b99c179 up to, but not including, 89ae04365e01d5ae4aae83044a8bbd2a9aaf8d0d; cdae7c07e3e3509eaabc18c1640a55dc5b99c179 up to, but not including, 5db10c8ad8c09f72c847dfeef3d876098257f505; cdae7c07e3e3509eaabc18c1640a55dc5b99c179 up to, but not including, 05a43157676c243c248d1c6d9dcecbe6eba2f35d; cdae7c07e3e3509eaabc18c1640a55dc5b99c179 up to, but not including, fcbd0cdab92838854a5818be7ed8a097164ef6d5; cdae7c07e3e3509eaabc18c1640a55dc5b99c179 up to, but not including, 906035d5c3784570191d259cbf9a0ac1617852b5; cdae7c07e3e3509eaabc18c1640a55dc5b99c179 up to, but not including, 322e93448d908434ae5545660fcbe8f5a7a8e141; and 1 more ranges | 0b334279a82d79fb4723bd4f614305de1ab69caa, 6021d39ccd979713b39b980286020d8f9a45efd1, 89ae04365e01d5ae4aae83044a8bbd2a9aaf8d0d, 5db10c8ad8c09f72c847dfeef3d876098257f505, 05a43157676c243c248d1c6d9dcecbe6eba2f35d, fcbd0cdab92838854a5818be7ed8a097164ef6d5 |
| Red Hat | Red Hat Enterprise Linux 10 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 6 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9 | Not specified in the record | Not stated |
| Siemens | SIMATIC S7-1500 TM MFP - GNU/Linux subsystem | all versions | Not stated |
| Linux | Linux Kernel | 4.15 up to, but not including, 5.10.259; 5.11 up to, but not including, 5.15.210; 5.16 up to, but not including, 6.1.176; 6.2 up to, but not including, 6.6.143; 6.7 up to, but not including, 6.12.94; 6.13 up to, but not including, 6.18.36; 6.19 up to, but not including, 7.0.13; 7.1 | 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36 |
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
- HighData or code can be modified at will.
- 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:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 3.1 | 7.0 | High | CNA |
Official description
In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Clamp XDomain response data copy to allocation size tb_xdp_properties_request() derives the per-packet copy length from the response header without checking that it fits in the previously allocated data buffer. A malicious peer can set its length field larger than the declared data_length, causing memcpy to write past the kcalloc allocation. Clamp the per-packet copy length so that the cumulative offset never exceeds data_len.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
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/05a43157676c243c248d1c6d9dcecbe6eba2f35d
- git.kernel.org/stable/c/0b334279a82d79fb4723bd4f614305de1ab69caa
- git.kernel.org/stable/c/322e93448d908434ae5545660fcbe8f5a7a8e141
- git.kernel.org/stable/c/5db10c8ad8c09f72c847dfeef3d876098257f505
- git.kernel.org/stable/c/6021d39ccd979713b39b980286020d8f9a45efd1
- git.kernel.org/stable/c/89ae04365e01d5ae4aae83044a8bbd2a9aaf8d0d
- git.kernel.org/stable/c/906035d5c3784570191d259cbf9a0ac1617852b5
- git.kernel.org/stable/c/fcbd0cdab92838854a5818be7ed8a097164ef6d5
Third-party and government advisories
- access.redhat.com/security/cve/CVE-2026-53148Third Party Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2492756Third Party Advisory
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53148.jsonThird Party Advisory
Other references
Recent Out-of-bounds Write vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
- 7.1 High severity
- 7.8 High severity
Spotted an error? Tell us.