CVE-2026-64478

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

A fix is available — apply it.

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

ALSA: usb-audio: avoid kobject path lookup in DualSense match

The DualSense jack-detection input handler verifies that a matching input device belongs to the same physical controller by building kobject path strings for both the input device and the USB audio device, then comparing the path prefix.

This was observed when a weak physical connection caused the controller to rapidly disconnect and reconnect. During that repeated hotplug, snd_dualsense_ih_match() can run while the controller's USB device is being disconnected. kobject_get_path() walks ancestor kobjects and dereferences their names; if the USB device kobject name is no longer valid, this can fault in strlen():

RIP: 0010:strlen+0x10/0x30 Call Trace: kobject_get_path+0x34/0x150 snd_dualsense_ih_match+0x49/0xd0 [snd_usb_audio] input_register_device+0x566/0x6a0 ps_probe+0xb89/0x1590 [hid_playstation]

The same ownership check can be done without building kobject path strings. The input device is parented below the HID device, USB interface and USB device, so walking the input device parent chain and comparing against the mixer USB device preserves the check without dereferencing kobject names during disconnect.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

References (8)

Vendor Advisories for CVE-2026-64478(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-13ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-13ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-13ubuntu

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

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1—

Additional Vendor Advisories

(3)

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 6× in last 7d / 44× 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.

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

Frequently asked(4)

What is CVE-2026-64478?
CVE-2026-64478 is a publicly disclosed vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: avoid kobject path lookup in DualSense match The DualSense jack-detection input handler verifies that a matching input device belongs to the same physical controller by building kobject path strings for both the…
When was CVE-2026-64478 disclosed?
CVE-2026-64478 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64478 actively exploited?
CVE-2026-64478 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 91.8% of all scored CVEs.
How do I remediate CVE-2026-64478?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64478, 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-64478

Explore →

Is Your Infrastructure Affected by CVE-2026-64478?

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

Start Free Scan →Browse All CVEs