Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0eba2a7e858907a746ba69cd002eb9eb4dbd7bf3, 296c8295ae34045da0214882628d49c1c060dd8a, 5.15.180.

Low priority for now. Upgrade to Linux Linux 0eba2a7e858907a746ba69cd002eb9eb4dbd7bf3, 296c8295ae34045da0214882628d49c1c060dd8a, 5.15.180 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 9, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 20th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-37889

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • linux linux kernel6.1.74 and later · before 6.1.132
  • linux linux kernel6.6.7 and later · before 6.6.84
  • linux linux kernel6.7.1 and later · before 6.12.20
  • linux linux kernel5.15.148 and later · before 5.15.180
  • linux linux kernel6.13 and later · before 6.13.8
  • linux linux kernel6.14
  • linux linux kernel6.7

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.7affected
    • c11fc224e58e7972ffd05b8f25e9b1d6a0b8d562 and later · before c402f184a053c8e7ca325e50f04bbbc1e4fee019affected · git
    • a50562146d6c7650029a115c96ef9aaa7648c344 and later · before 694110bc2407a61f02a770cbb5f39b51e4ec77c6affected · git
    • 395e52b7a1ad01e1b51adb09854a0aa5347428de and later · before 544055329560d4b64fe204fc6be325ebc24c72caaffected · git
    • fb9ad24485087e0f00d84bee7a5914640b2b9024 and later · before a46a9371f8b9a0eeff53a21e11ed3b65f52d9cf6affected · git
    • fb9ad24485087e0f00d84bee7a5914640b2b9024 and later · before 296c8295ae34045da0214882628d49c1c060dd8aaffected · git
    • fb9ad24485087e0f00d84bee7a5914640b2b9024 and later · before 0eba2a7e858907a746ba69cd002eb9eb4dbd7bf3affected · git
    • 5.15.148 and later · before 5.15.180affected · semver
    • 6.1.74 and later · before 6.1.132affected · semver
    • 6.6.7 and later · before 6.6.84affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.133-16.1.133-1
Debian:13linuxbefore 6.12.20-16.12.20-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-37887May 9, 2025 · pds_core: handle unsupported PDS_CORE_CMD_FW_CONTROL result
    22Monitor
  • ← EarlierCVE-2025-37888May 9, 2025 · net/mlx5: Fix null-ptr-deref in mlx5_create_{inner_,}ttc_table()
    22Monitor
  • Later →CVE-2025-37842May 9, 2025 · spi: fsl-qspi: use devm function instead of driver remove
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0eba2a7e858907a746ba69cd002eb9eb4dbd7bf3Vendor (CNA)
Linux Linux296c8295ae34045da0214882628d49c1c060dd8aVendor (CNA)
Linux Linux5.15.180Vendor (CNA)
Linux Linux544055329560d4b64fe204fc6be325ebc24c72caVendor (CNA)
Linux Linux6.1.132Vendor (CNA)
Linux Linux6.6.84Vendor (CNA)
Linux Linux694110bc2407a61f02a770cbb5f39b51e4ec77c6Vendor (CNA)
Linux Linuxa46a9371f8b9a0eeff53a21e11ed3b65f52d9cf6Vendor (CNA)
Linux Linuxc402f184a053c8e7ca325e50f04bbbc1e4fee019Vendor (CNA)
debian:linux6.1.133-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records