Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-46004: ALSA: caiaq: Handle probe errors properly

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 09616e25f502080ba684fc7fcf959d1376ab756d, 096dd8519cf2f768e9e14f224b627f7aaee1a9c5, 28abd224db4a49560b452115bca3672a20e45b2f; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 09616e25f502080ba684fc7fcf959d1376ab756d, 096dd8519cf2f768e9e14f224b627f7aaee1a9c5, 28abd224db4a49560b452115bca3672a20e45b2f; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 27, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-46004

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.25 and later · before 5.10.258
  • linux linux kernel5.11 and later · before 5.15.209
  • linux linux kernel5.16 and later · before 6.1.175
  • linux linux kernel6.2 and later · before 6.6.140
  • linux linux kernel6.7 and later · before 6.12.86
  • linux linux kernel6.13 and later · before 6.18.27
  • linux linux kernel6.19 and later · before 7.0.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.25affected
    • 8e3cd08ed8e590952aa9a656758cb24d4ba898f8 and later · before da938aa9fc7826901921dcea225948ab21a97e45affected · git
    • 8e3cd08ed8e590952aa9a656758cb24d4ba898f8 and later · before 09616e25f502080ba684fc7fcf959d1376ab756daffected · git
    • 8e3cd08ed8e590952aa9a656758cb24d4ba898f8 and later · before b956e48371f2ff72b76be9a829800ecec963bd45affected · git
    • 8e3cd08ed8e590952aa9a656758cb24d4ba898f8 and later · before f537e3ad69609f6924a4db6b4a7f6561f5288bddaffected · git
    • 8e3cd08ed8e590952aa9a656758cb24d4ba898f8 and later · before 6251e3e256337a30160ef59ab1580dde4d1acd28affected · git
    • 8e3cd08ed8e590952aa9a656758cb24d4ba898f8 and later · before e59ecd4ee3a450db6cb4e4ecaa3efdd593f80056affected · git
    • 8e3cd08ed8e590952aa9a656758cb24d4ba898f8 and later · before 096dd8519cf2f768e9e14f224b627f7aaee1a9c5affected · git
    • 8e3cd08ed8e590952aa9a656758cb24d4ba898f8 and later · before 28abd224db4a49560b452115bca3672a20e45b2faffected · git
    • before 2.6.25not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.176-16.1.176-1
Debian:13linuxbefore 6.12.86-16.12.86-1
Debian:14linuxbefore 7.0.4-17.0.4-1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-defaultbefore 6.4.0-150600.23.115.16.4.0-150600.23.115.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_27before 1-150600.13.3.11-150600.13.3.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-64kbbefore 6.4.0-150600.23.115.16.4.0-150600.23.115.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-default-basebefore 6.4.0-150600.23.115.1.150600.12.54.16.4.0-150600.23.115.1.150600.12.54.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-docsbefore 6.4.0-150600.23.115.16.4.0-150600.23.115.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-obs-buildbefore 6.4.0-150600.23.115.16.4.0-150600.23.115.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-sourcebefore 6.4.0-150600.23.115.16.4.0-150600.23.115.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-symsbefore 6.4.0-150600.23.115.16.4.0-150600.23.115.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-zfcpdumpbefore 6.4.0-150600.23.115.16.4.0-150600.23.115.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-46001May 27, 2026 · hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data()
    31Monitor
  • ← EarlierCVE-2026-46002May 27, 2026 · ext2: reject inodes with zero i_nlink and valid mode in ext2_iget()
    22Monitor
  • Later →CVE-2026-46005May 27, 2026 · xfs: fix a resource leak in xfs_alloc_buftarg()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux09616e25f502080ba684fc7fcf959d1376ab756dVendor (CNA)
Linux Linux096dd8519cf2f768e9e14f224b627f7aaee1a9c5Vendor (CNA)
Linux Linux28abd224db4a49560b452115bca3672a20e45b2fVendor (CNA)
Linux Linux6251e3e256337a30160ef59ab1580dde4d1acd28Vendor (CNA)
Linux Linuxb956e48371f2ff72b76be9a829800ecec963bd45Vendor (CNA)
Linux Linuxda938aa9fc7826901921dcea225948ab21a97e45Vendor (CNA)
Linux Linuxe59ecd4ee3a450db6cb4e4ecaa3efdd593f80056Vendor (CNA)
Linux Linuxf537e3ad69609f6924a4db6b4a7f6561f5288bddVendor (CNA)
azl3 kernel 6.6.139.1-1 on Azure Linux 3.06.6.141.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)
suse:kernel-64kb6.4.0-150600.23.115.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:kernel-default6.4.0-150600.23.115.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-default-base6.4.0-150600.23.115.1.150600.12.54.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:kernel-docs6.4.0-150600.23.115.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_271-150600.13.3.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-obs-build6.4.0-150600.23.115.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:kernel-source6.4.0-150600.23.115.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:kernel-syms6.4.0-150600.23.115.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:kernel-zfcpdump6.4.0-150600.23.115.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records