KernelScan.io

HIGH Introduced in 5.7

asoc VolumeControl OOB

CVE-2026-80526

CVSS 7.8 / 10.0 NVD

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

KernelScan AI7.3HIGH

01

In the Linux kernel, the following vulnerability has been resolved: ASoC: tas2562: Validate values for volume writes tas2562_volume_control_put() does not do any validation of the control value written by userspace, it uses it to look up a value in a fixed size array which can easily be overflowed and then writes whatever value it gets back to the device. Add validation that we are loading a value we have in the array.

02

Engine v0.6.0

Risk summary

A local user with access to the audio device can write an out-of-range volume control value, causing an out-of-bounds array read and writing an arbitrary retrieved value to the TAS2562 codec hardware register. This can cause unintended audio device behavior or a kernel error. The vulnerability requires the TAS2562 codec driver to be loaded and the audio device to be accessible.

Affectedsound/soc/codecs/tas2562.c (ASoC TAS2562 codec driver)

Vulnerability analysis

The volume control handler in the TAS2562 audio codec driver accepts a value from userspace and uses it directly as an index into a fixed-size lookup table without checking bounds. A sufficiently large value causes an out-of-bounds array read, and whatever value is retrieved is then written to the codec's hardware register, potentially causing unintended device behavior or a kernel error. The fix adds a bounds check that rejects out-of-range values before the array lookup. The vulnerable code path is reachable by any local user who can access the audio device and write ALSA mixer controls, which typically requires no special privileges on systems where the audio device node is world-accessible.

03

BranchIntroducedFixed inPatch commit
6.125.76.12.10520bdbb137645
6.185.76.18.46db488d653d89
6.65.76.6.1531f389ecd0c35
7.15.77.1.10c37a0461c0d0
mainline5.77.28fb41964f7e4
cip/6.125.76.12.108-cip3120bdbb137645

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Fixed in 6.12.108-cip31
cip/6.1Affected — no CIP fix yet (latest 6.1.189-cip61)
cip/6.1-rtAffected — no CIP fix yet (latest 6.1.189-cip61-rt32)
cip/5.10Affected — no CIP fix yet (latest 5.10.271-cip78)
cip/5.10-rtAffected — no CIP fix yet (latest 5.10.268-cip77-rt34)