CVE-2026-43311 soc/tegra: pmc: Fix unsafe generic_handle_irq() call
An unsafe function call during system resume on Tegra platforms can trigger a kernel warning, potentially leading to system instability or denial of service.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-43311?
CVE-2026-43311 is a medium-severity denial of service vulnerability in Linux kernel, published on 8 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
[[email protected]: miscellaneous cleanups]
Which versions are affected by CVE-2026-43311?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2026-43311?
Apply the vendor's patch.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-43311 being exploited?
There is no known exploitation of CVE-2026-43311 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as AZL-86199, BELL-CVE-2026-43311, DEBIAN-CVE-2026-43311, GHSA-5vxj-rjpg-8mhr, ROOT-OS-DEBIAN-13-CVE-2026-43311, ROOT-OS-UBUNTU-2204-CVE-2026-43311 and 2 more.