CVE-2026-80622

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

char: tlclk: fix use-after-free in tlclk_cleanup()

This patch improves the module cleanup process in the tlclk driver to prevent potential use-after-free and race conditions.

Currently, the file_operations structure does not specify the .owner field, which could allow the module to be unloaded while user-space processes are still interacting with the device. Additionally, the tlclk_cleanup() function frees the alarm_events memory before ensuring that blocked processes in the waitqueue are fully awakened and that the switchover_timer has completed.

To address these cases, this patch:

  • Sets '.owner = THIS_MODULE' in tlclk_fops to safely defer module
unloading while the device is in use.
  • Updates tlclk_cleanup() to explicitly wake up all blocked readers
(wake_up_all), properly release hardware I/O regions, and safely delete the timer (timer_delete_sync) prior to freeing memory.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (8)

Auto-updated Aug 29, 2026
No patch confirmed yet.
generic

char: tlclk: fix use-after-free in tlclk_cleanup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bbf003b7794d6ad6f939fdd29f1f1bde8ac554c1
generic

char: tlclk: fix use-after-free in tlclk_cleanup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42223445607a9a5df3cb1c4729abfe3a5085e7ce
generic

char: tlclk: fix use-after-free in tlclk_cleanup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d5e4cc0d9dce79b0429da3134ac7b072ab9009f
generic

char: tlclk: fix use-after-free in tlclk_cleanup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c3f0cd76561ae611c2d247ee96dfd559e4197cb7
generic

char: tlclk: fix use-after-free in tlclk_cleanup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/764723bd67a6c8f53a8d8309211fb039e2ebcf49
generic

char: tlclk: fix use-after-free in tlclk_cleanup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/166dd1d5265e067459e674c11688919901813ec2
generic

char: tlclk: fix use-after-free in tlclk_cleanup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96902299a22d126ef5eb3f45cd5d8ceea9e6a735
generic

char: tlclk: fix use-after-free in tlclk_cleanup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/09d8d2a46a9ec9ff728f3159a174a2ab25dd0f0a

Vendor Advisories for CVE-2026-80622(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 20:40 UTCEG score recompute
  3. 2026-08-29 20:40 UTCGHSA enrichment
  4. 2026-08-29 07:27 UTCEG score recompute
  5. 2026-08-29 07:27 UTCGHSA enrichment
  6. 2026-08-29 06:37 UTCEG score recompute▲ 7.80
  7. 2026-08-29 06:36 UTCGHSA enrichment
  8. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  9. 2026-08-28 21:42 UTCEPSS rescore
  10. 2026-08-28 08:20 UTCNVD update
  11. 2026-08-28 07:34 UTCEG score recompute
  12. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80622?
CVE-2026-80622 is a high vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: char: tlclk: fix use-after-free in tlclk_cleanup() This patch improves the module cleanup process in the tlclk driver to prevent potential use-after-free and race conditions. Currently, the file_operations structure does not…
When was CVE-2026-80622 disclosed?
CVE-2026-80622 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80622 actively exploited?
CVE-2026-80622 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-80622?
CVE-2026-80622 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-80622?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80622, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-80622

Explore →

Is Your Infrastructure Affected by CVE-2026-80622?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs