---
id: CVE-2026-64243
title: |-
  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
summary: |-
  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 …
severity: high
cvss: 7.1
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H'
published: '2026-07-24'
updated: '2026-07-27'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-64243'
references:
  - url: 'https://git.kernel.org/stable/c/05ef77f02607a3dc5d7f9762cb990f76843315d4'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/164dcbec9632ca93ae313e6da6e4e05584fa0f02'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/2ff3ac6f7664fe5639cad01712ac5e021fa7939c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/5fe860af8630cf7c78523cbd68e5a234743585aa'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6fb653b62f169f6050fac45b56bf21ad097e19f6'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d8cc3e747b002a8b965c529de79c0654675b9a1a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f63ad68e18d774a5d15cd7e405ead63f6b322679'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00167
epssPercentile: 0.05203
ingestedAt: '2026-07-27T06:16:49.426Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.