CVE-2025-40269

ALSA: usb-audio: Fix potential overflow of PCM transfer buffer

HIGH
7.8
CVSS Score
Published: December 6, 2025 at 09:50 PM UTC
Updated: October 15, 2026 at 07:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Fix potential overflow of PCM transfer buffer The PCM stream data in USB-audio driver is transferred over USB URB packet buffers, and each packet size is determined dynamically. The packet sizes are limited by some factors such as wMaxPacketSize USB descriptor. OTOH, in the current code, the actually used packet sizes are determined only by the rate and the PPS, which may be bigger than the size limit above. This results in a buffer overflow, as reported by syzbot. Basically when the limit is smaller than the calculated packet size, it implies that something is wrong, most likely a weird USB descriptor. So the best option would be just to return an error at the parameter setup time before doing any further operations. This patch introduces such a sanity check, and returns -EINVAL when the packet size is greater than maxpacksize. The comparison with ep->packsize[1] alone should suffice since it's always equal or greater than ep->packsize[0].

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.14.186 ≤ v < 4.14.1884.19.130 ≤ v < 4.19.1324.4.229 ≤ v < 4.4.2304.9.229 ≤ v < 4.9.2305.4.49 ≤ v < 5.4.515.7.6 ≤ v < 5.7.802c56650f3c118d3752122996d96173d26bb13aa2c56650f3c118d3752122996d96173d26bb13aa2d50acd7dbd0682a56968ad9551341d7fc5b6eaf4.14.1864.19.1304.4.2294.9.2295.4.495.7.65.85ef30e443e6d3654cccecec99cf481a69a0a6d3b99703c921864a318e3e8aae74fde071b1ff35beaaba41867dd66939d336fdf604e4d73b805d8039fd288dc74f8cf95cb7ae0aaf245b7128627a49bf3f0bd62b64016508938df9babe47f65c2c727d25c
Vendor states this is fixed in 05a1fc5efdd8560f34a3af39c9cf1e1526cc3ddf (fixed)
Vendor states this is fixed in 217d47255a2ec8b246f2725f5db9ac3f1d4109d7 (fixed)
Vendor states this is fixed in 282aba56713bbc58155716b55ca7222b2d9cf3c8 (fixed)
Vendor states this is fixed in 480a1490c595a242f27493a4544b3efb21b29f6a (fixed)
Vendor states this is fixed in 6a5da3fa80affc948923f20a4e086177f505e86e (fixed)
Vendor states this is fixed in 98e9d5e33bda8db875cc1a4fe99c192658e45ab6 (fixed)
Vendor states this is fixed in ab0b5e92fc36ee82c1bd01fe896d0f775ed5de41 (fixed)
Vendor states this is fixed in c4dc012b027c9eb101583011089dea14d744e314 (fixed)
Vendor states this is fixed in d2c04f20ccc6c0d219e6d3038bab45bc66a178ad (fixed)
Vendor states this is fixed in d67dde02049e632ba58d3c44a164a74b6a737154 (fixed)
Vendor states this is fixed in e0ed5a36fb3ab9e7b9ee45cd17f09f6d5f594360 (fixed)
Vendor states this is fixed in ece3b981bb6620e47fac826a2156c090b1a936a0 (fixed)
Vendor states this is fixed in ef592bf2232a2daa9fffa8881881fc9957ea56e9 (fixed)
Vendor states this is fixed in 4.14.188 (unaffected)
Vendor states this is fixed in 4.19.132 (unaffected)
Vendor states this is fixed in 4.4.230 (unaffected)
Vendor states this is fixed in 4.9.230 (unaffected)
Vendor states this is fixed in 5.10.247 (unaffected)
Vendor states this is fixed in 5.15.197 (unaffected)
Vendor states this is fixed in 5.4.51 (unaffected)
Vendor states this is fixed in 5.7.8 (unaffected)
Vendor states this is fixed in 5.8 (unaffected)
Vendor states this is fixed in 6.1.159 (unaffected)
Vendor states this is fixed in 6.12.59 (unaffected)
Vendor states this is fixed in 6.17.9 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.117 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card