Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 737ee8bdf682cedb3c42b713d20ffa5c899591fb – < f1e21b7b977f5ae2955ecf3ab144da2578a4fe00
    • affected 737ee8bdf682cedb3c42b713d20ffa5c899591fb – < b81c2131dbb6fe04e27841bc719977c106177c61
    • affected 737ee8bdf682cedb3c42b713d20ffa5c899591fb – < 1bb23c9d68312e77cec81bdfb2cc385e2d2960f7
    • affected 737ee8bdf682cedb3c42b713d20ffa5c899591fb – < 45fcf435ffcc5f61a43bd9b19094dc52de6cbc05
    • affected 737ee8bdf682cedb3c42b713d20ffa5c899591fb – < 1e8fddab6cbe536dd02e61205e4b9bf97df6479b
    • affected 737ee8bdf682cedb3c42b713d20ffa5c899591fb – < a47f087877bb2bc57c3ccb714fc49abf45d28e12
    • affected 737ee8bdf682cedb3c42b713d20ffa5c899591fb – < 612ccf42acd14bb2685fa60c3495ca13e63e8989
  • Linux · Linux

    • affected 5.12
    • unaffected < 5.12
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93185 badge
[![CVE-2026-93185](https://cveledger.app/badge/CVE-2026-93185.svg)](https://cveledger.app/cve/CVE-2026-93185)

Record last updated .