CVE-2026-93185

CVE CVE-2026-93185EUVD EUVD-2026-82293Veröffentlicht 2026-09-17T16:12:11.000Z

Was das Advisory beschreibt

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.

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux 737ee8bdf682cedb3c42b713d20ffa5c899591fb <45fcf435ffcc5f61a43bd9b19094dc52de6cbc05; patch: 6.1.188; 737ee8bdf682cedb3c42b713d20ffa5c899591fb <1e8fddab6cbe536dd02e61205e4b9bf97df6479b; patch: 6.12.110; patch: 7.3-rc1; patch: 6.6.157; 5.12; 737ee8bdf682cedb3c42b713d20ffa5c899591fb <b81c2131dbb6fe04e27841bc719977c106177c61; patch: 7.2.6; patch: 6.18.52; patch: 5.15.221; 737ee8bdf682cedb3c42b713d20ffa5c899591fb <f1e21b7b977f5ae2955ecf3ab144da2578a4fe00; 737ee8bdf682cedb3c42b713d20ffa5c899591fb <a47f087877bb2bc57c3ccb714fc49abf45d28e12; 737ee8bdf682cedb3c42b713d20ffa5c899591fb <1bb23c9d68312e77cec81bdfb2cc385e2d2960f7; patch: 0; 737ee8bdf682cedb3c42b713d20ffa5c899591fb <612ccf42acd14bb2685fa60c3495ca13e63e8989

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.