CVE-2026-23078: ALSA: scarlett2: Fix buffer overflow in config retrieval
In the Linux kernel, the following vulnerability has been resolved:
ALSA: scarlett2: Fix buffer overflow in config retrieval
The scarlett2_usb_get_config() function has a logic error in the
endianness conversion code that can cause buffer overflows when
count > 1.
The code checks `if (size == 2)` where `size` is the total buffer size in
bytes, then loops `count` times treating each element as u16 (2 bytes).
This causes the loop to access `count * 2` bytes when the buffer only
has `size` bytes allocated.
Fix by checking the element size (config_item->size) instead of the
total buffer size. This ensures the endianness conversion matches the
actual element type.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23078 is a Linux kernel flaw in the ALSA scarlett2 USB audio driver. A logic error can make config retrieval overrun an allocated buffer when multiple 16-bit items are processed. The public record does not provide CVSS severity, impact details, or evidence of exploitation.
Executive priority
Track this as a kernel maintenance issue with uncertain severity. Prioritize normal patch windows unless asset inventory shows broad use of affected kernels with scarlett2 exposure or a vendor advisory raises impact.
Technical view
scarlett2_usb_get_config() checked total buffer size instead of per-item size during endianness conversion. When count is greater than one, the loop can treat multiple elements as u16 and access more bytes than allocated. Kernel stable references show fixes changing the check to config_item->size.
Likely exposure
Exposure appears limited to Linux systems with affected kernels where the ALSA scarlett2 driver is present and relevant hardware or code paths are used. The source bundle lists Linux as affected, but exact downstream distribution status requires vendor kernel advisory verification.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation, public exploit availability, or remote attackability. Treat exploitation status as unconfirmed rather than assumed absent.
Researcher notes
The available record identifies a buffer overflow condition but lacks CVSS, CWE, attack vector, privilege requirement, and exploitability details. Analysis should focus on affected stable branches, downstream backports, and whether the vulnerable config retrieval path is reachable in deployed environments.
Mitigation direction
Update to a vendor kernel containing one of the referenced stable fixes.
Check Linux distribution advisories for backported fixes and package names.
Prioritize systems using USB audio workflows involving the scarlett2 driver.
If patching is delayed, review vendor guidance for driver-specific risk reduction.
Validation and detection
Inventory running kernel versions across Linux assets.
Check whether the ALSA scarlett2 driver is built, loaded, or packaged.
Map installed kernels against distribution advisories and referenced stable commits.
Confirm patched systems boot the updated kernel, not only install it.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23078 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
7Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 4, 2026, 16:08 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.