Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-37889ASoC: ops: Consistently treat platform_max as control value

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 18 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-37889, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.31% · top 76% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected c11fc224e58e7972ffd05b8f25e9b1d6a0b8d562 – < c402f184a053c8e7ca325e50f04bbbc1e4fee019
    • affected a50562146d6c7650029a115c96ef9aaa7648c344 – < 694110bc2407a61f02a770cbb5f39b51e4ec77c6
    • affected 395e52b7a1ad01e1b51adb09854a0aa5347428de – < 544055329560d4b64fe204fc6be325ebc24c72ca
    • affected fb9ad24485087e0f00d84bee7a5914640b2b9024 – < a46a9371f8b9a0eeff53a21e11ed3b65f52d9cf6
    • affected fb9ad24485087e0f00d84bee7a5914640b2b9024 – < 296c8295ae34045da0214882628d49c1c060dd8a
    • affected fb9ad24485087e0f00d84bee7a5914640b2b9024 – < 0eba2a7e858907a746ba69cd002eb9eb4dbd7bf3
    • affected 5.15.148 – < 5.15.180
    • affected 6.1.74 – < 6.1.132
    • affected 6.6.7 – < 6.6.84

  • Linux · Linux

    • affected 6.7
    • unaffected < 6.7
    • unaffected 5.15.180 – ≤ 5.15.*
    • unaffected 6.1.132 – ≤ 6.1.*
    • unaffected 6.6.84 – ≤ 6.6.*
    • unaffected 6.12.20 – ≤ 6.12.*
    • unaffected 6.13.8 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-37889 badge
[![CVE-2025-37889](https://cveledger.app/badge/CVE-2025-37889.svg)](https://cveledger.app/cve/CVE-2025-37889)

Record last updated .