Bug 2467162 (CVE-2026-43210) - CVE-2026-43210 kernel: tracing: ring-buffer: Fix to check event length before using
Summary: CVE-2026-43210 kernel: tracing: ring-buffer: Fix to check event length before...
Keywords:
Status: NEW
Alias: CVE-2026-43210
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-06 13:07 UTC by OSIDB Bzimport
Modified: 2026-05-06 21:45 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-05-06 13:07:47 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.