CVE-2026-43311: soc/tegra: pmc: Fix unsafe generic_handle_irq() call

Published May 8, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

soc/tegra: pmc: Fix unsafe generichandleirq() 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: handleirqdesc+0x20/0x58 (P) tegra186pmcwakesyscoreresume+0xe4/0x15c syscoreresume+0x3c/0xb8 suspenddevicesandenter+0x510/0x540 pmsuspend+0x16c/0x1d8

The warning occurs because generichandleirq() is being called from a non-interrupt context which is considered as unsafe.

Fix this warning by deferring generichandleirq() call to an IRQ work which gets executed in hard IRQ context where generichandleirq() can be called safely.

When PREEMPTRT kernels are used, regular IRQ work (initialized with initirqwork) is deferred to run in per-CPU kthreads in preemptible context rather than hard IRQ context. Hence, use the IRQWORKINITHARD variant so that with PREEMPTRT kernels, the IRQ work is processed in hardirq context instead of being deferred to a thread which is required for calling generichandleirq().

On non-PREEMPTRT kernels, both initirqwork() and IRQWORKINITHARD() execute in IRQ context, so this change has no functional impact for standard kernel configurations.

[treding@nvidia.com: miscellaneous cleanups]

Affected Software

2 affected components
Linux Linux kernel (soc/tegra pmc)
Linux Linux kernel>=6.2<6.19.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Defer the generic_handle_irq() call to IRQ work and initialize that IRQ work with IRQ_WORK_INIT_HARD.

    Linux kernel Tegra PMC IRQ work initializer for deferred generic_handle_irq() = IRQ_WORK_INIT_HARD

Event History

May 8, 2026
CVE Published
via MITRE·01:11 PM
Data Sourced
via MITRE·01:11 PM
Description
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-43311?

CVE-2026-43311 is considered to have a low severity impact due to its specific platform restrictions.

2

How do I fix CVE-2026-43311?

To mitigate CVE-2026-43311, update to the latest version of the Linux kernel that includes the fix for the unsafe generic_handle_irq() call.

3

Which versions of Linux kernel are affected by CVE-2026-43311?

CVE-2026-43311 affects specific versions of the Linux kernel on Tegra platforms.

4

What platforms are impacted by CVE-2026-43311?

CVE-2026-43311 impacts Tegra platforms within the Linux kernel.

5

Is there a workaround for CVE-2026-43311?

Currently, there is no known workaround for CVE-2026-43311; applying the latest updates is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203