cveboard RSS feed

CVE-2022-49292

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2022
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

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

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2affectedgita63af1baf0a5e11827db60e3127f87e437cab6e5UnavailableNone listed
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2affectedgit0c4190b41a69990666b4000999e27f8f1b2a426bUnavailableNone listed
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2affectedgit5ce74ff7059341d8b2f4d01c3383491df63d1898UnavailableNone listed
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2affectedgit7a40cbf3579a8e14849ba7ce46309c1992658d2bUnavailableNone listed
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2affectedgitfb08bf99195a87c798bc8ae1357337a981faeadeUnavailableNone listed
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2affectedgite74a069c6a7bb505f3ade141dddf85f4b0b5145aUnavailableNone listed
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2affectedgitefb6402c3c4a7c26d97c92d70186424097b6e366UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
2.6.12affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver2.6.12UnavailableNone listed
4.19.237unaffectedsemverUnavailable4.19.*None listed
5.4.188unaffectedsemverUnavailable5.4.*None listed
5.10.109unaffectedsemverUnavailable5.10.*None listed
5.15.32unaffectedsemverUnavailable5.15.*None listed
5.16.18unaffectedsemverUnavailable5.16.*None listed
5.17.1unaffectedsemverUnavailable5.17.*None listed
5.18unaffectedoriginal_commit_for_fixUnavailable*None listed