Unknown

CVE-2026-98314 — ALSA: pcm: set timer->private_data before registering the PCM timer

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: set timer->private_data before registering the PCM timer snd_pcm_timer_init() calls snd_device_register() to link the new struct snd_timer into the global timer list while it still carries hw.c_resolution = snd_pcm_timer_resolution (and hw.start/hw.stop), and only afterwards sets timer->private_data = substream. Once the timer is on the list under register_mutex, a concurrent reader can already reach it through the same mutex and invoke these callbacks. /proc/asound/timers does this via c_resolution(), and snd_timer_open()+snd_timer_start() reach start()/stop() the same way. All three dereference timer->private_data, which for this brief window is NULL, giving a NULL-pointer dereference: substream = timer->private_data; return substream->runtime ? ... // substream is NULL Move the private_data/private_free assignment before snd_device_register() so the timer is never visible on the list without its private_data set. On the snd_device_register() failure path, private_free() (snd_pcm_timer_free()) can now run, but it only does substream->timer = NULL, which is already NULL at that point since substream->timer is set to the new timer just once, after a successful registration -- so the failure path stays safe.

Published Oct 6, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.18%

ahead of 7% of scored CVEs · Oct 14, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 27f167e117eca310661fbcbacb352ea08face067≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 555d168bd98daa46daccc68c908201388c834293≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 8c869d5cf5affb20994bdbb60e7d46d65c91b55f≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 686c7a6af1eea8d2a919303e4c6bbec3de79dbdc≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < e1eee8f16628f8b6bcae0a366fd6a2dd65e71edd≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < d63f5a9f8121fb43c798056d7dd34c58f47185d7≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 0b349249d572633d7c8cdeb917623d1676a2b7c3≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 1e713f9bb2ac583521f06b0eb4e22440b1e3d078 and 1 more version 2.6.12	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.18%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 13, 2026
Affected products added · linux/linux
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Oct 6, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

8 on the record

git.kernel.org/stable/c/686c7a6af1eea8d2a919303e4c6bbec3de79dbdc
NIST National Vulnerability Database
git.kernel.org/stable/c/27f167e117eca310661fbcbacb352ea08face067
NIST National Vulnerability Database
git.kernel.org/stable/c/1e713f9bb2ac583521f06b0eb4e22440b1e3d078
NIST National Vulnerability Database
git.kernel.org/stable/c/d63f5a9f8121fb43c798056d7dd34c58f47185d7
NIST National Vulnerability Database
git.kernel.org/stable/c/e1eee8f16628f8b6bcae0a366fd6a2dd65e71edd
NIST National Vulnerability Database
git.kernel.org/stable/c/8c869d5cf5affb20994bdbb60e7d46d65c91b55f
NIST National Vulnerability Database
git.kernel.org/stable/c/0b349249d572633d7c8cdeb917623d1676a2b7c3
NIST National Vulnerability Database
git.kernel.org/stable/c/555d168bd98daa46daccc68c908201388c834293
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 8h
Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 8h
Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-98314 is "ALSA: pcm: set timer->private_data before registering the PCM timer", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.