CVE-2026-46004

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
2.9%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (8)

Auto-updated Jun 16, 2026
No patch confirmed yet.
generic

ALSA: caiaq: Handle probe errors properly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f537e3ad69609f6924a4db6b4a7f6561f5288bdd
generic

ALSA: caiaq: Handle probe errors properly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e59ecd4ee3a450db6cb4e4ecaa3efdd593f80056
generic

ALSA: caiaq: Handle probe errors properly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/da938aa9fc7826901921dcea225948ab21a97e45
generic

ALSA: caiaq: Handle probe errors properly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b956e48371f2ff72b76be9a829800ecec963bd45
generic

ALSA: caiaq: Handle probe errors properly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6251e3e256337a30160ef59ab1580dde4d1acd28
generic

ALSA: caiaq: Handle probe errors properly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28abd224db4a49560b452115bca3672a20e45b2f
generic

ALSA: caiaq: Handle probe errors properly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/096dd8519cf2f768e9e14f224b627f7aaee1a9c5
generic

ALSA: caiaq: Handle probe errors properly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/09616e25f502080ba684fc7fcf959d1376ab756d

Vendor Advisories for CVE-2026-46004(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 79× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 120 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 23:51 UTCEG score recompute
  7. 2026-07-11 23:51 UTCVendor advisory
  8. 2026-07-11 23:51 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 00:00 UTCEG score recompute
  12. 2026-07-09 00:00 UTCVendor advisory
  13. 2026-07-09 00:00 UTCGHSA enrichment
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 10:49 UTCEG score recompute
  22. 2026-07-01 10:49 UTCVendor advisory
  23. 2026-07-01 10:48 UTCGHSA enrichment
  24. 2026-06-30 03:25 UTCEG score recompute
  25. 2026-06-30 03:25 UTCVendor advisory
Show 75 more
  1. 2026-06-30 03:25 UTCGHSA enrichment
  2. 2026-06-29 14:23 UTCEG score recompute
  3. 2026-06-29 14:23 UTCVendor advisory
  4. 2026-06-29 14:23 UTCGHSA enrichment
  5. 2026-06-29 14:06 UTCEPSS rescore
  6. 2026-06-29 14:06 UTCEPSS rescore
  7. 2026-06-28 21:00 UTCEG score recompute
  8. 2026-06-28 21:00 UTCVendor advisory
  9. 2026-06-28 21:00 UTCGHSA enrichment
  10. 2026-06-28 14:07 UTCEPSS rescore
  11. 2026-06-28 06:44 UTCEG score recompute
  12. 2026-06-28 06:44 UTCVendor advisory
  13. 2026-06-28 06:44 UTCGHSA enrichment
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 18:30 UTCEG score recompute
  17. 2026-06-27 18:30 UTCVendor advisory
  18. 2026-06-27 18:30 UTCGHSA enrichment
  19. 2026-06-27 06:02 UTCEG score recompute
  20. 2026-06-27 06:02 UTCVendor advisory
  21. 2026-06-27 06:02 UTCGHSA enrichment
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-26 17:10 UTCEG score recompute
  24. 2026-06-26 17:10 UTCVendor advisory
  25. 2026-06-26 17:09 UTCGHSA enrichment
  26. 2026-06-26 02:33 UTCEG score recompute
  27. 2026-06-26 02:33 UTCVendor advisory
  28. 2026-06-26 02:33 UTCGHSA enrichment
  29. 2026-06-25 13:49 UTCEPSS rescore
  30. 2026-06-25 13:09 UTCEG score recompute
  31. 2026-06-25 13:09 UTCVendor advisory
  32. 2026-06-25 13:09 UTCGHSA enrichment
  33. 2026-06-25 01:23 UTCEG score recompute
  34. 2026-06-25 01:23 UTCVendor advisory
  35. 2026-06-25 01:23 UTCGHSA enrichment
  36. 2026-06-24 14:05 UTCEPSS rescore
  37. 2026-06-23 21:33 UTCEPSS rescore
  38. 2026-06-23 21:33 UTCEPSS rescore
  39. 2026-06-22 14:25 UTCEPSS rescore
  40. 2026-06-22 14:25 UTCEPSS rescore
  41. 2026-06-21 14:56 UTCEPSS rescore
  42. 2026-06-21 14:56 UTCEPSS rescore
  43. 2026-06-21 01:59 UTCEPSS rescore
  44. 2026-06-21 01:59 UTCEPSS rescore
  45. 2026-06-19 19:26 UTCEPSS rescore
  46. 2026-06-19 19:26 UTCEPSS rescore
  47. 2026-06-18 17:52 UTCEPSS rescore
  48. 2026-06-18 17:52 UTCEPSS rescore
  49. 2026-06-17 21:22 UTCEG score recompute
  50. 2026-06-17 21:22 UTCGHSA enrichment
  51. 2026-06-17 17:53 UTCEPSS rescore
  52. 2026-06-17 09:42 UTCEG score recompute 7.80
  53. 2026-06-17 09:42 UTCGHSA enrichment
  54. 2026-06-16 17:52 UTCEPSS rescore
  55. 2026-06-16 15:47 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
  56. 2026-06-15 17:49 UTCEPSS rescore
  57. 2026-06-14 23:28 UTCMITRE cvelistV5
  58. 2026-06-14 02:35 UTCVendor advisory
  59. 2026-06-14 02:35 UTCGHSA enrichment
  60. 2026-06-13 23:00 UTCEPSS rescore
  61. 2026-06-12 23:12 UTCEPSS rescore
  62. 2026-06-12 23:12 UTCEPSS rescore
  63. 2026-06-11 14:00 UTCEPSS rescore
  64. 2026-06-10 22:18 UTCEPSS rescore
  65. 2026-06-10 20:21 UTCVendor advisory
  66. 2026-06-10 20:21 UTCGHSA enrichment
  67. 2026-06-10 13:22 UTCEPSS rescore
  68. 2026-06-10 13:22 UTCEPSS rescore
  69. 2026-06-08 14:17 UTCEPSS rescore
  70. 2026-06-08 14:17 UTCEPSS rescore
  71. 2026-06-07 15:25 UTCEPSS rescore
  72. 2026-06-07 15:25 UTCEPSS rescore
  73. 2026-06-07 14:06 UTCGHSA enrichment
  74. 2026-06-06 13:47 UTCEPSS rescore
  75. 2026-06-06 13:47 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-46004?
CVE-2026-46004 is a high vulnerability published on May 27, 2026. 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 sndcardregister() calls sndcardfree() but continues. This would lead to a…
When was CVE-2026-46004 disclosed?
CVE-2026-46004 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46004 actively exploited?
CVE-2026-46004 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46004?
CVE-2026-46004 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46004?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46004, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46004

Explore →

Is Your Infrastructure Affected by CVE-2026-46004?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.