CVE-2022-49292

published 26 Feb 2025 · updated 5 Aug 2026

ALSA: oss: Fix PCM OSS buffer allocation overflow

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0c4190b41a69990666b4000999e27f8f1b2a426b, Kernel 5ce74ff7059341d8b2f4d01c3383491df63d1898, Kernel 7a40cbf3579a8e14849ba7ce46309c1992658d2b and 4 more.

In the Linux kernel, the following vulnerability has been resolved: ALSA: oss: Fix PCM OSS buffer allocation overflow We've got syzbot reports hitting INT_MAX overflow at vmalloc() allocation that is called from snd_pcm_plug_alloc(). Although we apply the restrictions to input parameters, it's based only on the hw_params of the underlying PCM device. Since the PCM OSS layer allocates a temporary buffer for the data conversion, the size may become unexpectedly large when more channels or higher rates is given; in the reported case, it went over INT_MAX, hence it hits WARN_ON(). This patch is an attempt to avoid such an overflow and an allocation for too large buffers. First off, it adds the limit of 1MB as the upper bound for period bytes. This must be large enough for all use cases, and we really don't want to handle a larger temporary buffer than this size. The size check is performed at two places, where the original period bytes is calculated and where the plugin buffer size is calculated. In addition, the driver uses array_size() and array3_size() for multiplications to catch overflows for the converted period size and buffer bytes.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.12, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0c4190b41a69990666b4000999e27f8f1b2a426b, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5ce74ff7059341d8b2f4d01c3383491df63d1898, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7a40cbf3579a8e14849ba7ce46309c1992658d2b, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a63af1baf0a5e11827db60e3127f87e437cab6e5, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e74a069c6a7bb505f3ade141dddf85f4b0b5145a, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <efb6402c3c4a7c26d97c92d70186424097b6e366, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fb08bf99195a87c798bc8ae1357337a981faeade0c4190b41a69990666b4000999e27f8f1b2a426b, 5ce74ff7059341d8b2f4d01c3383491df63d1898, 7a40cbf3579a8e14849ba7ce46309c1992658d2b, a63af1baf0a5e11827db60e3127f87e437cab6e5, e74a069c6a7bb505f3ade141dddf85f4b0b5145a, efb6402c3c4a7c26d97c92d70186424097b6e366, fb08bf99195a87c798bc8ae1357337a981faeade

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-49292 severity on Zeptric[![CVE-2022-49292](https://zeptric.io/badge/cve/CVE-2022-49292.svg)](https://zeptric.io/cve/CVE-2022-49292)