CVE-2026-46048

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ALSA: caiaq: fix usb_dev refcount leak on probe failure

create_card() takes a reference on the USB device with usb_get_dev() and stores the matching usb_put_dev() in card_free(), which is installed as the snd_card's ->private_free destructor.

However, ->private_free is only assigned near the end of init_card(), after several failure points (usb_set_interface(), EP type checks, usb_submit_urb(), the EP1_CMD_GET_DEVICE_INFO exchange, and its timeout). When any of those fail, init_card() returns an error to snd_probe(), which calls snd_card_free(card). Because ->private_free is still NULL, card_free() never runs, the usb_get_dev() reference is not dropped, and the struct usb_device leaks along with its descriptor allocations and device_private.

syzbot reproduces this with a malformed UAC3 device whose only valid altsetting is 0; init_card()'s usb_set_interface(usb_dev, 0, 1) call fails with -EIO and triggers the leak.

Move the ->private_free assignment into create_card(), immediately after usb_get_dev(), so that every error path reaching snd_card_free() balances the reference. card_free()'s callees (snd_usb_caiaq_input_free, free_urbs, kfree) already tolerate the partially-initialized state because the chip private area is zero-initialized by snd_card_new().

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
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: fix usb_dev refcount leak on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: caiaq: fix usb_dev refcount leak on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: caiaq: fix usb_dev refcount leak on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: caiaq: fix usb_dev refcount leak on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7a5f1cd22d47f8ca4b760b6334378ae42c1bd24b
generic

ALSA: caiaq: fix usb_dev refcount leak on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6fa8dff64fb6c401ced40a05797b327659317498
generic

ALSA: caiaq: fix usb_dev refcount leak on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6153878c5255bb69b7d0868105ca078ef13cbcf8
generic

ALSA: caiaq: fix usb_dev refcount leak on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50c6a1f05973f56d23280c9d7645a7a5734e0907
generic

ALSA: caiaq: fix usb_dev refcount leak on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21ca595aafa40d3ac70eab1f4cb62cc00ca21657

Vendor Advisories for CVE-2026-46048(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu

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.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.86-1~bpo12+1 (19 versions)6.12.86-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (131 versions)7.0.4-1

Additional Vendor Advisories

(1)

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 5× in last 7d / 64× 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 203 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46048?
CVE-2026-46048 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: caiaq: fix usb_dev refcount leak on probe failure createcard() takes a reference on the USB device with usbget_dev() and stores the matching usbputdev() in card_free(), which is installed as the sndcard's ->privatefree…
When was CVE-2026-46048 disclosed?
CVE-2026-46048 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-46048 actively exploited?
CVE-2026-46048 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.7% of all scored CVEs.
What is the CVSS score of CVE-2026-46048?
CVE-2026-46048 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46048?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46048, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46048

Explore →

Is Your Infrastructure Affected by CVE-2026-46048?

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