CVE-2026-43210: Linux kernel · tracing: ring-buffer: Fix to check event length before using
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 11 Nov 2026, 23:06 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 6 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
Description
In the Linux kernel, the following vulnerability has been resolved: tracing: ring-buffer: Fix to check event length before using Check the event length before adding it for accessing next index in rb_read_data_buffer(). Since this function is used for validating possibly broken ring buffers, the length of the event could be broken. In that case, the new event (e + len) can point a wrong address. To avoid invalid memory access at boot, check whether the length of each event is in the possible range before using it.
References
- git.kernel.org/stable/c/b4700c089a10f89de3a5149d57f8a58306458982 (opens in a new tab)
- git.kernel.org/stable/c/5026010110a5ad2268d8c23e1e286ab7c736f7ac (opens in a new tab)
- git.kernel.org/stable/c/9eb80e54494ef1efef8a64bec4ffa672c9cf411e (opens in a new tab)
- git.kernel.org/stable/c/912b0ee248c529a4f45d1e7f568dc1adddbf2a4a (opens in a new tab)