Incorrect ftrace event lengths via alignment miscalculation
Published Sep 4, 2026 · Updated Sep 4, 2026
Incorrect length reporting in affected Linux stable branches causes small ftrace ring-buffer events to report four extra data bytes. The ring_buffer_event_length() path fails to subtract the event->array[0] length field for small events when RB_FORCE_8BYTE_ALIGNMENT is enabled. The condition was observed on riscv64 with CONFIG_HAVE_64BIT_ALIGNED_ACCESS enabled, and the published record identifies no consequence beyond incorrect payload-length reporting.
Summary
What happened
Incorrect length reporting in affected Linux stable branches causes small ftrace ring-buffer events to report four extra data bytes. The ring_buffer_event_length() path fails to subtract the event->array[0] length field for small events when RB_FORCE_8BYTE_ALIGNMENT is enabled. The condition was observed on riscv64 with CONFIG_HAVE_64BIT_ALIGNED_ACCESS enabled, and the published record identifies no consequence beyond incorrect payload-length reporting.
The record
- CVE
- CVE-2026-80876
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2271048d1b3b0aabf83d25b29c20646dcabedc05 <14057268e79654c3e8ea2c9b5204cb9644b2964d
- Affected versionversion=2271048d1b3b0aabf83d25b29c20646dcabedc05 <24c3fa71f9947b0e1f3b954db1b769b44140192e
- Affected versionversion=2271048d1b3b0aabf83d25b29c20646dcabedc05 <3a63a11897c7ba32d1be7a3fdbc48a8b01cf4992
- Affected versionversion=2271048d1b3b0aabf83d25b29c20646dcabedc05 <7c9f0ccf9f04142458d2ac3d39414f4acae242f0
- Affected versionversion=2271048d1b3b0aabf83d25b29c20646dcabedc05 <c37e0a4b79a6bbb96ce5ffe279d7c001e20529e0
- Affected versionversion=2271048d1b3b0aabf83d25b29c20646dcabedc05 <cfada73fabe2ccc06ec77fe2ceaa088689213326
- Affected versionversion=2271048d1b3b0aabf83d25b29c20646dcabedc05 <dbcb8635b1eb7603818591cf745c7b1d714f7ac6
- Affected versionversion=2271048d1b3b0aabf83d25b29c20646dcabedc05 <ec5e96aee75d27779b9a860307679f13f33adb0c
- Affected versionversion=2.6.34
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo