ASoC: cs35l34: 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 07a86575edc308e66b6c8873ed4a93ef3a063e55, 3be8380fb14d602cd833e5852e6d83c1e7eb1ceb, 4105a4c0678b2808fc8046b60321b4f1cc7dae75; 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 07a86575edc308e66b6c8873ed4a93ef3a063e55, 3be8380fb14d602cd833e5852e6d83c1e7eb1ceb, 4105a4c0678b2808fc8046b60321b4f1cc7dae75; 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
In the Linux kernel, the following vulnerability has been resolved: ASoC: cs35l34: drain threaded IRQ before runtime suspend cs35l34_runtime_suspend() currently switches the codec into regcache_cache_only(true), asserts reset low, and powers the device off without first quiescing the threaded IRQ registered by devm_request_threaded_irq(). That leaves a window where cs35l34_irq_thread() can still run after suspend has removed live hardware 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..4 after cache_only has been enabled, ignores the regmap_read() failures, and can still execute the PROT_RELEASE_CTL release sequence or the BST fault power-down writes. Use disable_irq() before entering cache_only/reset-low/power-off so any in-flight threaded handler is drained and no new IRQ thread can run while the device is suspended. Re-enable the IRQ only after runtime_resume() has restored live register access with regcache_sync(). Since probe only logs request_threaded_irq() failures and keeps going, track whether the IRQ was actually installed before disabling or re-enabling it.
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.10affected
- c1124c09e1035cabdbc17d4538ae6f922086fec9 and later · before 3be8380fb14d602cd833e5852e6d83c1e7eb1cebaffected · git
- c1124c09e1035cabdbc17d4538ae6f922086fec9 and later · before 96982734e765c13c3db02067e1d5784682085f5caffected · git
- c1124c09e1035cabdbc17d4538ae6f922086fec9 and later · before 5b063739619990d5de0c94c85d6e5be14e7cbdfeaffected · git
- c1124c09e1035cabdbc17d4538ae6f922086fec9 and later · before f4bfd755c52dfa7584e6c9374206b71b8895c997affected · git
- c1124c09e1035cabdbc17d4538ae6f922086fec9 and later · before 4fe8a91a9266f1321c2d31ce67940a4e8b93559eaffected · git
- c1124c09e1035cabdbc17d4538ae6f922086fec9 and later · before 5a4fe7a87841af23ba80bae31b80355b16926cf4affected · git
- c1124c09e1035cabdbc17d4538ae6f922086fec9 and later · before 07a86575edc308e66b6c8873ed4a93ef3a063e55affected · git
- c1124c09e1035cabdbc17d4538ae6f922086fec9 and later · before 4105a4c0678b2808fc8046b60321b4f1cc7dae75affected · git
- before 4.10not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | all versions | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 07a86575edc308e66b6c8873ed4a93ef3a063e55 | Vendor (CNA) |
| Linux Linux | 3be8380fb14d602cd833e5852e6d83c1e7eb1ceb | Vendor (CNA) |
| Linux Linux | 4105a4c0678b2808fc8046b60321b4f1cc7dae75 | Vendor (CNA) |
| Linux Linux | 4fe8a91a9266f1321c2d31ce67940a4e8b93559e | Vendor (CNA) |
| Linux Linux | 5a4fe7a87841af23ba80bae31b80355b16926cf4 | Vendor (CNA) |
| Linux Linux | 5b063739619990d5de0c94c85d6e5be14e7cbdfe | Vendor (CNA) |
| Linux Linux | 96982734e765c13c3db02067e1d5784682085f5c | Vendor (CNA) |
| Linux Linux | f4bfd755c52dfa7584e6c9374206b71b8895c997 | Vendor (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.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package 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.
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 researchersFinders, 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.
- TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3be8380fb14d602cd833e5852e6d83c1e7eb1ceb
- git.kernel.org/stable/c/4105a4c0678b2808fc8046b60321b4f1cc7dae75
- git.kernel.org/stable/c/4fe8a91a9266f1321c2d31ce67940a4e8b93559e
- git.kernel.org/stable/c/5a4fe7a87841af23ba80bae31b80355b16926cf4
- git.kernel.org/stable/c/5b063739619990d5de0c94c85d6e5be14e7cbdfe
- git.kernel.org/stable/c/96982734e765c13c3db02067e1d5784682085f5c
- git.kernel.org/stable/c/f4bfd755c52dfa7584e6c9374206b71b8895c997
Vendor advisories and official records. Exploit/PoC links are deliberately left out.