Is there a patch available for EUVD-2026-93299?

Yes, a patch is available for EUVD-2026-93299. Update the affected software to the latest version immediately.

Linux EUVD-2026-93299

| CVE-2026-98314

2026-10-06 Linux

GHSA-f958-2rwj-98rc

Information Disclosure Linux

View

Monitor Track and reassess. Why: No CVSS yet + weak signal (CWE or non-zero EPSS).

Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

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.

Affected VersionsENISA

Linux patch: 6.12.112

Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d63f5a9f8121fb43c798056d7dd34c58f47185d7

Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <27f167e117eca310661fbcbacb352ea08face067

Linux patch: 5.10.271

Linux patch: 7.3-rc4

Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e1eee8f16628f8b6bcae0a366fd6a2dd65e71edd

Linux patch: 6.18.54

Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1e713f9bb2ac583521f06b0eb4e22440b1e3d078

Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <555d168bd98daa46daccc68c908201388c834293

Linux patch: 5.15.222

Linux patch: 7.2.8

Linux patch: 6.6.158

Linux 2.6.12

Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <686c7a6af1eea8d2a919303e4c6bbec3de79dbdc

Linux patch: 0

Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0b349249d572633d7c8cdeb917623d1676a2b7c3

Linux patch: 6.1.189

Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8c869d5cf5affb20994bdbb60e7d46d65c91b55f

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Lifecycle Timeline

Patch available

Oct 06, 2026 - 10:02 EUVD

CVE Published

Oct 06, 2026 - 08:46 cve.org

UNKNOWN (no severity yet)

Threat Intelligence Overview

EPSS Score

0.2%

Top 93% exploitable

Data Quality

3 sources

Confidence: Low

EUVD

CVE.org

EPSS MSRC

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity Not scored yet

CISA KEV No

Public POC No

EPSS 0.2%

Patch available Yes

Active threat No

Deciding rule

No CVSS yet + weak signal (CWE or non-zero EPSS)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.