Back to CVE records
Not yet scoredPublished Sep 17, 2026

CVE-2026-93185ASoC: rt700-sdw: always drain jack work on remove

Updated under an hour ago ()

Does this affect you?

It affects Linux. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

In the Linux kernel, the following vulnerability has been resolved: ASoC: rt700-sdw: always drain jack work on remove rt700_sdw_remove() drains jack_detect_work and jack_btn_check_work only when rt700->hw_init is true. That state bit is cleared by rt700_update_status() when the SoundWire slave becomes UNATTACHED, but a jack work item can already have been queued by rt700_interrupt_callback() or rt700_jack_init() while the device was initialized. Do not use hw_init as the remove-time guard for draining these work objects. The delayed works are initialized during rt700_init(), so remove can cancel them unconditionally and pair the object lifetime with the codec-private data lifetime instead of a mutable hardware state bit. This issue was found by our static analysis tool and then confirmed by manual review of the SoundWire status, interrupt and remove paths. The remove path should drain work based on whether the work object exists, not on a runtime hardware state bit that can change after the work was queued. A QEMU PoC queued jack_detect_work, simulated SDW_SLAVE_UNATTACHED, and then entered remove. DEBUG_OBJECTS reported an active timer/work object associated with the rt700 jack work path after remove skipped the cancel. This is sent as an RFC because the practical trigger depends on SoundWire core remove ordering after an UNATTACHED status update. If remove cannot run after hw_init has been cleared while jack work is still pending, this is a defensive lifecycle cleanup rather than a reachable race on current systems.

CVSS
Not yet scored
Weakness (CWE)
Not given
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Received
Record last updated
Sep 17, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from 737ee8bdf682cedb3c42b713d20ffa5c899591fb before f1e21b7b977f5ae2955ecf3ab144da2578a4fe00; from 737ee8bdf682cedb3c42b713d20ffa5c899591fb before b81c2131dbb6fe04e27841bc719977c106177c61; 737ee8bdf682cedb3c42b713d20ffa5c899591fb builds before 1bb23c9d68312e77cec81bdfb2cc385e2d2960f7; 737ee8bdf682cedb3c42b713d20ffa5c899591fb builds before 45fcf435ffcc5f61a43bd9b19094dc52de6cbc05; 737ee8bdf682cedb3c42b713d20ffa5c899591fb builds before 1e8fddab6cbe536dd02e61205e4b9bf97df6479b; from 737ee8bdf682cedb3c42b713d20ffa5c899591fb before a47f087877bb2bc57c3ccb714fc49abf45d28e12; 737ee8bdf682cedb3c42b713d20ffa5c899591fb builds before 612ccf42acd14bb2685fa60c3495ca13e63e8989
CNA record

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.