Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-31778ALSA: caiaq: fix stack out-of-bounds read in init_card

Description

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 < sizeof(card->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.

Timeline

  1. ID reserved

    By Linux

  2. · 53 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31778, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected bafeee5b1f8d32cbf791c322b40a6fa91d8ccf7a – < 02d9c5b0b5553a391448b6d655262bd829f90234
    • affected bafeee5b1f8d32cbf791c322b40a6fa91d8ccf7a – < 3f7f8bae0d52cbd07ab04b76b6aac89ef98ee9f6
    • affected bafeee5b1f8d32cbf791c322b40a6fa91d8ccf7a – < 66194c2575a4f567577ae70b1d7561163ce791a6
    • affected bafeee5b1f8d32cbf791c322b40a6fa91d8ccf7a – < a82c1bce2d1299dd3c686a8fe48cf75b79a403c7
    • affected bafeee5b1f8d32cbf791c322b40a6fa91d8ccf7a – < 3178b62e2e31bab39f63d4c8e54bf4ee0a425627
    • affected bafeee5b1f8d32cbf791c322b40a6fa91d8ccf7a – < 3afa2e67f3523a980a2f90fd63c22322ac2b9ce0
    • affected bafeee5b1f8d32cbf791c322b40a6fa91d8ccf7a – < 7594a6464873d90fd229e5b94cdd3b92c9feabed
    • affected bafeee5b1f8d32cbf791c322b40a6fa91d8ccf7a – < 45424e871abf2a152e247a9cff78359f18dd95c0
  • Linux · Linux

    • affected 2.6.31
    • unaffected < 2.6.31
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.134 – ≤ 6.6.*
    • unaffected 6.12.81 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31778 badge
[![CVE-2026-31778](https://cveledger.app/badge/CVE-2026-31778.svg)](https://cveledger.app/cve/CVE-2026-31778)

Record last updated .