Bug 2348302 (CVE-2022-49292) - CVE-2022-49292 kernel: ALSA: oss: Fix PCM OSS buffer allocation overflow
Summary: CVE-2022-49292 kernel: ALSA: oss: Fix PCM OSS buffer allocation overflow
Keywords:
Status: NEW
Alias: CVE-2022-49292
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-26 03:24 UTC by OSIDB Bzimport
Modified: 2025-02-27 14:21 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-02-26 03:24:42 UTC
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.

Comment 3 Avinash Hanwate 2025-02-27 14:12:55 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022633-CVE-2022-49292-b60c@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.