CVE-2026-46157
Received Received - Intake
Race Condition in Linux Kernel ALSA PCM OSS Subsystem

Publication date: 2026-05-28

Last updated on: 2026-05-28

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger Currently the runtime.oss.trigger field may be accessed concurrently without protection, which may lead to the data race. And, in this case, it may lead to more severe problem because it's a bit field; as writing the data, it may overwrite other bit fields as well, which confuses the operation completely, as spotted by fuzzing. Fix it by covering runtime.oss.trigger bit fled also with the existing params_lock mutex in both snd_pcm_oss_get_trigger() and snd_pcm_oss_poll().
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-28
Last Modified
2026-05-28
Generated
2026-05-28
AI Q&A
2026-05-28
EPSS Evaluated
N/A
NVD
CVE-2026-46157
EUVD
EUVD-2026-32784
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, update your Linux kernel to a version where the ALSA pcm oss component has been fixed to protect the runtime.oss.trigger field with the existing params_lock mutex. This prevents the data race condition.

Since the issue is a data race in the kernel ALSA subsystem, applying the official patch or upgrading to a kernel version released after 2026-05-28 that includes this fix is the recommended immediate step.


Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's ALSA pcm oss component. It involves a data race condition when accessing the runtime.oss.trigger field. Because this field is a bit field, concurrent access without proper synchronization can cause overwriting of other bits, leading to incorrect operation. The issue was identified through fuzzing and fixed by protecting the runtime.oss.trigger field with an existing mutex lock.


How can this vulnerability impact me? :

The data race in accessing the runtime.oss.trigger bit field can cause unpredictable behavior in the ALSA pcm oss component of the Linux kernel. This may lead to corrupted data or malfunctioning audio operations, potentially causing system instability or unexpected behavior in applications relying on this audio subsystem.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart