CVE-2026-89945

CVE CVE-2026-89945EUVD EUVD-2026-80545Published 2026-09-16T10:32:31.000Z

What the advisory describes

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.

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 c1124c09e1035cabdbc17d4538ae6f922086fec9 <96982734e765c13c3db02067e1d5784682085f5c; c1124c09e1035cabdbc17d4538ae6f922086fec9 <5a4fe7a87841af23ba80bae31b80355b16926cf4; c1124c09e1035cabdbc17d4538ae6f922086fec9 <4105a4c0678b2808fc8046b60321b4f1cc7dae75; 4.10; patch: 0; patch: 7.3-rc1; c1124c09e1035cabdbc17d4538ae6f922086fec9 <f4bfd755c52dfa7584e6c9374206b71b8895c997; patch: 5.10.270; patch: 6.6.157; c1124c09e1035cabdbc17d4538ae6f922086fec9 <3be8380fb14d602cd833e5852e6d83c1e7eb1ceb; patch: 6.18.51; patch: 6.1.188; patch: 7.2.5; patch: 6.12.110; c1124c09e1035cabdbc17d4538ae6f922086fec9 <5b063739619990d5de0c94c85d6e5be14e7cbdfe; c1124c09e1035cabdbc17d4538ae6f922086fec9 <4fe8a91a9266f1321c2d31ce67940a4e8b93559e; c1124c09e1035cabdbc17d4538ae6f922086fec9 <07a86575edc308e66b6c8873ed4a93ef3a063e55; patch: 5.15.221

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.