Skip to main content
VulnerabilityPublished Updated

CVE-2026-80876: Linux kernel · ring-buffer: Fix event length with forced 8-byte alignment

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ec5e96aee75d27779b9a860307679f13f33adb0c : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:34 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in ec5e96aee75d27779b9a860307679f13f33adb0c, dbcb8635b1eb7603818591cf745c7b1d714f7ac6, cfada73fabe2ccc06ec77fe2ceaa088689213326 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 2271048d1b3b0aabf83d25b29c20646dcabedc05, < ec5e96aee75d27779b9a860307679f13f33adb0c
Fixed in
  • ec5e96aee75d27779b9a860307679f13f33adb0c
LinuxLinuxAffected
  • ≥ 2271048d1b3b0aabf83d25b29c20646dcabedc05, < dbcb8635b1eb7603818591cf745c7b1d714f7ac6
Fixed in
  • dbcb8635b1eb7603818591cf745c7b1d714f7ac6
LinuxLinuxAffected
  • ≥ 2271048d1b3b0aabf83d25b29c20646dcabedc05, < cfada73fabe2ccc06ec77fe2ceaa088689213326
Fixed in
  • cfada73fabe2ccc06ec77fe2ceaa088689213326
LinuxLinuxAffected
  • ≥ 2271048d1b3b0aabf83d25b29c20646dcabedc05, < c37e0a4b79a6bbb96ce5ffe279d7c001e20529e0
Fixed in
  • c37e0a4b79a6bbb96ce5ffe279d7c001e20529e0
LinuxLinuxAffected
  • ≥ 2271048d1b3b0aabf83d25b29c20646dcabedc05, < 14057268e79654c3e8ea2c9b5204cb9644b2964d
Fixed in
  • 14057268e79654c3e8ea2c9b5204cb9644b2964d
LinuxLinuxAffected
  • ≥ 2271048d1b3b0aabf83d25b29c20646dcabedc05, < 24c3fa71f9947b0e1f3b954db1b769b44140192e
Fixed in
  • 24c3fa71f9947b0e1f3b954db1b769b44140192e

AI-suggested

A fix is available and has been applied in specific Linux kernel commits. Users should update to a kernel version that includes the fix identified by the listed commit hashes to resolve the issue. No additional mitigation steps are necessary as the patch corrects the event length calculation.

Description

A vulnerability in the Linux kernel's ring-buffer event length calculation was fixed. The issue caused small events on architectures with forced 8-byte alignment to report a data length 4 bytes larger than expected, leading to inconsistent event data length reporting. This was observed on riscv64 kernels with 64-bit aligned access enabled. The fix ensures consistent event length accounting by adjusting the calculation when RB_FORCE_8BYTE_ALIGNMENT is true.

References

Community reviews

Loading reviews…