CVE-2025-40269

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].

Gravité et risque d'exploitation

CVE-2025-40269 obtient un score CVSS de 7.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.18 %, ce qui la place devant 6.8 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <ece3b981bb6620e47fac826a2156c090b1a936a0, <282aba56713bbc58155716b55ca7222b2d9cf3c8, 4.19.130, <d2c04f20ccc6c0d219e6d3038bab45bc66a178ad, 0, 5ef30e443e6d3654cccecec99cf481a69a0a6d3b, <5.8, <05a1fc5efdd8560f34a3af39c9cf1e1526cc3ddf, <217d47255a2ec8b246f2725f5db9ac3f1d4109d7, f0bd62b64016508938df9babe47f65c2c727d25c, 4.14.186, 4.9.230, <ef592bf2232a2daa9fffa8881881fc9957ea56e9, <ab0b5e92fc36ee82c1bd01fe896d0f775ed5de41, 5.7.6, <=4.9.*, 6.18, d288dc74f8cf95cb7ae0aaf245b7128627a49bf3, <=4.14.*, 5.10.247, <=5.10.*, <=6.6.*, <4.14.188, 2d50acd7dbd0682a56968ad9551341d7fc5b6eaf, 5.7.8, <5.7.8, 02c56650f3c118d3752122996d96173d26bb13aa, <=5.4.*, <=5.7.*, <=4.19.*, <98e9d5e33bda8db875cc1a4fe99c192658e45ab6, <6a5da3fa80affc948923f20a4e086177f505e86e, <4.19.132, 6.6.117, <480a1490c595a242f27493a4544b3efb21b29f6a, <4.4.230, 5.15.197, <d67dde02049e632ba58d3c44a164a74b6a737154, 6.1.159, 4.4.229, <c4dc012b027c9eb101583011089dea14d744e314, 4.19.132, 6.12.59, 5.4.51, <4.9.230, 4.4.230, <=4.4.*, 99703c921864a318e3e8aae74fde071b1ff35bea, 4.14.188, <=*, <=5.15.*, <=6.17.*, <e0ed5a36fb3ab9e7b9ee45cd17f09f6d5f594360, aba41867dd66939d336fdf604e4d73b805d8039f, 5.8, <5.4.51, 5.4.49, 6.17.9, 4.9.229) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• https://git.kernel.org/stable/c/480a1490c595a242f27493a4544b3efb21b29f6a
• https://git.kernel.org/stable/c/ab0b5e92fc36ee82c1bd01fe896d0f775ed5de41
• https://git.kernel.org/stable/c/282aba56713bbc58155716b55ca7222b2d9cf3c8
• https://git.kernel.org/stable/c/c4dc012b027c9eb101583011089dea14d744e314
• https://git.kernel.org/stable/c/e0ed5a36fb3ab9e7b9ee45cd17f09f6d5f594360
• https://git.kernel.org/stable/c/d67dde02049e632ba58d3c44a164a74b6a737154
• https://git.kernel.org/stable/c/6a5da3fa80affc948923f20a4e086177f505e86e
• https://git.kernel.org/stable/c/217d47255a2ec8b246f2725f5db9ac3f1d4109d7
• https://git.kernel.org/stable/c/ef592bf2232a2daa9fffa8881881fc9957ea56e9
• https://git.kernel.org/stable/c/ece3b981bb6620e47fac826a2156c090b1a936a0
• https://git.kernel.org/stable/c/98e9d5e33bda8db875cc1a4fe99c192658e45ab6
• https://git.kernel.org/stable/c/d2c04f20ccc6c0d219e6d3038bab45bc66a178ad
• https://git.kernel.org/stable/c/05a1fc5efdd8560f34a3af39c9cf1e1526cc3ddf