SECUFOCUSNOW
Home›CVE index›CVE-2022-49292
Review reviewHigh

CVE-2022-49292

Linux Linux, linux kernel

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

CVSS
7.8
EPSS
0.28%
20.0% percentile
CISA KEV
Not listed
Published
2025.02.26
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.28%
Technical severityCVSS 7.8

Vulnerability overview

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

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < a63af1baf0a5e11827db60e3127f87e437cab6e5, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0c4190b41a69990666b4000999e27f8f1b2a426b, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5ce74ff7059341d8b2f4d01c3383491df63d1898, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 7a40cbf3579a8e14849ba7ce46309c1992658d2b, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < fb08bf99195a87c798bc8ae1357337a981faeade, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < e74a069c6a7bb505f3ade141dddf85f4b0b5145a, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < efb6402c3c4a7c26d97c92d70186424097b6e366, >= 2.6.12, < 4.19.237, >= 4.20 < 5.4.188, >= 5.5 < 5.10.109, >= 5.11 < 5.15.32, >= 5.16 < 5.16.18, 5.17
Fixed versions
4.19.237, 5.4.188, 5.10.109, 5.15.32, 5.16.18

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-787