CVE-2026-64243
Medium
Elevated severity or exploit probability.
CVSS base
7.1
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS — probability of exploitation (30 days)
0.1%
1.9th percentile
CISA KEV
Not listed
Weakness / dates
CWE-129
Published 2026-07-24 · modified 2026-08-17
CVSS breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
| Attack Vector | L | Local |
| Attack Complexity | L | Low |
| Privileges Required | L | Low |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | H | High |
| Integrity | N | None |
| Availability | H | High |
Timeline
- 2026-07-24 — Published (NVD)
- 2026-08-17 — Last modified (NVD)
Description
In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: simple-mux: Fix enum control bounds check simple_mux_control_put() rejects values greater than e->items, but enum control values are zero based. For the two-entry mux used by this driver, valid values are 0 and 1, so value 2 must be rejected as well. Accepting e->items can store an invalid mux state, pass it to the GPIO setter, and pass it on to the DAPM mux update path where it is used as an index into the enum text array. Use the same >= e->items check used by the ASoC enum helpers.
Affected
References
- https://git.kernel.org/stable/c/05ef77f02607a3dc5d7f9762cb990f76843315d4
- https://git.kernel.org/stable/c/164dcbec9632ca93ae313e6da6e4e05584fa0f02
- https://git.kernel.org/stable/c/2ff3ac6f7664fe5639cad01712ac5e021fa7939c
- https://git.kernel.org/stable/c/5fe860af8630cf7c78523cbd68e5a234743585aa
- https://git.kernel.org/stable/c/6fb653b62f169f6050fac45b56bf21ad097e19f6
- https://git.kernel.org/stable/c/d8cc3e747b002a8b965c529de79c0654675b9a1a
- https://git.kernel.org/stable/c/f63ad68e18d774a5d15cd7e405ead63f6b322679