Skip to content
Noroxi
CVE-2026-74261· NVD / CVE Program· CNA Linux

ALSA: seq: avoid stale FIFO cells during resize

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 1c4c35fb68d520241f7d9f1c356b5e2370fd8364, 3.11, 3.13.

Low priority for now. Upgrade to Linux Linux 1c4c35fb68d520241f7d9f1c356b5e2370fd8364, 3.11, 3.13 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

—No exploit Fix available
Published
Aug 15, 2026
Updated
Oct 21, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-74261

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • df7a2d0af9f7ab73cf22a7b62bbc0bad93a02110, 28e0ebdd57cd3287ac821068364b74c70af3861c, d4b8e8a32d74052fe292618ae19f794944ddc673, e91325f27c4d98d1088e9e86b3ab475f752eeb80, 9ebfed203c0d93449a074c5c2fd5bb3e58518f0d, 3492352e1f34673708fa7409b4b1d97545aa2f1c, a90d7447e4a154ad26e3b9e09a0878680be49339, 74a2c1ff88a4e0960623d17f7db56ac5a60bb0cf, c36ef6467420f8982e6d4d6f93d0634a85a5ee45, 4.11affected
    • 2d7d54002e396c180db0c800c1046f0a3c471597 and later · before ae429220c7f9747579bc4682c574585230e971ccaffected · git
    • 2d7d54002e396c180db0c800c1046f0a3c471597 and later · before dcf784abee6df2f5c47e36a1d9e400065993bc04affected · git
    • 2d7d54002e396c180db0c800c1046f0a3c471597 and later · before 98a965cb1e767b54b6bbd831b6cea26f521a8f51affected · git
    • 2d7d54002e396c180db0c800c1046f0a3c471597 and later · before 1c4c35fb68d520241f7d9f1c356b5e2370fd8364affected · git
    • 2d7d54002e396c180db0c800c1046f0a3c471597 and later · before e546128291f8d688dcb931827e2efd2aa6c0734daffected · git
    • 3.2.91 and later · before 3.3affected · semver
    • 3.10.107 and later · before 3.11affected · semver
    • 3.12.73 and later · before 3.13affected · semver
    • 3.16.46 and later · before 3.17affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:14linuxbefore 7.1.5-17.1.5-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-74258Aug 15, 2026 · bpf: Guard __get_user acesss with access_ok for uprobe_multi data
    31Monitor
  • ← EarlierCVE-2026-74260Aug 15, 2026 · netfilter: nf_dup_netdev: add nf_dev_xmit_recursion*() helpers and use them
    31Monitor
  • Later →CVE-2026-74262Aug 15, 2026 · kcm: use WRITE_ONCE() when changing lower socket callbacks
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1c4c35fb68d520241f7d9f1c356b5e2370fd8364Vendor (CNA)
Linux Linux3.11Vendor (CNA)
Linux Linux3.13Vendor (CNA)
Linux Linux3.17Vendor (CNA)
Linux Linux3.19Vendor (CNA)
Linux Linux3.3Vendor (CNA)
Linux Linux4.10Vendor (CNA)
Linux Linux4.11Vendor (CNA)
Linux Linux4.2Vendor (CNA)
Linux Linux4.5Vendor (CNA)
Linux Linux98a965cb1e767b54b6bbd831b6cea26f521a8f51Vendor (CNA)
Linux Linuxae429220c7f9747579bc4682c574585230e971ccVendor (CNA)
Linux Linuxdcf784abee6df2f5c47e36a1d9e400065993bc04Vendor (CNA)
Linux Linuxe546128291f8d688dcb931827e2efd2aa6c0734dVendor (CNA)
debian:linux7.1.5-1 · Debian:14Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records