CVE-2026-68152

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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:

amt: fix use-after-free in AMT delayed works

When an AMT device is removed, pending delayed works can still access the freed amt_dev structure, which may result in kernel crashes or memory corruption.

amt_dev_stop() cancels req_wq and discovery_wq with cancel_delayed_work_sync(), but these works can be scheduled again from event_wq after the cancellation. This allows delayed works to access the freed amt_dev structure after the netdev has been released.

The following is a simple race scenario:

CPU0 CPU1

amt_dev_stop() cancel_delayed_work_sync() amt_event_work() mod_delayed_work(req_wq) free netdev req_wq accesses freed amt_dev

Use disable_delayed_work_sync() in amt_dev_stop() to prevent req_wq and discovery_wq from being queued again and wait for running work items to complete.

The delayed works are disabled after initialization in amt_newlink() and enabled only when the device is successfully opened. This keeps the delayed work lifecycle synchronized with the lifetime of the AMT device.

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 10, 2026

Last Modified

August 17, 2026

Advisory Details (4)

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

amt: fix use-after-free in AMT delayed works - kernel/git/stable/linux.git - Linux kernel stable tree

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

amt: fix use-after-free in AMT delayed works - kernel/git/stable/linux.git - Linux kernel stable tree

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

amt: fix use-after-free in AMT delayed works - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1a644db2cf59f164cdf3c75995bab5aadc097528
generic

amt: fix use-after-free in AMT delayed works - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/006340cf06881b6ff49767d8b6f3c4f7b892670c

Vendor Advisories for CVE-2026-68152(2)

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 35× in last 7d / 41× 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-20 12:33 UTCGHSA enrichment
  2. 2026-08-20 01:23 UTCEG score recompute
  3. 2026-08-20 01:23 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 14:10 UTCGHSA enrichment
  6. 2026-08-19 02:58 UTCGHSA enrichment
  7. 2026-08-18 15:18 UTCEG score recompute
  8. 2026-08-18 15:18 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 04:02 UTCGHSA enrichment
  11. 2026-08-17 16:51 UTCEG score recompute
  12. 2026-08-17 16:51 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 05:40 UTCEG score recompute
  15. 2026-08-17 05:40 UTCGHSA enrichment
  16. 2026-08-17 05:11 UTCEG score recompute
  17. 2026-08-17 05:11 UTCGHSA enrichment
  18. 2026-08-16 18:35 UTCEG score recompute
  19. 2026-08-16 18:35 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 07:24 UTCEG score recompute
  22. 2026-08-16 07:24 UTCGHSA enrichment
  23. 2026-08-15 20:14 UTCGHSA enrichment
  24. 2026-08-15 09:03 UTCEG score recompute
  25. 2026-08-15 09:03 UTCGHSA enrichment
Show 16 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 21:52 UTCGHSA enrichment
  3. 2026-08-14 10:41 UTCEG score recompute
  4. 2026-08-14 10:41 UTCGHSA enrichment
  5. 2026-08-13 23:30 UTCEG score recompute
  6. 2026-08-13 23:30 UTCGHSA enrichment
  7. 2026-08-13 22:45 UTCEG score recompute▲ 7.80
  8. 2026-08-13 22:45 UTCGHSA enrichment
  9. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 17:54 UTCEG score recompute
  12. 2026-08-13 17:54 UTCGHSA enrichment
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-10 13:24 UTCNVD update
  15. 2026-08-10 12:21 UTCEG score recompute
  16. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68152?
CVE-2026-68152 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: amt: fix use-after-free in AMT delayed works When an AMT device is removed, pending delayed works can still access the freed amt_dev structure, which may result in kernel crashes or memory corruption. amtdevstop() cancels reqwq and…
When was CVE-2026-68152 disclosed?
CVE-2026-68152 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68152 actively exploited?
CVE-2026-68152 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 96.6% of all scored CVEs.
What is the CVSS score of CVE-2026-68152?
CVE-2026-68152 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68152?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68152, 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-68152

Explore →

Is Your Infrastructure Affected by CVE-2026-68152?

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

Start Free Scan →Browse All CVEs