CVE-2026-68259

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: 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:

drm/amdkfd: Check bounds in allocate_event_notification_slot

The valid event ids go from 0 to KFD_SIGNAL_EVENT_LIMIT

allocate_event_notification_slot has an option to specify an event id to allocate at, used by CRIU. We weren't checking the bounds on that value.

Check them.

v2: Lower bounds check is unecessary because of idr_alloc already rejecting negative numbers. Upper bounds check should be KFD_SIGNAL_EVENT_LIMIT since the signal mode mappings might not yet exist

(cherry picked from commit 6853f1f6cbbeb3f53ebbbd7286536aeb2c5d5f50)

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

References (6)

Vendor Advisories for CVE-2026-68259(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 20× in last 7d / 26× 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-19 17:25 UTCGHSA enrichment
  2. 2026-08-19 17:21 UTCNVD update
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-19 16:54 UTCGHSA enrichment
  5. 2026-08-19 16:43 UTCMITRE cvelistV5
  6. 2026-08-18 13:49 UTCEPSS rescore
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-18 07:25 UTCGHSA enrichment
  9. 2026-08-18 07:25 UTCNVD update
  10. 2026-08-18 07:03 UTCGHSA enrichment
  11. 2026-08-18 07:01 UTCMITRE cvelistV5
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 05:37 UTCGHSA enrichment
  14. 2026-08-17 05:26 UTCNVD update
  15. 2026-08-17 05:07 UTCGHSA enrichment
  16. 2026-08-17 05:05 UTCMITRE cvelistV5
  17. 2026-08-16 21:50 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 17:39 UTCEG score recompute
  22. 2026-08-13 17:39 UTCGHSA enrichment
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-10 13:24 UTCNVD update
  25. 2026-08-10 12:19 UTCEG score recompute
Show 1 more
  1. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-68259?
CVE-2026-68259 is a publicly disclosed vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Check bounds in allocateeventnotification_slot The valid event ids go from 0 to KFDSIGNALEVENT_LIMIT allocateeventnotification_slot has an option to specify an event id to allocate at, used by CRIU. We weren't checking…
When was CVE-2026-68259 disclosed?
CVE-2026-68259 was first published in the National Vulnerability Database on August 10, 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-68259 actively exploited?
CVE-2026-68259 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 93.5% of all scored CVEs.
How do I remediate CVE-2026-68259?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68259, 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-68259

Explore →

Is Your Infrastructure Affected by CVE-2026-68259?

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

Start Free Scan →Browse All CVEs