CVE-2026-74639

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week

Also known asEUVD-2026-64576 (ENISA EUVD) · GHSA-hx28-f548-xhmf (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ALSA: us144mkii: re-anchor capture URBs on resubmission

capture_urb_complete() resubmits each capture URB without anchoring it:

usb_get_urb(urb); ret = usb_submit_urb(urb, GFP_ATOMIC);

Anchoring is a property of a submission, not of the URB. The giveback path calls usb_unanchor_urb() before urb->complete(), so an URB resubmitted from its own completion handler is off the anchor. The capture URBs are anchored once, at stream start, so from the first completion onward tascam->capture_anchor is empty.

tascam_free_urbs(), tascam_disconnect(), tascam_suspend() and the stop-work path all call usb_kill_anchored_urbs(&tascam->capture_anchor) to reap the capture URBs before anything is freed. With the anchor empty those calls return immediately and the URBs stay queued on the host controller.

tascam_free_urbs() then returns the capture transfer buffers with usb_free_coherent(), and snd_card_free() releases the snd_card allocation that embeds tascam (card->private_data). The controller completes the queued URBs afterwards, writing device-supplied data into the freed transfer buffer, and capture_urb_complete() dereferences the freed driver object.

KASAN on 7.2.0-rc5 (arm64):

BUG: KASAN: slab-use-after-free in dummy_timer Write of size 512 at addr ffff000015b62000 __asan_memcpy dummy_timer hrtimer_run_softirq Allocated by task 64: usb_alloc_coherent tascam_alloc_urbs tascam_probe Freed by task 170: usb_free_coherent tascam_free_urbs tascam_disconnect usb_unbind_interface

BUG: KASAN: slab-use-after-free in capture_urb_complete Read of size 4 at addr ffff0000170ee878 Freed by task 170: release_card_device snd_card_free tascam_disconnect

Restore the usb_anchor_urb() between the reference count bump and the resubmission. That also makes the handler's usb_unanchor_urb() failure arm meaningful again and restores usb_kill_anchored_urbs() as a barrier on the disconnect, suspend and stop-work paths.

The anchoring was removed on the premise that the URB is already anchored from the initial submission, which does not hold once the first giveback has run.

Discovered by XBOW, triaged by Baul Lee

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.2%
EPSS %ILE
10th
KEV
Not listed

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

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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
No SSVC decision: EchelonGraph has not assessed this CVECISA 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: the BOD 26-04 block below.

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.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 22, 2026

Last Modified

October 14, 2026

Vendor Advisories for CVE-2026-74639(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.18.45 (fixes >=6.18.39)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (167 versions)
  • every version up to 7.1.9-1: fixed in 7.1.9-1
—

Data Freshness Timeline

(refreshed 9× in last 7d / 40× 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 it from the CNA feed. 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). Most recent first.

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. 2 repeat rows among the latest 89 are merged into the row they repeat.

  1. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-27 12:55 UTCOSV refresh
  6. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-25 14:04 UTCEG score recompute
  9. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-18 03:14 UTCEG score recompute
  17. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-10-14 13:44 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  22. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-12 15:39 UTCEG score recompute
  25. 2026-10-11 19:25 UTCEG score recompute
Show 62 more
  1. 2026-10-11 16:41 UTCEG score recompute
  2. 2026-10-11 14:00 UTCEG score recompute
  3. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-10-10 16:26 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-06 19:45 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  10. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-03 16:36 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  14. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-09-30 07:28 UTCEG score recompute
  17. 2026-09-30 07:28 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  18. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-09-27 01:01 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  22. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  26. 2026-09-23 01:34 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  27. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  28. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-09-19 22:37 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  31. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-09-16 19:40 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  33. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  34. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  35. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  36. 2026-09-13 16:01 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  37. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  38. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  39. 2026-09-10 13:04 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  40. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  41. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  42. 2026-09-07 10:07 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  43. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  44. 2026-09-04 07:11 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  45. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  46. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  47. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  48. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  49. 2026-09-01 04:03 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  50. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  51. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  52. 2026-08-29 00:52 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  53. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  54. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  55. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  56. 2026-08-25 19:23 UTCEG score recompute
  57. 2026-08-25 19:23 UTCGHSA enrichmentGHSA-hx28-f548-xhmf
  58. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  59. 2026-08-24 14:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  60. 2026-08-22 16:24 UTCNVD update
  61. 2026-08-22 15:41 UTCEG score recompute
  62. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-74639?
CVE-2026-74639 is a vulnerability whose severity is not yet rated; its CVE record was published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: us144mkii: re-anchor capture URBs on resubmission captureurbcomplete() resubmits each capture URB without anchoring it: usbgeturb(urb); ret = usbsubmiturb(urb, GFP_ATOMIC); Anchoring is a property of a submission, not of the…
When was the CVE record for CVE-2026-74639 published?
The CVE record for CVE-2026-74639 was published on August 22, 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 14, 2026; the record at its source may have been updated since.
Is CVE-2026-74639 actively exploited?
CVE-2026-74639 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-74639?
A fix for CVE-2026-74639 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74639 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-74639

Explore →

Is Your Infrastructure Affected by CVE-2026-74639?

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