diff options
author | Takashi Iwai <tiwai@suse.de> | 2022-03-18 09:20:36 +0100 |
---|---|---|
committer | Takashi Iwai <tiwai@suse.de> | 2022-03-18 14:01:07 +0100 |
commit | efb6402c3c4a7c26d97c92d70186424097b6e366 (patch) | |
tree | 7d4b3af91ceb693f40fa6ad77998eae61d9b1e1a /sound/soc/sh | |
parent | c14231cc04337c2c2a937db084af342ce704dbde (diff) | |
download | linux-efb6402c3c4a7c26d97c92d70186424097b6e366.tar.bz2 |
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.
Reported-by: syzbot+72732c532ac1454eeee9@syzkaller.appspotmail.com
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <stable@vger.kernel.org>
Link: https://lore.kernel.org/r/00000000000085b1b305da5a66f3@google.com
Link: https://lore.kernel.org/r/20220318082036.29699-1-tiwai@suse.de
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'sound/soc/sh')
0 files changed, 0 insertions, 0 deletions