CVE-2026-64478 — ALSA: usb-audio: avoid kobject path lookup in DualSense match
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 0105cfc41abeb428d4405951a20e1e239bea5e1dversion 6.17≥ 6.16.10 and < 6.17≥ 5.4.300 and < 5.5≥ 6.12.50 and < 6.12.96≥ 6.6.109 and < 6.6.145≥ 6.1.155 and < 6.1.178≥ 5.15.194 and < 5.15.212 and 10 more≥ 5.10.245 and < 5.10.261≥ d0b0264009596c07a77d82808b0dae72bc04ac5c and < e4c66a149c408e44e60bfec3fabf08b6b7abbc60version 104ad9bae11ee450fb7d0595ff7876cfb6527838≥ 79d561c4ec0497669f19a9550cfb74812f60938b and < 7693c0cc415f3a16a7a3355f245474a5e661be4e≥ 79d561c4ec0497669f19a9550cfb74812f60938b and < 4246dd043b7a4f8e3bc1d2896e81d11220610eda≥ 79d561c4ec0497669f19a9550cfb74812f60938b and < a263eb12cbe2e208e6e637df0f9b0be9a484158e≥ a705899ec6085b12a33aa0fd94a58e82e9e90502 and < c1da6d3f45036fa63672ee04ad97cb526b40b987≥ d04d301614630724feb4048bf17432fc7964fe74 and < a47ecd904c51ae6a42957feb3cf2f4266adee2e5≥ c2d5b0a6c688ffb32c35627e337fbbcc65bc275f and < 662a1d7b5affc424ea4f4bc20dd99be29e687886≥ b4b94f092f193d7a2db8e82af5e51519ae89963c and < 4566bf8ae9dbfe81bdc2ff1702d59db8a233b06e |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/4566bf8ae9dbfe81bdc2ff1702d59db8a233b06e
- git.kernel.org/stable/c/c1da6d3f45036fa63672ee04ad97cb526b40b987
- git.kernel.org/stable/c/4246dd043b7a4f8e3bc1d2896e81d11220610eda
- git.kernel.org/stable/c/7693c0cc415f3a16a7a3355f245474a5e661be4e
- git.kernel.org/stable/c/e4c66a149c408e44e60bfec3fabf08b6b7abbc60
- git.kernel.org/stable/c/662a1d7b5affc424ea4f4bc20dd99be29e687886
- git.kernel.org/stable/c/a47ecd904c51ae6a42957feb3cf2f4266adee2e5
- git.kernel.org/stable/c/a263eb12cbe2e208e6e637df0f9b0be9a484158e
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-64478 is "ALSA: usb-audio: avoid kobject path lookup in DualSense match", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.