dbcve.org
Linux KernelOperating system · Linux

CVE-2026-46146

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 5.5 / 5.10.258 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Avoid potential endless loop in convert_chmap_v3() The convert_chmap_v3() has a loop with its increment size of cs_desc->wLength, but we forgot to validate cs_desc->wLength itself, which may lead to potential endless loop by a malformed descriptor. Add a proper size check to abort the loop for plugging the hole.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-835

Crafted input drives a loop whose exit condition is never satisfied, hanging the thread and starving the service of the resource it occupies. A single request can be enough to take a worker down. Remediation is bounding iteration counts and validating the conditions that are supposed to terminate the loop.

General guidance for the infinite loop class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.4.297, < 5.5>= 5.10.241, < 5.10.258>= 5.15.190, < 5.15.209>= 6.1.149, < 6.1.175>= 6.6.103, < 6.6.140>= 6.12.43, < 6.12.88>= 6.15.11, < 6.16>= 6.16.2, < 6.17>= 6.17.1, < 6.18.30>= 6.19, < 7.0.7= 6.17= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.5 / 5.10.258 / 5.15.209 or later
Fixed in 5.55.10.2585.15.209
Vendor patch git.kernel.org →
Recommended fix High confidence

5.5, 5.10.258, 5.15.209, or 6.1.175 (depending on your kernel branch)

  1. 1. Identify the currently running Linux kernel version using `uname -r`
  2. 2. Determine which kernel branch you are on (e.g., 5.4, 5.10, 6.1, 6.6, etc.)
  3. 3. Upgrade to the first fixed release for your branch: For 5.4.x, upgrade to 5.5 or later; For 5.10.x, upgrade to 5.10.258 or later; For 5.15.x, upgrade to 5.15.209 or later; For 6.1.x, upgrade to 6.1.175 or later; For 6.6.x and later, the vulnerability is already fixed in stable releases
  4. 4. On Debian/Ubuntu: `sudo apt-get update && sudo apt-get dist-upgrade` followed by reboot
  5. 5. On RHEL/CentOS: `sudo yum update kernel` followed by reboot
  6. 6. On Fedora: `sudo dnf update kernel` followed by reboot
  7. 7. Verify the fix is applied by checking the convert_chmap_v3 function in sound/usb/chmap.c contains the wLength validation check after reboot
Caveat Kernel upgrades may require rebooting and could introduce compatibility changes with third-party kernel modules

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46146 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46146 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data