Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80916: kcov: fix data corruption and race conditions on PREEMPT_RT

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.18% (FIRST EPSS).
  • Fixed version: Linux Linux 18799e858b407bf355383c9dd6c06477aa437134, 22670d1552fe155822b2abf91f920925f7d067b4, 2eed77fdcb0cc48e8eccb2bcd4b7f2c6d650e84c.

Low priority for now. Upgrade to Linux Linux 18799e858b407bf355383c9dd6c06477aa437134, 22670d1552fe155822b2abf91f920925f7d067b4, 2eed77fdcb0cc48e8eccb2bcd4b7f2c6d650e84c 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: kcov: fix data corruption and race conditions on PREEMPT_RT syzbot is reporting KCOV state corruption on PREEMPT_RT kernels, for the temporary storage used for saving/restoring remote KCOV state is currently allocated as the per-CPU area. On PREEMPT_RT kernels, softirq handlers run as preemptible task threads (e.g., ksoftirqd). If a softirq context preempts a task running a remote KCOV session, it safely saves the task's state into the per-CPU area. However, if that softirq thread is subsequently preempted by a higher- priority softirq thread on the same CPU, the second softirq will overwrite the same per-CPU area, permanently destroying the original task's KCOV state. Fix this data corruption by moving the temporary storage from the per-CPU area to the per-thread area. Since each softirq thread now owns its own task context, nested softirq preemption no longer causes data overwrites. Note that while the temporary storage is now on a per-thread basis, the per-CPU kcov_percpu_data.lock must be retained, for we need to ensure that kcov_remote_start() and kcov_remote_stop() operate atomically without racing against asynchronous interrupts that manipulate the current task's KCOV state. It is likely that GFP_KERNEL allocation by vmalloc_node() in kcov_init() has already called panic() before returning NULL, for there will be no OOM-killable userspace processes when __init function of built-in module runs. But this patch also fixes crashing the kernel when vmalloc_node() in kcov_init() returned NULL, for kcov_init() left per-CPU irq_area == NULL but kcov_remote_start() depends on per-CPU irq_area != NULL, resulting in (1) doing vmalloc() in kcov_remote_start() despite !in_task() context (2) out-of-array-bounds access if (1) succeeded but kcov->remote_size < CONFIG_KCOV_IRQ_AREA_SIZE (3) always leak memory allocated by (1), eventually killing all OOM-killable userspace processes problems.

—No exploit Fix available
Published
Sep 9, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 7th 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.1%

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-80916

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

    • 5.8affected
    • 5ff3b30ab57da82d8db4f14662a2858cabfbc2c0 and later · before ef7048d8a614c5f5a9b20513a5428101a744514eaffected · git
    • 5ff3b30ab57da82d8db4f14662a2858cabfbc2c0 and later · before 8ed3ddf23d39bf5338406bd9f8863d44748cf6ceaffected · git
    • 5ff3b30ab57da82d8db4f14662a2858cabfbc2c0 and later · before 5dc59fc959b2b5742985d7ef24bccd1868217dc2affected · git
    • 5ff3b30ab57da82d8db4f14662a2858cabfbc2c0 and later · before a2fb8222cde23b0001812ed3acb7c0ea36dd94e2affected · git
    • 5ff3b30ab57da82d8db4f14662a2858cabfbc2c0 and later · before 18799e858b407bf355383c9dd6c06477aa437134affected · git
    • 5ff3b30ab57da82d8db4f14662a2858cabfbc2c0 and later · before e11f5b48c82703242a3be7a7ae4b4940b4cb4610affected · git
    • 5ff3b30ab57da82d8db4f14662a2858cabfbc2c0 and later · before 22670d1552fe155822b2abf91f920925f7d067b4affected · git
    • 5ff3b30ab57da82d8db4f14662a2858cabfbc2c0 and later · before f8c9a3ec36b4ee3d4701b9be08f40e7bfbf89761affected · git
    • 5ff3b30ab57da82d8db4f14662a2858cabfbc2c0 and later · before 2eed77fdcb0cc48e8eccb2bcd4b7f2c6d650e84caffected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.107-1~deb12u16.12.107-1~deb12u1
Debian:13linuxbefore 6.12.107-16.12.107-1
Debian:14linuxbefore 7.1.12-17.1.12-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-80919Sep 9, 2026 · drm/amdgpu: fix recursive ww_mutex acquire in amdgpu_devcoredump_format
    0Monitor
  • ← EarlierCVE-2026-80914Sep 9, 2026 · Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready
    35Monitor
  • Later →CVE-2026-80917Sep 9, 2026 · PCI: host-generic: Fix NULL pointer dereference on 32-bit CAM systems
    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 Linux18799e858b407bf355383c9dd6c06477aa437134Vendor (CNA)
Linux Linux22670d1552fe155822b2abf91f920925f7d067b4Vendor (CNA)
Linux Linux2eed77fdcb0cc48e8eccb2bcd4b7f2c6d650e84cVendor (CNA)
Linux Linux5dc59fc959b2b5742985d7ef24bccd1868217dc2Vendor (CNA)
Linux Linux8ed3ddf23d39bf5338406bd9f8863d44748cf6ceVendor (CNA)
Linux Linuxa2fb8222cde23b0001812ed3acb7c0ea36dd94e2Vendor (CNA)
Linux Linuxe11f5b48c82703242a3be7a7ae4b4940b4cb4610Vendor (CNA)
Linux Linuxef7048d8a614c5f5a9b20513a5428101a744514eVendor (CNA)
Linux Linuxf8c9a3ec36b4ee3d4701b9be08f40e7bfbf89761Vendor (CNA)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.107-1~deb12u1 · 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 (8 more)

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

All records