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]
Published: 2026-05-08
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The issue occurs during system suspend and resume in Tegra platforms, where an unsafe call to generic_handle_irq() is made from a non‑interrupt context, violating its API contract and producing a warning. The patch defers that call to a hard IRQ context, eliminating the warning. The CVE description does not report any crash or service disruption; it focuses on the warning message.

Affected Systems

Linux kernel builds that include the Tegra PMC driver; all kernels prior to the commit introducing IRQ_WORK_INIT_HARD are affected. Both PREEMPT_RT and non‑PREEMPT_RT kernels are impacted, with the PREEMPT_RT variant requiring IRQ_WORK_INIT_HARD to execute in hardirq context.

Risk and Exploitability

The CVSS score of 5.5 indicates medium severity, the vulnerability is not listed in the CISA KEV catalog, and EPSS data is not available. Attackers would need access that allows triggering system suspend/resume to experience the warning. No information suggests that this flaw can be exploited remotely or to gain elevated privileges; the risk appears limited to a warning that may signal kernel instability.

Generated by OpenCVE AI on May 9, 2026 at 03:00 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the kernel patch that defers generic_handle_irq() to hard IRQ context (for example, incorporate commit 64016227dcdb968b7030eda04304f3d0df5d209d).
  • If an upgrade is not immediately available, avoid running a PREEMPT_RT kernel or, if it is, ensure the PMC driver uses IRQ_WORK_INIT_HARD so the work is processed in hardirq context; otherwise defer suspend/resume cycles until the fix is applied.
  • After applying the update, monitor kernel logs for the absence of the "WARNING: CPU" message during resume and verify system stability under typical suspend/resume workloads.

Generated by OpenCVE AI on May 9, 2026 at 03:00 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 09 May 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-821
References
Metrics threat_severity

None

 cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low

Fri, 08 May 2026 16:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362
CWE-646

Fri, 08 May 2026 13:30:00 +0000

Type Values Removed Values Added
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]
Title soc/tegra: pmc: Fix unsafe generic_handle_irq() call
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-05-09T04:10:25.725Z

Reserved: 2026-05-01T14:12:56.001Z

Link: CVE-2026-43311

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-05-08T14:16:39.480

Modified: 2026-05-08T14:16:39.480

Link: CVE-2026-43311

cve-icon Redhat

Severity : Low

Publid Date: 2026-05-08T00:00:00Z

Links: CVE-2026-43311 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-05-09T03:00:11Z

Weaknesses