CVE-2026-89946

CVE CVE-2026-89946EUVD EUVD-2026-80546Published 2026-09-16T10:32:32.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <e074c12c428c633e079154301207a6079a208583; 4.8; patch: 6.18.51; patch: 7.2.5; patch: 6.1.188; 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <6e369bc46663b4bfce3d5f8b8ed08e71ecea13a2; patch: 5.15.221; 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <6ae98918240585eb2ad32b097c4810f4e2dabe88; 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <a04722542c76ce861031384480825afded8cc4f4; patch: 7.3-rc1; 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <d07799302721d381aef834fac8a11d196894eccb; patch: 6.6.157; 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <614c2616ea677abfbed917a92bdc5141efff3536; 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <5b5311427e54d9c0d07178ee42df68ba44c2d5ca; 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <84cf6acd01a1ec8f30276578a039216327af782e; patch: 6.12.110; patch: 5.10.270; patch: 0

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.