CVE-2026-68200

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-55301 (ENISA EUVD) · GHSA-78vp-jqhh-pcc3 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ALSA: timer: don't re-enter an instance callback that is still running

The userspace-driven timer (utimer) TRIGGER ioctl calls snd_timer_interrupt() directly with no serialization, so two threads triggering the same utimer can run snd_timer_interrupt() on one snd_timer concurrently.

snd_timer_process_callbacks() drops timer->lock around each instance callback and marks the in-flight callback with the single SNDRV_TIMER_IFLG_CALLBACK bit; snd_timer_close_locked() waits on that bit to drain an in-flight callback before freeing the instance. The bit cannot represent two concurrent callbacks: when a second interrupt re-queues an instance whose callback is still running, both run at once, the first to finish clears the bit, and the close-path drain then frees the instance (and its callback_data) while the other callback is still live - a use-after-free reachable by any user able to open /dev/snd/timer, both via a user timer instance and via a sequencer queue timer bound to the utimer.

snd_timer_interrupt() sets IFLG_CALLBACK before dropping timer->lock, so a concurrent interrupt already observes it under the lock. Skip re-queuing an instance (and its slaves) to the ack/sack list while its callback is in flight; the accumulated pticks are delivered on the next tick, so no event is lost.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-16). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 10, 2026

Last Modified

October 19, 2026

Advisory Details (4)

Auto-updated Aug 14, 2026
Patch available.
Web page

ALSA: timer: don't re-enter an instance callback that is still running - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c1078130a4cd7e738f4b73afe99b3e68cbfbf884
Web page

ALSA: timer: don't re-enter an instance callback that is still running - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/996c24377eea4d4506b7c3ccbbf1e490440b5e0b
Web page

ALSA: timer: don't re-enter an instance callback that is still running - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/70d28bfcd6224eed75986b3b987b997e59643fa4
Web page

ALSA: timer: don't re-enter an instance callback that is still running - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1395327a96614885552bae5fbb650e6dd182d49b

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-570.152.1.el9_62026-10-28redhat
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-10-27ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-27ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-10-27ubuntu
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-aws-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-38.38~24.04.4) @ noble2026-10-27ubuntu
redhatkernel-0:6.12.0-55.113.1.el10_02026-10-23redhat
redhatkernel-0:5.14.0-687.49.1.el9_82026-09-17redhat
redhatkernel-0:6.12.0-211.56.1.el10_22026-09-17redhat
linuxKernel @ 6.12.101 (fixes >=6.12.0)—osv

These rows come from Red Hat, Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.126.12.100-1~deb12u1
  • every version up to 6.12.101-1~deb12u1: fixed in 6.12.101-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)
  • every version up to 6.12.101-1: fixed in 6.12.101-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (162 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 9× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 298 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 198 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 22:26 UTCOSV refresh
  2. 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-11-17 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-11-17 11:59 UTCEchelonGraph re-scored
  8. 2026-11-17 11:59 UTCVendor advisory
  9. 2026-11-17 11:59 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-11-16 16:52 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-11-15 17:02 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-11-14 16:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-11-10 07:07 UTCEchelonGraph re-scored
  18. 2026-11-10 07:07 UTCVendor advisory
  19. 2026-11-10 07:07 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 75 more
  1. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-11-03 12:48 UTCEchelonGraph re-scored
  3. 2026-11-03 12:48 UTCVendor advisory
  4. 2026-11-03 12:48 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-27 18:30 UTCEchelonGraph re-scored
  11. 2026-10-27 18:30 UTCVendor advisory
  12. 2026-10-27 18:30 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  13. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-25 14:10 UTCEchelonGraph re-scored
  17. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-19 21:43 UTCEchelonGraph re-scored
  23. 2026-10-19 21:43 UTCVendor advisory
  24. 2026-10-19 21:43 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-19 21:04 UTCEchelonGraph re-scored
  26. 2026-10-19 21:04 UTCVendor advisory
  27. 2026-10-19 21:03 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  28. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  30. 2026-10-18 03:19 UTCEchelonGraph re-scored
  31. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  32. 2026-10-16 17:34 UTCEchelonGraph re-scored
  33. 2026-10-16 17:34 UTCVendor advisory
  34. 2026-10-16 17:33 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  36. 2026-10-16 16:08 UTCEchelonGraph re-scored
  37. 2026-10-16 16:08 UTCVendor advisory
  38. 2026-10-16 16:07 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  39. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  40. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  42. 2026-10-13 10:14 UTCEchelonGraph re-scored
  43. 2026-10-13 10:14 UTCVendor advisory
  44. 2026-10-13 10:13 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  45. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  46. 2026-10-12 15:45 UTCEchelonGraph re-scored
  47. 2026-10-11 19:30 UTCEchelonGraph re-scored
  48. 2026-10-11 16:45 UTCEchelonGraph re-scored
  49. 2026-10-11 14:06 UTCEchelonGraph re-scored
  50. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  51. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  52. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  53. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  54. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  55. 2026-10-07 05:43 UTCVendor advisory
  56. 2026-10-07 05:43 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-10-06 18:31 UTCEchelonGraph re-scored
  58. 2026-10-06 18:31 UTCVendor advisory
  59. 2026-10-06 18:31 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  61. 2026-10-05 18:59 UTCEchelonGraph re-scored
  62. 2026-10-05 18:59 UTCVendor advisory
  63. 2026-10-05 18:59 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  64. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  65. 2026-10-05 07:51 UTCEchelonGraph re-scored
  66. 2026-10-05 07:51 UTCVendor advisory
  67. 2026-10-05 07:51 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  68. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  69. 2026-10-04 16:44 UTCVendor advisory
  70. 2026-10-04 16:44 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  71. 2026-10-04 05:25 UTCEchelonGraph re-scored
  72. 2026-10-04 05:25 UTCVendor advisory
  73. 2026-10-04 05:25 UTCGHSA enrichmentGHSA-78vp-jqhh-pcc3 · GitHub severity HIGH · GitHub CVSS 7.8
  74. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  75. 2026-10-03 00:55 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-68200?
CVE-2026-68200 is a high-severity vulnerability; its CVE record was published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: timer: don't re-enter an instance callback that is still running The userspace-driven timer (utimer) TRIGGER ioctl calls snd_timer_interrupt() directly with no serialization, so two threads triggering the same utimer can run…
When was the CVE record for CVE-2026-68200 published?
The CVE record for CVE-2026-68200 was published on August 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-68200 actively exploited?
CVE-2026-68200 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68200?
CVE-2026-68200 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68200?
A fix for CVE-2026-68200 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68200 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68200

Explore →

Is Your Infrastructure Affected by CVE-2026-68200?

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