CVE-2022-49292
published 2025-02-26CVE-2022-49292: 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…
PriorityP341high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.28%
20.1th percentile
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
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.17.3-1 (bookworm) | linux 5.17.3-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < a63af1baf0a5e11827db60e3127f87e437cab6e5 | a63af1baf0a5e11827db60e3127f87e437cab6e5 |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0c4190b41a69990666b4000999e27f8f1b2a426b | 0c4190b41a69990666b4000999e27f8f1b2a426b |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5ce74ff7059341d8b2f4d01c3383491df63d1898 | 5ce74ff7059341d8b2f4d01c3383491df63d1898 |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 7a40cbf3579a8e14849ba7ce46309c1992658d2b | 7a40cbf3579a8e14849ba7ce46309c1992658d2b |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < fb08bf99195a87c798bc8ae1357337a981faeade | fb08bf99195a87c798bc8ae1357337a981faeade |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < e74a069c6a7bb505f3ade141dddf85f4b0b5145a | e74a069c6a7bb505f3ade141dddf85f4b0b5145a |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < efb6402c3c4a7c26d97c92d70186424097b6e366 | efb6402c3c4a7c26d97c92d70186424097b6e366 |
| linux | linux_kernel | < 4.19.237 | 4.19.237 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.113-1 | 5.10.113-1 |
| linux | linux_kernel | >= 0 < 5.17.3-1 | 5.17.3-1 |
| linux | linux_kernel | >= 0 < 5.17.3-1 | 5.17.3-1 |
| linux | linux_kernel | >= 0 < 5.17.3-1 | 5.17.3-1 |
| linux | linux_kernel | >= 4.20 < 5.4.188 | 5.4.188 |
| linux | linux_kernel | >= 5.11 < 5.15.32 | 5.15.32 |
| linux | linux_kernel | >= 5.16 < 5.16.18 | 5.16.18 |
| linux | linux_kernel | >= 5.5 < 5.10.109 | 5.10.109 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-vq9m-4624-xg7r: In the Linux kernel, the following vulnerability has been resolved:
ALSA: oss: Fix PCM OSS buffer allocation overflow
We've got syzbot reports hitti
ghsa_unreviewed·2025-09-22
CVE-2022-49292 [HIGH] CWE-787 GHSA-vq9m-4624-xg7r: In the Linux kernel, the following vulnerability has been resolved:
ALSA: oss: Fix PCM OSS buffer allocation overflow
We've got syzbot reports hitti
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
OSV
CVE-2022-49292: In the Linux kernel, the following vulnerability has been resolved: ALSA: oss: Fix PCM OSS buffer allocation overflow We've got syzbot reports hitting
osv·2025-02-26·CVSS 7.8
CVE-2022-49292 [HIGH] CVE-2022-49292: In the Linux kernel, the following vulnerability has been resolved: ALSA: oss: Fix PCM OSS buffer allocation overflow We've got syzbot reports hitting
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
Red Hat
kernel: ALSA: oss: Fix PCM OSS buffer allocation overflow
vendor_redhat·2025-02-26·CVSS 7.8
CVE-2022-49292 [HIGH] CWE-770 kernel: ALSA: oss: Fix PCM OSS buffer allocation overflow
kernel: ALSA: oss: Fix PCM OSS buffer allocation overflow
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
Debian
CVE-2022-49292: linux - In the Linux kernel, the following vulnerability has been resolved: ALSA: oss: ...
vendor_debian·2022·CVSS 7.8
CVE-2022-49292 [HIGH] CVE-2022-49292: linux - In the Linux kernel, the following vulnerability has been resolved: ALSA: oss: ...
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
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0c4190b41a69990666b4000999e27f8f1b2a426bhttps://git.kernel.org/stable/c/5ce74ff7059341d8b2f4d01c3383491df63d1898https://git.kernel.org/stable/c/7a40cbf3579a8e14849ba7ce46309c1992658d2bhttps://git.kernel.org/stable/c/a63af1baf0a5e11827db60e3127f87e437cab6e5https://git.kernel.org/stable/c/e74a069c6a7bb505f3ade141dddf85f4b0b5145ahttps://git.kernel.org/stable/c/efb6402c3c4a7c26d97c92d70186424097b6e366https://git.kernel.org/stable/c/fb08bf99195a87c798bc8ae1357337a981faeade
2025-02-26
Published