NVD / CVE Program· CNA Linux

CVE-2026-68202: ALSA: seq: close a re-opened queue timer in the destructor

Noroxi assessment

Priority: Monitor (action score 31/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.17% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 24f0cabf173539f048946c8fc221131dc221f277, 2c4dc0ed50b05cd847a4b34b8cebf0775f19aeb9, 31a6163e301d832060f8236f1ed17cbc1ca198df; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 24f0cabf173539f048946c8fc221131dc221f277, 2c4dc0ed50b05cd847a4b34b8cebf0775f19aeb9, 31a6163e301d832060f8236f1ed17cbc1ca198df; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 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: close a re-opened queue timer in the destructor queue_delete() closes the queue timer, then frees it. snd_seq_timer_close() clears q->timer->timeri. snd_use_lock_sync() then drains borrowers, and snd_seq_timer_delete() frees q->timer. A borrower can re-open the timer inside that window. A SET_QUEUE_CLIENT that took a queueptr() use_lock reference before the queue was unlinked runs snd_seq_timer_open() after the close. Open refuses re-open only while timeri is set, and the close just cleared it, so it re-opens timeri. snd_seq_timer_delete() does not close that instance. Its snd_seq_timer_stop() is a no-op, because running was cleared first. So it frees q->timer with the instance still live. The queue is freed next. The instance stays on the global timer with callback_data pointing at the freed queue. A non-owner START on the unlocked queue arms it. The next tick derefs the freed queue in snd_seq_timer_interrupt(). Reachable by an unprivileged user with access to /dev/snd/seq. No CAP and no queue ownership required. Close any lingering instance in the destructor. There, ->timeri can no longer change: the queue is unlinked and all use_lock borrowers have drained, so no snd_seq_queue_use() can re-open it. Close it before clearing q->timer. snd_timer_close() waits for any in-flight snd_seq_timer_interrupt() to finish, and that callback still reads q->timer (via snd_seq_check_queue()), so q->timer must stay valid until it drains.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

Published: Aug 10, 2026
Updated: Oct 19, 2026
EPSS: 0.1% · 7th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Linux: 7.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

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
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b7feeaca1f53b10df9b4de9eaf611767ca70dc92affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 7478ef94b49bc9789cf1a003deec58b42283dde4affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 9d9be6fc30f384f92c4e1b8ed40bd9d4796b7833affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before fb40d03ed792a8a8bf77aa0ee15df57b0ff78b07affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 24f0cabf173539f048946c8fc221131dc221f277affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6a10025c7fd09a7d2af37a3ae1da188569fce470affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 31a6163e301d832060f8236f1ed17cbc1ca198dfaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2c4dc0ed50b05cd847a4b34b8cebf0775f19aeb9affected · git
- before 2.6.12not affected · semver

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
AlmaLinux:10	kernel	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k-core	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k-debug	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k-debug-core	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k-debug-devel	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k-debug-devel-matched	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k-debug-modules	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k-debug-modules-core	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k-debug-modules-extra	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k-devel	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k-devel-matched	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k-modules	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k-modules-core	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-64k-modules-extra	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-abi-stablelists	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-core	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-cross-headers	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-debug	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-debug-core	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-debug-devel	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-debug-devel-matched	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-debug-modules	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2
AlmaLinux:10	kernel-debug-modules-core	before 6.12.0-211.68.1.el10_2	6.12.0-211.68.1.el10_2

+96

Same product

linux: all records

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-68200Aug 10, 2026 · ALSA: timer: don't re-enter an instance callback that is still running
31Monitor
← EarlierCVE-2026-68201Aug 10, 2026 · ALSA: timer: drain a slave's callback before its master detaches it
31Monitor
Later →CVE-2026-68203Aug 10, 2026 · media: vivid: fix cleanup bugs in vivid_init()
0Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
Linux Linux	24f0cabf173539f048946c8fc221131dc221f277	Vendor (CNA)
Linux Linux	2c4dc0ed50b05cd847a4b34b8cebf0775f19aeb9	Vendor (CNA)
Linux Linux	31a6163e301d832060f8236f1ed17cbc1ca198df	Vendor (CNA)
Linux Linux	6a10025c7fd09a7d2af37a3ae1da188569fce470	Vendor (CNA)
Linux Linux	7478ef94b49bc9789cf1a003deec58b42283dde4	Vendor (CNA)
Linux Linux	9d9be6fc30f384f92c4e1b8ed40bd9d4796b7833	Vendor (CNA)
Linux Linux	b7feeaca1f53b10df9b4de9eaf611767ca70dc92	Vendor (CNA)
Linux Linux	fb40d03ed792a8a8bf77aa0ee15df57b0ff78b07	Vendor (CNA)
azl3 kernel 6.6.143.1-1 on Azure Linux 3.0	6.6.150.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
almalinux:bpftool	4.18.0-553.177.1.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel	4.18.0-553.177.1.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt	4.18.0-553.177.1.rt7.518.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-core	4.18.0-553.177.1.rt7.518.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-debug	4.18.0-553.177.1.rt7.518.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-debug-core	4.18.0-553.177.1.rt7.518.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-debug-devel	4.18.0-553.177.1.rt7.518.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-debug-modules	4.18.0-553.177.1.rt7.518.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra	4.18.0-553.177.1.rt7.518.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-devel	4.18.0-553.177.1.rt7.518.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-modules	4.18.0-553.177.1.rt7.518.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:kernel-rt-modules-extra	4.18.0-553.177.1.rt7.518.el8_10 · AlmaLinux:8	Package registry (OSV)
debian:linux	6.1.187-1 · Debian:12	Package registry (OSV)
debian:linux-6.12	6.12.101-1~deb12u1 · Debian:12	Package registry (OSV)
rocky linux:kernel	0:4.18.0-553.177.1.el8_10 · Rocky Linux:8	Package registry (OSV)
rocky linux:kernel-rt	0:4.18.0-553.177.1.rt7.518.el8_10 · Rocky Linux:8	Package registry (OSV)
suse:kernel-default	3.0.101-108.220.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:kernel-docs	3.0.101-108.220.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:kernel-ec2	3.0.101-108.220.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_16	15-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6	Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7_Update_7	13-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7	Package registry (OSV)

+19

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.

Credits

All researchers

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.

CVE-2026-681170 days aparttipc: clear sock->sk on the failed-insert path in tipc_sk_create()
39Monitor
CVE-2026-681270 days apartila: reload IPv6 header after pskb_may_pull in checksum adjust
39Monitor
CVE-2026-681440 days apartphonet: pep: fix use-after-free in pep_get_sb()
39Monitor
CVE-2026-681560 days apartlibceph: refresh auth->authorizer_buf{,_len} after authorizer update
39Monitor
CVE-2026-683810 days apartksmbd: pin conn during async oplock break notification
39Monitor
CVE-2026-684260 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment
39Monitor

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

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

SSVC exploitation— → noneOct 16, 2026, 5:07 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:07 PM UTC

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

References

git.kernel.org/stable/c/24f0cabf173539f048946c8fc221131dc221f277

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records