Skip to main content
VulnerabilityPublished Updated

CVE-2026-23076: Linux kernel · Out-of-bounds Read

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in d77ba72558cd66704f0fb7e0969f697e87c0f71c : update Linux kernel when convenient.

Data as of 26 Oct 2026, 11:07 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-06-10.

Patch
Available – fixed in d77ba72558cd66704f0fb7e0969f697e87c0f71c, afca7ff5d5d4d63a1acb95461f55ca9a729feedf, a8c42d11b0526a89192bd2f79facb4c60c8a1f38 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 8cc72361481f00253f1e468ade5795427386d593, < d77ba72558cd66704f0fb7e0969f697e87c0f71c
Fixed in
  • d77ba72558cd66704f0fb7e0969f697e87c0f71c
LinuxLinuxAffected
  • ≥ 8cc72361481f00253f1e468ade5795427386d593, < afca7ff5d5d4d63a1acb95461f55ca9a729feedf
Fixed in
  • afca7ff5d5d4d63a1acb95461f55ca9a729feedf
LinuxLinuxAffected
  • ≥ 8cc72361481f00253f1e468ade5795427386d593, < a8c42d11b0526a89192bd2f79facb4c60c8a1f38
Fixed in
  • a8c42d11b0526a89192bd2f79facb4c60c8a1f38
LinuxLinuxAffected
  • ≥ 8cc72361481f00253f1e468ade5795427386d593, < 6524205326e0c1a21263b5c14e48e14ef7e449ae
Fixed in
  • 6524205326e0c1a21263b5c14e48e14ef7e449ae
LinuxLinuxAffected
  • ≥ 8cc72361481f00253f1e468ade5795427386d593, < 61006c540cbdedea83b05577dc7fb7fa18fe1276
Fixed in
  • 61006c540cbdedea83b05577dc7fb7fa18fe1276
LinuxLinuxAffected
  • ≥ 8cc72361481f00253f1e468ade5795427386d593, < 873e2360d247eeee642878fcc3398babff7e387c
Fixed in
  • 873e2360d247eeee642878fcc3398babff7e387c

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: ctxfi: Fix potential OOB access in audio mixer handling In the audio mixer handling code of ctxfi driver, the conf field is used as a kind of loop index, and it's referred in the index callbacks (amixer_index() and sum_index()). As spotted recently by fuzzers, the current code causes OOB access at those functions. | UBSAN: array-index-out-of-bounds in /build/reproducible-path/linux-6.17.8/sound/pci/ctxfi/ctamixer.c:347:48 | index 8 is out of range for type 'unsigned char [8]' After the analysis, the cause was found to be the lack of the proper (re-)initialization of conj field. This patch addresses those OOB accesses by adding the proper initializations of the loop indices.

References

Community reviews

Loading reviews…