Home/CVE/In the Linux kernel, the following vulnerability has been resolved: ALSA: caiaq: Handle probe errors properly The prob
CVE

CVE-2026-46004

In the Linux kernel, the following vulnerability has been resolved: ALSA: caiaq: Handle probe errors properly The prob

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.

EPSS 0.00032
Monitor
  • ⚠ NVD has not scored this CVE yet - manual triage required (common for recent CVEs)
Sigma rules0 YARA rules0
Look this up elsewhere - one-click external pivots
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-46004, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
📦

Fixed versions by distribution

21
The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
suse sle15cluster-md-kmp-default fixed in 0:6.4.0-150600.23.115.1
suse sle15dlm-kmp-default fixed in 0:6.4.0-150600.23.115.1
suse sle15gfs2-kmp-default fixed in 0:6.4.0-150600.23.115.1
suse sle15kernel-64kb fixed in 0:6.4.0-150600.23.115.1
suse sle15kernel-default fixed in 0:6.4.0-150600.23.115.1
suse sle15kernel-default-base fixed in 0:6.4.0-150600.23.115.1.150600.12.54.1
suse sle15kernel-default-devel open
suse sle15kernel-default-extra open
suse sle15kernel-default-livepatch open
suse sle15kernel-default-livepatch-devel open
suse sle15kernel-devel open
suse sle15kernel-devel-rt open
suse sle15kernel-docs fixed in 0:6.4.0-150600.23.115.1
suse sle15kernel-macros open
suse sle15kernel-obs-build fixed in 0:6.4.0-150600.23.115.1
suse sle15kernel-source fixed in 0:6.4.0-150600.23.115.1
suse sle15kernel-source-rt open
suse sle15kernel-syms fixed in 0:6.4.0-150600.23.115.1
suse sle15kernel-zfcpdump fixed in 0:6.4.0-150600.23.115.1
suse sle15ocfs2-kmp-default fixed in 0:6.4.0-150600.23.115.1
suse sle15reiserfs-kmp-default fixed in 0:6.4.0-150600.23.115.1

Scoring & Timeline

Published to NVD27 May 2026 · 02:17 PM

Vendor Advisories

3
suse-csafSUSE-SU-2026:2310-1
suse-csafopenSUSE-SU-2026:10954-1
SOC and Response
CVE triage
Stack monitoring
Am I affected
IOC triage
KEV catalog
Daily brief
Change tracking
Detection Engineering
Coverage workspace
Detection coverage
Coverage check
Telemetry ceiling
SIEM query builder
Sigma rules
SIEM rules
YARA rules
Network rules
D3FEND
Threat Hunting
Threat actors
ATT&CK techniques
Attack paths
Indicators
Atomic tests
Red Team and Pentest
Exploitability triage
Recon pack
Attack paths
CAPEC patterns
Adversary emulation
Compliance and GRC
Framework mapping
Control assessment
Audit view
Coverage report
Atlas Search Threat actors Techniques Tools & malware CWE CAPEC KEV catalog Package vulns TAXII feed Data sources
About All capabilities Pricing API docs Live statistics Live status Privacy policy Terms of service
threatengine.sh