CVE-2026-80661

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:

ufs: core: tracing: Do not dereference pointers in TP_printk()

The trace events in drivers/ufs/core/ufs_trace.h were converted to take a pointer to the hba structure as an argument for the tracepoint and then in TP_printk() the printing of the dev_name from the ring buffer was converted to using the dev dereferenced pointer from the hba saved pointer.

This is not allowed as the TP_printk() is executed at the time the trace event is read from /sys/kernel/tracing/trace file. That can happen literally, seconds, minutes, hours, weeks, days, or even months later! There is no guarantee that the hba pointer will still exist by the time it is dereferenced when the "trace" file is read.

Instead, save the device name from the hba pointer at the time the tracepoint is called and place it into the ring buffer event. Then the TP_printk() can read the name directly from the ring buffer and remove the possibility that it will read a freed pointer and crash the kernel.

This was detected when testing the trace event code that looks for TP_printk() parameters doing illegal derferences[1]

[1] https://lore.kernel.org/all/[email protected]/

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 (3)

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

ufs: core: tracing: Do not dereference pointers in TP_printk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/535fcf4b8a261fbb8cc4f91e4597343c135a90f2
generic

ufs: core: tracing: Do not dereference pointers in TP_printk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2510434307a224078302019e52ab3c863fbe87fb
generic

ufs: core: tracing: Do not dereference pointers in TP_printk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e497fef9ad7e913f52de6f97e818f56915e96164

Vendor Advisories for CVE-2026-80661(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 19:32 UTCEG score recompute
  3. 2026-08-29 19:32 UTCGHSA enrichment
  4. 2026-08-29 07:26 UTCEG score recompute
  5. 2026-08-29 07:26 UTCGHSA enrichment
  6. 2026-08-29 06:36 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-80661?
CVE-2026-80661 is a high vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: ufs: core: tracing: Do not dereference pointers in TP_printk() The trace events in drivers/ufs/core/ufs_trace.h were converted to take a pointer to the hba structure as an argument for the tracepoint and then in TPprintk() the…
When was CVE-2026-80661 disclosed?
CVE-2026-80661 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-80661 actively exploited?
CVE-2026-80661 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.4% of all scored CVEs.
What is the CVSS score of CVE-2026-80661?
CVE-2026-80661 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-80661?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80661, 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-80661

Explore →

Is Your Infrastructure Affected by CVE-2026-80661?

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