CVE-2026-43311

published 8 May 2026 · updated 16 Nov 2026

soc/tegra: pmc: Fix unsafe generic_handle_irq() call

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e6d96073af681780820c94079b978474a8a44413, Kernel 57a79c5df057deb7c1d0ebc066698c795092530f, Kernel 64016227dcdb968b7030eda04304f3d0df5d209d and 6 more.

In the Linux kernel, the following vulnerability has been resolved: soc/tegra: pmc: Fix unsafe generic_handle_irq() call Currently, when resuming from system suspend on Tegra platforms, the following warning is observed: WARNING: CPU: 0 PID: 14459 at kernel/irq/irqdesc.c:666 Call trace: handle_irq_desc+0x20/0x58 (P) tegra186_pmc_wake_syscore_resume+0xe4/0x15c syscore_resume+0x3c/0xb8 suspend_devices_and_enter+0x510/0x540 pm_suspend+0x16c/0x1d8 The warning occurs because generic_handle_irq() is being called from a non-interrupt context which is considered as unsafe. Fix this warning by deferring generic_handle_irq() call to an IRQ work which gets executed in hard IRQ context where generic_handle_irq() can be called safely. When PREEMPT_RT kernels are used, regular IRQ work (initialized with init_irq_work) is deferred to run in per-CPU kthreads in preemptible context rather than hard IRQ context. Hence, use the IRQ_WORK_INIT_HARD variant so that with PREEMPT_RT kernels, the IRQ work is processed in hardirq context instead of being deferred to a thread which is required for calling generic_handle_irq(). On non-PREEMPT_RT kernels, both init_irq_work() and IRQ_WORK_INIT_HARD() execute in IRQ context, so this change has no functional impact for standard kernel configurations. [treding@nvidia.com: miscellaneous cleanups]

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=0474cc8489bda9a8cd6a10252e7e6af29c849438 <e6d96073af681780820c94079b978474a8a44413, >=0474cc8489bda9a8cd6a10252e7e6af29c849438 <57a79c5df057deb7c1d0ebc066698c795092530f, >=0474cc8489bda9a8cd6a10252e7e6af29c849438 <64016227dcdb968b7030eda04304f3d0df5d209d, >=0474cc8489bda9a8cd6a10252e7e6af29c849438 <d1c9c79eb06ed7c4e0a090ba5b1d4e475f7d0681, >=6.2 <6.19.6, =6.2, >=0474cc8489bda9a8cd6a10252e7e6af29c849438 <5330afc068e90c538dd25aa8f82b3735bdb6d461e6d96073af681780820c94079b978474a8a44413, 57a79c5df057deb7c1d0ebc066698c795092530f, 64016227dcdb968b7030eda04304f3d0df5d209d, d1c9c79eb06ed7c4e0a090ba5b1d4e475f7d0681, 6.19.6, 5330afc068e90c538dd25aa8f82b3735bdb6d461
linux-kernel: Kernel>=6.13.0 <6.18.57, >=6.19.0 <6.19.6, >=6.2.0 <6.6.143, >=6.7.0 <6.12.1146.18.57, 6.19.6, 6.6.143, 6.12.114

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-43311 severity on Zeptric[![CVE-2026-43311](https://zeptric.io/badge/cve/CVE-2026-43311.svg)](https://zeptric.io/cve/CVE-2026-43311)