CVE-2025-37889: PCI/MSI: Handle the NOMASK flag correctly for all PCI/MSI backends
First published: Fri May 09 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: ASoC: ops: Consistently treat platform_max as control value This reverts commit 9bdd10d57a88 ("ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min"), and makes some additional related updates. There are two ways the platform_max could be interpreted; the maximum register value, or the maximum value the control can be set to. The patch moved from treating the value as a control value to a register one. When the patch was applied it was technically correct as snd_soc_limit_volume() also used the register interpretation. However, even then most of the other usages treated platform_max as a control value, and snd_soc_limit_volume() has since been updated to also do so in commit fb9ad24485087 ("ASoC: ops: add correct range check for limiting volume"). That patch however, missed updating snd_soc_put_volsw() back to the control interpretation, and fixing snd_soc_info_volsw_range(). The control interpretation makes more sense as limiting is typically done from the machine driver, so it is appropriate to use the customer facing representation rather than the internal codec representation. Update all the code to consistently use this interpretation of platform_max. Finally, also add some comments to the soc_mixer_control struct to hopefully avoid further patches switching between the two approaches.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/46d357520934eef99fa121889f8ebbf46a6eddb8
- https://git.kernel.org/stable/c/2e3ad60b8f72a95e3a32ddd9d70ea129aa3fcfb7
- https://git.kernel.org/stable/c/3ece3e8e5976c49c3f887e5923f998eabd54ff40
- https://git.kernel.org/stable/c/0eba2a7e858907a746ba69cd002eb9eb4dbd7bf3
- https://git.kernel.org/stable/c/296c8295ae34045da0214882628d49c1c060dd8a
- https://git.kernel.org/stable/c/544055329560d4b64fe204fc6be325ebc24c72ca
- https://git.kernel.org/stable/c/694110bc2407a61f02a770cbb5f39b51e4ec77c6
- https://git.kernel.org/stable/c/a46a9371f8b9a0eeff53a21e11ed3b65f52d9cf6
- https://git.kernel.org/stable/c/c402f184a053c8e7ca325e50f04bbbc1e4fee019
Frequently Asked Questions
What is the severity of CVE-2025-37889?
The severity of CVE-2025-37889 is categorized as moderate due to potential impacts on system stability.
How do I fix CVE-2025-37889?
To fix CVE-2025-37889, update the Linux Kernel to the latest version that includes the patch addressing this vulnerability.
Who is affected by CVE-2025-37889?
All users running vulnerable versions of the Linux Kernel that utilize PCI/MSI are potentially affected by CVE-2025-37889.
What are the potential impacts of CVE-2025-37889?
The potential impacts of CVE-2025-37889 include issues related to the integrity of device interrupts, which can lead to system instability.
When was CVE-2025-37889 disclosed?
CVE-2025-37889 was disclosed in the year 2025, highlighting a vulnerability in the handling of the NOMASK flag in the Linux Kernel.
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/type
- agent/weakness
- agent/first-publish-date
- agent/author
- agent/source
- agent/event
- collector/nvd-api
- source/NVD
- agent/references
- agent/last-modified-date
- agent/description
- agent/tags
- agent/softwarecombine
- agent/guess-ai
- agent/software-canonical-lookup
- vendor/linux
- canonical/linux kernel