Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Fixed version: Linux Linux 14057268e79654c3e8ea2c9b5204cb9644b2964d, 24c3fa71f9947b0e1f3b954db1b769b44140192e, 3a63a11897c7ba32d1be7a3fdbc48a8b01cf4992.

Low priority for now. Upgrade to Linux Linux 14057268e79654c3e8ea2c9b5204cb9644b2964d, 24c3fa71f9947b0e1f3b954db1b769b44140192e, 3a63a11897c7ba32d1be7a3fdbc48a8b01cf4992 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix event length with forced 8-byte alignment 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 1..100, the number of data field is 8*N, but once id exceeds 100, the number of data field becomes 8*N+4: # 1 buf: 58 00 00 00 80 5e d1 63 (number of data field is 8*1) ... # a buf: 58 ... (number of data field is 8*2) ... # 64 buf: 58 ... (number of data field is 8*13) # 65 buf: 58 ... (number of data field is 8*13+4) After applying this change, the number of data field keeps being 8*N+4 consistently.

—No exploit Fix available
Published
Sep 4, 2026
Updated
Sep 4, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-80876

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.34affected
    • 2271048d1b3b0aabf83d25b29c20646dcabedc05 and later · before 7c9f0ccf9f04142458d2ac3d39414f4acae242f0affected · git
    • 2271048d1b3b0aabf83d25b29c20646dcabedc05 and later · before 24c3fa71f9947b0e1f3b954db1b769b44140192eaffected · git
    • 2271048d1b3b0aabf83d25b29c20646dcabedc05 and later · before 14057268e79654c3e8ea2c9b5204cb9644b2964daffected · git
    • 2271048d1b3b0aabf83d25b29c20646dcabedc05 and later · before dbcb8635b1eb7603818591cf745c7b1d714f7ac6affected · git
    • 2271048d1b3b0aabf83d25b29c20646dcabedc05 and later · before cfada73fabe2ccc06ec77fe2ceaa088689213326affected · git
    • 2271048d1b3b0aabf83d25b29c20646dcabedc05 and later · before ec5e96aee75d27779b9a860307679f13f33adb0caffected · git
    • 2271048d1b3b0aabf83d25b29c20646dcabedc05 and later · before 3a63a11897c7ba32d1be7a3fdbc48a8b01cf4992affected · git
    • 2271048d1b3b0aabf83d25b29c20646dcabedc05 and later · before c37e0a4b79a6bbb96ce5ffe279d7c001e20529e0affected · git
    • before 2.6.34not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-80874Sep 4, 2026 · arm64: dts: renesas: ironhide: Describe inline ECC carveouts
    0Monitor
  • ← EarlierCVE-2026-80875Sep 4, 2026 · ipvs: use parsed transport offset in TCP state lookup
    0Monitor
  • Later →CVE-2026-80877Sep 4, 2026 · afs: Fix vllist leak
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux14057268e79654c3e8ea2c9b5204cb9644b2964dVendor (CNA)
Linux Linux24c3fa71f9947b0e1f3b954db1b769b44140192eVendor (CNA)
Linux Linux3a63a11897c7ba32d1be7a3fdbc48a8b01cf4992Vendor (CNA)
Linux Linux7c9f0ccf9f04142458d2ac3d39414f4acae242f0Vendor (CNA)
Linux Linuxc37e0a4b79a6bbb96ce5ffe279d7c001e20529e0Vendor (CNA)
Linux Linuxcfada73fabe2ccc06ec77fe2ceaa088689213326Vendor (CNA)
Linux Linuxdbcb8635b1eb7603818591cf745c7b1d714f7ac6Vendor (CNA)
Linux Linuxec5e96aee75d27779b9a860307679f13f33adb0cVendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records