Linux: Out-of-bounds Read
CVE-2026-53224 is a critical-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions b1ca7dcfb335caa2c73d2d1bb5710e6dea2c11e0, dd75066882ecc4ec8df3f5384b4b9fa9579be8f0, 29ab56e7660b6f849c10c46e87e085649df751eb 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.57% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Linux to b1ca7dcfb335caa2c73d2d1bb5710e6dea2c11e0 or dd75066882ecc4ec8df3f5384b4b9fa9579be8f0 or 29ab56e7660b6f849c10c46e87e085649df751eb or 7560afb8cddafd829e709d7ea09230e45a825557, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.18.36 or 7.0.13, whichever matches your release line, or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, b1ca7dcfb335caa2c73d2d1bb5710e6dea2c11e0; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, dd75066882ecc4ec8df3f5384b4b9fa9579be8f0; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 29ab56e7660b6f849c10c46e87e085649df751eb; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 7560afb8cddafd829e709d7ea09230e45a825557; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 512a9bb77c04ac9927648ea58af617e472be96e6; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 6f4c80a2a7e6d06753b89a578b710a2499a5e62b; 2.6.12 | b1ca7dcfb335caa2c73d2d1bb5710e6dea2c11e0, dd75066882ecc4ec8df3f5384b4b9fa9579be8f0, 29ab56e7660b6f849c10c46e87e085649df751eb, 7560afb8cddafd829e709d7ea09230e45a825557, 512a9bb77c04ac9927648ea58af617e472be96e6, 6f4c80a2a7e6d06753b89a578b710a2499a5e62b |
| Linux | Linux Kernel | 2.6.12.1 up to, but not including, 6.18.36; 6.19 up to, but not including, 7.0.13; 2.6.12; 7.1 | 6.18.36, 7.0.13 |
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
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- 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:N/AC:L/PR:N/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: sctp: validate embedded INIT chunk and address list lengths in cookie sctp_unpack_cookie() only checked that the embedded INIT chunk length did not exceed the remaining cookie payload, but did not ensure that the INIT chunk is large enough to contain a complete INIT header. A malformed COOKIE_ECHO can therefore carry a truncated INIT chunk whose length field is smaller than sizeof(struct sctp_init_chunk). Later, sctp_process_init() accesses INIT parameters unconditionally, which may lead to out-of-bounds reads. In addition, raw_addr_list_len is not fully validated against the remaining cookie payload. When cookie authentication is disabled, an attacker can supply an oversized raw_addr_list_len and cause sctp_raw_to_bind_addrs() to read beyond the end of the cookie. The address parser also lacks sufficient bounds checks for parameter headers and lengths, allowing malformed address parameters to trigger out-of-bounds reads. Fix this by: - requiring the embedded INIT chunk length to be at least sizeof(struct sctp_init_chunk); - validating that the INIT chunk and raw address list together fit within the cookie payload; - verifying sufficient data exists for each address parameter header and payload before parsing it. Note that sctp_verify_init() must be called after sctp_unpack_cookie() and before sctp_process_init() when cookie authentication is disabled. This will be addressed in a separate patch.
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: yes, 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
- 7.5 High severity
- 7.1 High severity
- 8.4 High severity
- 9.1 Critical severity
- 8.2 High severity
- 7.1 High severity
Spotted an error? Tell us.