Servers and applications
CVE-2026-80876
ring-buffer: Fix event length with forced 8-byte alignment
- Severity
- Unrated
- Published
- 4 Sept 2026
- Last changed
- 6 Nov 2026
- Added to UpHeron
- 6 Nov 2026
- Fixed in
- 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5
- Exploit chance
- 0.2% in the next 30 daysHigher than 12% of CVEs. EPSS by FIRST, 19 Nov 2026
- Sources
- CVE Program
Description
In the Linux kernel, the following vulnerability has been resolved:
When RB_FORCE_8BYTE_ALIGNMENT is true, rb_calculate_event_length() reserves the space of event->array[0] for placing the data length and rb_update_event() stores the data length in event->array[0] accordingly. As a result the whole event length will add extra 4 bytes for sizeof(event.array[0]) unconditionally.
But ring_buffer_event_length() only subtracts the sizeof(event->array[0]) for events larger than RB_MAX_SMALL_DATA + sizeof(event->array[0]). As a result, small events on architectures with RB_FORCE_8BYTE_ALIGNMENT=true report a data length that is 4 bytes larger than expected.
To fix it, add the RB_FORCE_8BYTE_ALIGNMENT as a condition to subtract the size of that length field whenever RB_FORCE_8BYTE_ALIGNMENT is true.
This issue is observed in a riscv64 kernel with CONFIG_HAVE_64BIT_ALIGNED_ACCESS set to y, when we run ftrace selftest trace_marker_raw.tc, we get the weird log: for cases where the id is…
Affected software
| Software | Affected versions |
|---|---|
Linux kernelServers and applications · cna:linux|linux |
All 7 release lines
|
About Linux kernel
Unix-like operating system kernel, basis for all Linux operating systems
- GitHub stars
- 255,726GitHub, 15 Nov 2026
- Forks
- 67,394GitHub, 15 Nov 2026
- Developer
- Linus TorvaldsWikidata
- License
- GNU General Public License, version 2.0Wikidata
- Written in
- CWikidata
- First released
- 25 Aug 1991Wikidata
- First published on GitHub
- 4 Sept 2011GitHub
Vulnerabilities in Linux kernel
- In our list
- 2,989
- Published in the last 12 months
- 2,989
- Critical, last 12 months
- 83
- High, last 12 months
- 485
- Known exploited
- 0
- CVE-2026-99804io_uring/io-wq: save worker type before dropping its referenceUnrated 20 Nov 2026
- CVE-2026-99803io_uring/net: mask socket type with SOCK_TYPE_MASK in io_socket_bpf_populate()Unrated 20 Nov 2026
- CVE-2026-99802io_uring/register: enforce per-task restrictions in io_uring_register_blind()Unrated 20 Nov 2026
- CVE-2026-99801io_uring/bpf-ops: clear bpf_ctx while submitting SQEsUnrated 20 Nov 2026
- CVE-2026-99800io_uring: free the task context after a grace periodUnrated 20 Nov 2026
- CVE-2026-99799io_uring/sqpoll: don't wait for the thread to exitUnrated 20 Nov 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-80876