Review reviewHigh

CVE-2022-48702

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: ALSA: emu10k1: Fix out of bounds access in snd_emu10k1_pcm_channel_alloc() The voice allocator sometimes begins allocating from near the end of the array and then wraps around, however snd_emu10k1_pcm_channel_alloc() accesses the newly allocated voices as if it never wrapped around. This results in out of bounds access if the first voice has a high enough index so that first_voice + requested_voice_count > NUM_G (64). The more voices are requested, the more likely it is for this to occur. This was initially discovered using...

CVSS
7.8
EPSS
0.24%
14.8% percentile
CISA KEV
Not listed
Published
2024.05.04
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: ALSA: emu10k1: Fix out of bounds access in snd_emu10k1_pcm_channel_alloc() The voice allocator sometimes begins allocating from near the end of the array and then wraps around, however snd_emu10k1_pcm_channel_alloc() accesses the newly allocated voices as if it never wrapped around. This results in out of bounds access if the first voice has a high enough index so that first_voice + requested_voice_count > NUM_G (64). The more voices are requested, the more likely it is for this to occur. This was initially discovered using...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 637c5310acb48fffcc5657568db3f3e9bc719bfa, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6b0e260ac3cf289e38446552461caa65e6dab275, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 88aac6684cf8bc885cca15463cb4407e91f28ff7, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 45321a7d02b7cf9b3f97e3987fc1e4d649b82da2, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 39a90720f3abe96625d1224e7a7463410875de4c, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 45814a53514e10a8014906c882e0d0d38df39cc1, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 4204a01ffce97cae1d59edc5848f02be5b2b9178, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d29f59051d3a07b81281b2df2b8c9dfe4716067f, >= 2.6.12, < 4.9.328, >= 4.10 < 4.14.293, >= 4.15 < 4.19.258, >= 4.20 < 5.4.213, >= 5.5 < 5.10.143, >= 5.11 < 5.15.68, >= 5.17 < 5.19.9, 6.0
Fixed versions
4.9.328, 4.14.293, 4.19.258, 5.4.213, 5.10.143, 5.15.68, 5.19.9

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