CVE-2026-74490

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.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: 8.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:

tipc: avoid use-after-free in poll trace queue dumps

TIPC socket tracepoints dump queue state through tipc_sk_dump(). Most queue-dump callsites already serialize that walk under the socket lock or sk->sk_lock.slock, but tipc_poll() calls trace_tipc_sk_poll(..., TIPC_DUMP_ALL, ...) without holding either lock.

That lets the poll trace path reach tipc_list_dump() and backlog head/tail dumping while another context dequeues and frees an skb, leaving the trace helper dereferencing a stale queue entry.

Stop the unlocked poll trace site from requesting queue dumps. Other queue dump trace callsites keep their existing output under the locking they already provide, while poll still emits the event itself without walking live queue members from an unlocked context.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 19, 2026

Advisory Details (5)

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

tipc: avoid use-after-free in poll trace queue dumps - kernel/git/stable/linux.git - Linux kernel stable tree

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

tipc: avoid use-after-free in poll trace queue dumps - kernel/git/stable/linux.git - Linux kernel stable tree

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

tipc: avoid use-after-free in poll trace queue dumps - kernel/git/stable/linux.git - Linux kernel stable tree

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

tipc: avoid use-after-free in poll trace queue dumps - kernel/git/stable/linux.git - Linux kernel stable tree

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

tipc: avoid use-after-free in poll trace queue dumps - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5e82beba4bc1f91d0e64c9c43f2b2fa9cd1c2a7d

Vendor Advisories for CVE-2026-74490(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 32× in last 7d / 32× 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-21 05:51 UTCEG score recompute
  2. 2026-08-21 05:51 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 17:46 UTCGHSA enrichment
  5. 2026-08-20 05:43 UTCGHSA enrichment
  6. 2026-08-19 17:38 UTCEG score recompute
  7. 2026-08-19 17:38 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 16:53 UTCEG score recompute
  10. 2026-08-19 16:53 UTCGHSA enrichment
  11. 2026-08-19 07:07 UTCGHSA enrichment
  12. 2026-08-18 19:03 UTCEG score recompute
  13. 2026-08-18 19:03 UTCGHSA enrichment
  14. 2026-08-18 13:49 UTCEPSS rescore
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-18 06:58 UTCGHSA enrichment
  17. 2026-08-17 18:54 UTCEG score recompute
  18. 2026-08-17 18:54 UTCGHSA enrichment
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 06:24 UTCEG score recompute
  21. 2026-08-17 06:24 UTCGHSA enrichment
  22. 2026-08-17 05:55 UTCEG score recompute 8.80
  23. 2026-08-17 05:55 UTCGHSA enrichment
  24. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  25. 2026-08-17 05:40 UTCEG score recompute
Show 7 more
  1. 2026-08-17 05:40 UTCGHSA enrichment
  2. 2026-08-17 05:39 UTCMITRE cvelistV5
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-15 13:27 UTCNVD update
  6. 2026-08-15 12:40 UTCEG score recompute
  7. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74490?
CVE-2026-74490 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: tipc: avoid use-after-free in poll trace queue dumps TIPC socket tracepoints dump queue state through tipcskdump(). Most queue-dump callsites already serialize that walk under the socket lock or sk->sklock.slock, but tipcpoll()…
When was CVE-2026-74490 disclosed?
CVE-2026-74490 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74490 actively exploited?
CVE-2026-74490 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 62.0% of all scored CVEs.
What is the CVSS score of CVE-2026-74490?
CVE-2026-74490 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-74490?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74490, 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-74490

Explore →

Is Your Infrastructure Affected by CVE-2026-74490?

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