Linux Kernel up to 6.19.11 ALSA sound/core/init.c snd_card_set_id off-by-one

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability has been found in Linux Kernel up to 6.19.11 and classified as critical. Affected by this issue is the function snd_card_set_id of the file sound/core/init.c of the component ALSA. The manipulation leads to off-by-one. This vulnerability is listed as CVE-2026-31778. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.19.11. This issue affects the function snd_card_set_id of the file sound/core/init.c of the component ALSA. The manipulation with an unknown input leads to a off-by-one vulnerability. Using CWE to declare the problem leads to CWE-193. A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: ALSA: caiaq: fix stack out-of-bounds read in init_card The loop creates a whitespace-stripped copy of the card shortname where `len id)` is used for the bounds check. Since sizeof(card->id) is 16 and the local id buffer is also 16 bytes, writing 16 non-space characters fills the entire buffer, overwriting the terminating nullbyte. When this non-null-terminated string is later passed to snd_card_set_id() -> copy_valid_id_string(), the function scans forward with `while (*nid && ...)` and reads past the end of the stack buffer, reading the contents of the stack. A USB device with a product name containing many non-ASCII, non-space characters (e.g. multibyte UTF-8) will reliably trigger this as follows: BUG: KASAN: stack-out-of-bounds in copy_valid_id_string sound/core/init.c:696 [inline] BUG: KASAN: stack-out-of-bounds in snd_card_set_id_no_lock+0x698/0x74c sound/core/init.c:718 The off-by-one has been present since commit bafeee5b1f8d ("ALSA: snd_usb_caiaq: give better shortname") from June 2009 (v2.6.31-rc1), which first introduced this whitespace-stripping loop. The original code never accounted for the null terminator when bounding the copy. Fix this by changing the loop bound to `sizeof(card->id) - 1`, ensuring at least one byte remains as the null terminator.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-31778 since 03/09/2026. The exploitation is known to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/21/2026).

The vulnerability scanner Nessus provides a plugin with the ID 321690 (SUSE SLES12 Security Update : kernel (SUSE-SU-2026:2450-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.253, 5.15.203, 6.1.168, 6.6.134, 6.12.81, 6.18.22 or 6.19.12 eliminates this vulnerability. Applying the patch 3f7f8bae0d52cbd07ab04b76b6aac89ef98ee9f6/66194c2575a4f567577ae70b1d7561163ce791a6/a82c1bce2d1299dd3c686a8fe48cf75b79a403c7/3178b62e2e31bab39f63d4c8e54bf4ee0a425627/3afa2e67f3523a980a2f90fd63c22322ac2b9ce0/7594a6464873d90fd229e5b94cdd3b92c9feabed/45424e871abf2a152e247a9cff78359f18dd95c0 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (321690). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Off-by-one
CWE: CWE-193 / CWE-189
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 321690
Nessus Name: SUSE SLES12 Security Update : kernel (SUSE-SU-2026:2450-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.253/5.15.203/6.1.168/6.6.134/6.12.81/6.18.22/6.19.12
Patch: 3f7f8bae0d52cbd07ab04b76b6aac89ef98ee9f6/66194c2575a4f567577ae70b1d7561163ce791a6/a82c1bce2d1299dd3c686a8fe48cf75b79a403c7/3178b62e2e31bab39f63d4c8e54bf4ee0a425627/3afa2e67f3523a980a2f90fd63c22322ac2b9ce0/7594a6464873d90fd229e5b94cdd3b92c9feabed/45424e871abf2a152e247a9cff78359f18dd95c0

Timelineinfo

03/09/2026 CVE reserved
05/01/2026 +52 days Advisory disclosed
05/01/2026 +0 days VulDB entry created
06/21/2026 +51 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-31778 (🔒)
GCVE (CVE): GCVE-0-2026-31778
GCVE (VulDB): GCVE-100-360713

Entryinfo

Created: 05/01/2026 18:08
Updated: 06/21/2026 08:19
Changes: 05/01/2026 18:08 (60), 06/21/2026 08:19 (2)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!