CVE-2026-64478

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

N/A
Published: July 25, 2026 at 08:51 AM UTC
Updated: August 17, 2026 at 05:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.4.300v ≥ 6.16.105.10.245 ≤ v < 5.10.2615.15.194 ≤ v < 5.15.2125.4.300 ≤ v < 5.56.1.155 ≤ v < 6.1.1786.12.50 ≤ v < 6.12.966.16.10 ≤ v < 6.176.17 ≤ v < 6.18.396.17 ≤ v < 7.1.46.17 ≤ v < 7.26.6.109 ≤ v < 6.6.145104ad9bae11ee450fb7d0595ff7876cfb6527838105cfc41abeb428d4405951a20e1e239bea5e1d5.10.2455.15.1945.4.3006.1.1556.12.506.16.106.176.6.10979d561c4ec0497669f19a9550cfb74812f60938ba705899ec6085b12a33aa0fd94a58e82e9e90502b4b94f092f193d7a2db8e82af5e51519ae89963cc2d5b0a6c688ffb32c35627e337fbbcc65bc275fd04d301614630724feb4048bf17432fc7964fe74d0b0264009596c07a77d82808b0dae72bc04ac5c
Vendor states this is fixed in 4246dd043b7a4f8e3bc1d2896e81d11220610eda (fixed)
Vendor states this is fixed in 4566bf8ae9dbfe81bdc2ff1702d59db8a233b06e (fixed)
Vendor states this is fixed in 662a1d7b5affc424ea4f4bc20dd99be29e687886 (fixed)
Vendor states this is fixed in 7693c0cc415f3a16a7a3355f245474a5e661be4e (fixed)
Vendor states this is fixed in a263eb12cbe2e208e6e637df0f9b0be9a484158e (fixed)
Vendor states this is fixed in a47ecd904c51ae6a42957feb3cf2f4266adee2e5 (fixed)
Vendor states this is fixed in c1da6d3f45036fa63672ee04ad97cb526b40b987 (fixed)
Vendor states this is fixed in e4c66a149c408e44e60bfec3fabf08b6b7abbc60 (fixed)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card