VDB

CVE-2026-80916

CVE-2026-80916 PUBLISHED

kcov: fix data corruption and race conditions on PREEMPT_RT

Reported by linux · Published September 9, 2026

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.

EPSS 0.18% · 7.8th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
bpftoolAmazon Linux1:6.1.186-228.374.amzn2023

Risk scores

EPSS Score
0.18%
7.8th percentile

Affected products

VendorProductVersions
LinuxLinux5ff3b30ab57da82d8db4f14662a2858cabfbc2c0, 5ff3b30ab57da82d8db4f14662a2858cabfbc2c0, 5ff3b30ab57da82d8db4f14662a2858cabfbc2c0
LinuxLinux5.8, 0, 5.10.269
amazon:2023bpftool0
LinuxLinux7.3, 5ff3b30ab57da82d8db4f14662a2858cabfbc2c0, 5ff3b30ab57da82d8db4f14662a2858cabfbc2c0
amazon:2023python3-perf0
amazon:2023kernel0
amazon:2023kernel-headers0
amazon:2023kernel-livepatch-6.1.186-228.3740
amazon:2023kernel-tools-devel0
amazon:2023kernel-modules-extra0
amazon:2023kernel-modules-extra-common0
amazon:2023perf0
amazon:2023kernel-tools0
amazon:2023kernel-devel0
linuxlinux_kernel5.8, 5.8, 5.8

Timeline

  • Sep 9, 2026 Coalition ESS Score
  • Sep 9, 2026 CVE Published
  • Sep 10, 2026 EPSS Score (13 in total, the first dated here)
  • Sep 15, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-80916
vulnetix vdb fixes CVE-2026-80916

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80916/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›