CVE-2026-74261

UNRATEDCVSS · not yet scored
—
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: seq: avoid stale FIFO cells during resize

snd_seq_fifo_resize() still needs to publish the replacement pool before it waits for FIFO users. A blocking snd_seq_read() holds f->use_lock while it sleeps, so concurrent senders must be able to queue to the new pool and wake that reader instead of failing against a closing old pool.

However, snd_seq_fifo_event_in() duplicates an event before it takes f->lock, and snd_seq_read() can dequeue a cell and later call snd_seq_fifo_cell_putback() if copy_to_user() or snd_seq_expand_var_event() fails. If resize swaps f->pool and detaches oldhead in between, either path can relink an old-pool cell after the snapshot. That stale cell sits outside the drained oldhead list, keeps oldpool->counter elevated, and can leave snd_seq_pool_delete() waiting for the retired pool to drain.

Keep the existing swap-before-wait ordering in snd_seq_fifo_resize(), but reject stale cells before any FIFO relink. Revalidate event-in cells under f->lock and retry them against the published replacement pool, and free stale putback cells instead of linking them back into the FIFO.

The buggy scenario involves two paths, with each column showing the order within that path:

resize path: relink path:

  • Allocate newpool. 1. Take f->use_lock.
  • Swap f->pool to newpool and 2. Duplicate or dequeue an old-pool
detach oldhead. cell before oldpool closes.
  • Mark oldpool closing and 3. Reach a later relink point after
wait for FIFO users. resize published newpool.
  • Free oldhead and delete 4. Relink the old-pool cell after
oldpool. resize detached oldhead.
  • Drop f->use_lock.

The reproducer reports a resize ioctl blocked in the expected pool teardown path:

signal: resize iteration=98 target_pool=4 exceeded 250ms (elapsed=251ms) diagnostic: resize_tid=651 wchan=snd_seq_pool_done diagnostic: resize_tid=651 stack= snd_seq_pool_done+0x5b/0x140 snd_seq_pool_delete+0x7a/0x90 snd_seq_fifo_resize+0x193/0x1e0 snd_seq_ioctl_set_client_pool+0x214/0x260 snd_seq_ioctl+0x119/0x540 __x64_sys_ioctl+0xd1/0x120 do_syscall_64+0xbb/0x2f0 entry_SYSCALL_64_after_hwframe+0x77/0x7f

A second run with larger pools hit the same target path:

signal: resize iteration=32 target_pool=64 exceeded 250ms (elapsed=251ms) diagnostic: resize_tid=663 wchan=snd_seq_pool_done diagnostic: resize_tid=663 stack= snd_seq_pool_done+0x5b/0x140 snd_seq_pool_delete+0x7a/0x90 snd_seq_fifo_resize+0x193/0x1e0 snd_seq_ioctl_set_client_pool+0x214/0x260 snd_seq_ioctl+0x119/0x540 __x64_sys_ioctl+0xd1/0x120 do_syscall_64+0xbb/0x2f0 entry_SYSCALL_64_after_hwframe+0x77/0x7f

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
9th
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. 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 15, 2026

Last Modified

August 17, 2026

Vendor Advisories for CVE-2026-74261(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

Data Freshness Timeline

(refreshed 8× 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 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. 4 repeat rows among the latest 88 are merged into the row they repeat.

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

Frequently asked(4)

What is CVE-2026-74261?
CVE-2026-74261 is a vulnerability whose severity is not yet rated; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: avoid stale FIFO cells during resize sndseqfifo_resize() still needs to publish the replacement pool before it waits for FIFO users. A blocking sndseqread() holds f->use_lock while it sleeps, so concurrent senders must…
When was the CVE record for CVE-2026-74261 published?
The CVE record for CVE-2026-74261 was published on August 15, 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 August 17, 2026; the record at its source may have been updated since.
Is CVE-2026-74261 actively exploited?
CVE-2026-74261 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-74261?
A fix for CVE-2026-74261 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74261 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-74261

Explore →

Is Your Infrastructure Affected by CVE-2026-74261?

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