Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 1bb23c9d68312e77cec81bdfb2cc385e2d2960f7, 1e8fddab6cbe536dd02e61205e4b9bf97df6479b, 45fcf435ffcc5f61a43bd9b19094dc52de6cbc05; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.

Low priority for now. Upgrade to Linux Linux 1bb23c9d68312e77cec81bdfb2cc385e2d2960f7, 1e8fddab6cbe536dd02e61205e4b9bf97df6479b, 45fcf435ffcc5f61a43bd9b19094dc52de6cbc05; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 17, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-93185

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.12affected
    • 737ee8bdf682cedb3c42b713d20ffa5c899591fb and later · before f1e21b7b977f5ae2955ecf3ab144da2578a4fe00affected · git
    • 737ee8bdf682cedb3c42b713d20ffa5c899591fb and later · before b81c2131dbb6fe04e27841bc719977c106177c61affected · git
    • 737ee8bdf682cedb3c42b713d20ffa5c899591fb and later · before 1bb23c9d68312e77cec81bdfb2cc385e2d2960f7affected · git
    • 737ee8bdf682cedb3c42b713d20ffa5c899591fb and later · before 45fcf435ffcc5f61a43bd9b19094dc52de6cbc05affected · git
    • 737ee8bdf682cedb3c42b713d20ffa5c899591fb and later · before 1e8fddab6cbe536dd02e61205e4b9bf97df6479baffected · git
    • 737ee8bdf682cedb3c42b713d20ffa5c899591fb and later · before a47f087877bb2bc57c3ccb714fc49abf45d28e12affected · git
    • 737ee8bdf682cedb3c42b713d20ffa5c899591fb and later · before 612ccf42acd14bb2685fa60c3495ca13e63e8989affected · git
    • before 5.12not affected · semver
    • 5.15.221 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-93183Sep 17, 2026 · drm/lima: call drm_mm_init() with a valid allocation range
    0Monitor
  • ← EarlierCVE-2026-93184Sep 17, 2026 · ASoC: fsl_audmix: rework runtime PM handling in probe
    0Monitor
  • Later →CVE-2026-93186Sep 17, 2026 · cxl/mbox: Clamp mailbox output allocation to the payload size
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1bb23c9d68312e77cec81bdfb2cc385e2d2960f7Vendor (CNA)
Linux Linux1e8fddab6cbe536dd02e61205e4b9bf97df6479bVendor (CNA)
Linux Linux45fcf435ffcc5f61a43bd9b19094dc52de6cbc05Vendor (CNA)
Linux Linux612ccf42acd14bb2685fa60c3495ca13e63e8989Vendor (CNA)
Linux Linuxa47f087877bb2bc57c3ccb714fc49abf45d28e12Vendor (CNA)
Linux Linuxb81c2131dbb6fe04e27841bc719977c106177c61Vendor (CNA)
Linux Linuxf1e21b7b977f5ae2955ecf3ab144da2578a4fe00Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records