CVE-2026-89946

Unknown

Last modified

CVE-2026-89946 is a vulnerability of currently unknown severity. 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.

Description

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8, < d07799302721d381aef834fac8a11d196894eccb; >= 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8, < 5b5311427e54d9c0d07178ee42df68ba44c2d5ca; >= 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8, < a04722542c76ce861031384480825afded8cc4f4; >= 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8, < 614c2616ea677abfbed917a92bdc5141efff3536; >= 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8, < 6ae98918240585eb2ad32b097c4810f4e2dabe88; >= 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8, < 6e369bc46663b4bfce3d5f8b8ed08e71ecea13a2; >= 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8, < 84cf6acd01a1ec8f30276578a039216327af782e; >= 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8, < e074c12c428c633e079154301207a6079a208583
LinuxLinux4.8

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-89946?
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.
How severe is CVE-2026-89946?
Severity scoring for CVE-2026-89946 is pending analysis.
How do I fix CVE-2026-89946?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-89946?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST