Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-89946: ASoC: cs35l33: drain threaded IRQ before runtime suspend

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 5b5311427e54d9c0d07178ee42df68ba44c2d5ca, 614c2616ea677abfbed917a92bdc5141efff3536, 6ae98918240585eb2ad32b097c4810f4e2dabe88; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 5b5311427e54d9c0d07178ee42df68ba44c2d5ca, 614c2616ea677abfbed917a92bdc5141efff3536, 6ae98918240585eb2ad32b097c4810f4e2dabe88; 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: cs35l33: drain threaded IRQ before runtime suspend cs35l33_runtime_suspend() currently switches the codec into regcache_cache_only(true) and powers it down without first quiescing the threaded IRQ registered by devm_request_threaded_irq(). That leaves a window where cs35l33_irq_thread() can still run after suspend has closed off live register access. A running system can reach this during runtime PM while the driver still has critical fault IRQs unmasked. If the threaded handler runs in that window, it reads volatile INT_STATUS_1/2 after cache_only has been enabled, ignores the regmap_read() failures, and can still drive the AMP_SHORT_RLS, CAL_ERR_RLS, OTE_RLS, and OTW_RLS release paths. Use disable_irq() before entering cache_only/power-off so any in-flight threaded handler is drained and no new IRQ thread can run during the suspended state. Re-enable the IRQ only after runtime_resume() has restored live register access with regcache_sync(). Since probe only warns if devm_request_threaded_irq() fails, track whether the IRQ was actually installed before disabling or re-enabling it.

—No exploit Fix available
Published
Sep 16, 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-89946

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

    • 4.8affected
    • 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and later · before d07799302721d381aef834fac8a11d196894eccbaffected · git
    • 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and later · before 5b5311427e54d9c0d07178ee42df68ba44c2d5caaffected · git
    • 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and later · before a04722542c76ce861031384480825afded8cc4f4affected · git
    • 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and later · before 614c2616ea677abfbed917a92bdc5141efff3536affected · git
    • 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and later · before 6ae98918240585eb2ad32b097c4810f4e2dabe88affected · git
    • 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and later · before 6e369bc46663b4bfce3d5f8b8ed08e71ecea13a2affected · git
    • 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and later · before 84cf6acd01a1ec8f30276578a039216327af782eaffected · git
    • 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and later · before e074c12c428c633e079154301207a6079a208583affected · git
    • before 4.8not 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-89944Sep 16, 2026 · ASoC: hdac_hda: Fix hlink refcount leak on component registration failure
    0Monitor
  • ← EarlierCVE-2026-89945Sep 16, 2026 · ASoC: cs35l34: drain threaded IRQ before runtime suspend
    0Monitor
  • Later →CVE-2026-89947Sep 16, 2026 · clk: meson: align gxbb_32k_clk_sel number of parents with actual count
    32Monitor

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 Linux5b5311427e54d9c0d07178ee42df68ba44c2d5caVendor (CNA)
Linux Linux614c2616ea677abfbed917a92bdc5141efff3536Vendor (CNA)
Linux Linux6ae98918240585eb2ad32b097c4810f4e2dabe88Vendor (CNA)
Linux Linux6e369bc46663b4bfce3d5f8b8ed08e71ecea13a2Vendor (CNA)
Linux Linux84cf6acd01a1ec8f30276578a039216327af782eVendor (CNA)
Linux Linuxa04722542c76ce861031384480825afded8cc4f4Vendor (CNA)
Linux Linuxd07799302721d381aef834fac8a11d196894eccbVendor (CNA)
Linux Linuxe074c12c428c633e079154301207a6079a208583Vendor (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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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 (7 more)

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

All records