Skip to main content
VulnerabilityPublished Updated

CVE-2026-46004: Linux kernel · ALSA: caiaq: Handle probe errors properly

Affects Linux kernelSource CVE Database V5

0
Compare

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

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

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

Thin evidence

One scorer or none
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-11-06.

Patch
Available – fixed in f537e3ad69609f6924a4db6b4a7f6561f5288bdd, e59ecd4ee3a450db6cb4e4ecaa3efdd593f80056, da938aa9fc7826901921dcea225948ab21a97e45 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 8e3cd08ed8e590952aa9a656758cb24d4ba898f8, < f537e3ad69609f6924a4db6b4a7f6561f5288bdd
Fixed in
  • f537e3ad69609f6924a4db6b4a7f6561f5288bdd
LinuxLinuxAffected
  • ≥ 8e3cd08ed8e590952aa9a656758cb24d4ba898f8, < e59ecd4ee3a450db6cb4e4ecaa3efdd593f80056
Fixed in
  • e59ecd4ee3a450db6cb4e4ecaa3efdd593f80056
LinuxLinuxAffected
  • ≥ 8e3cd08ed8e590952aa9a656758cb24d4ba898f8, < da938aa9fc7826901921dcea225948ab21a97e45
Fixed in
  • da938aa9fc7826901921dcea225948ab21a97e45
LinuxLinuxAffected
  • ≥ 8e3cd08ed8e590952aa9a656758cb24d4ba898f8, < b956e48371f2ff72b76be9a829800ecec963bd45
Fixed in
  • b956e48371f2ff72b76be9a829800ecec963bd45
LinuxLinuxAffected
  • ≥ 8e3cd08ed8e590952aa9a656758cb24d4ba898f8, < 09616e25f502080ba684fc7fcf959d1376ab756d
Fixed in
  • 09616e25f502080ba684fc7fcf959d1376ab756d
LinuxLinuxAffected
  • ≥ 8e3cd08ed8e590952aa9a656758cb24d4ba898f8, < 6251e3e256337a30160ef59ab1580dde4d1acd28
Fixed in
  • 6251e3e256337a30160ef59ab1580dde4d1acd28

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: caiaq: Handle probe errors properly The probe procedure of setup_card() in caiaq driver doesn't treat the error cases gracefully, e.g. the error from snd_card_register() calls snd_card_free() but continues. This would lead to a UAF for the further calls like snd_usb_caiaq_control_init(), as Berk suggested in another patch in the link below. However, the problem is not only that; in general, this function drops the all error handlings (as it's a void function) although its caller can propagate an error to snd_probe(), which eventually calls snd_card_free() as a proper error path. That said, we should treat each error case in setup_card(), and just return the error code promptly, which is then handled later as a fatal error in snd_probe(). This patch achieves it by changing the setup_card() to return an error code. Also, the superfluous snd_card_free() call is removed, too. Note that card->private_free can be set still safely at returning an error. All called functions in card_free() have checks of the unassigned resources or NULL checks.

References

Community reviews

Loading reviews…