VulnerabilityPublished 8 May 2026Updated 21 Oct 2026

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

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in e6d96073af681780820c94079b978474a8a44413 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in e6d96073af681780820c94079b978474a8a44413, d1c9c79eb06ed7c4e0a090ba5b1d4e475f7d0681, 64016227dcdb968b7030eda04304f3d0df5d209d +2

Exploitation evidence

Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 0474cc8489bda9a8cd6a10252e7e6af29c849438, < e6d96073af681780820c94079b978474a8a44413	Fixed in e6d96073af681780820c94079b978474a8a44413
LinuxLinux	Affected ≥ 0474cc8489bda9a8cd6a10252e7e6af29c849438, < d1c9c79eb06ed7c4e0a090ba5b1d4e475f7d0681	Fixed in d1c9c79eb06ed7c4e0a090ba5b1d4e475f7d0681
LinuxLinux	Affected ≥ 0474cc8489bda9a8cd6a10252e7e6af29c849438, < 64016227dcdb968b7030eda04304f3d0df5d209d	Fixed in 64016227dcdb968b7030eda04304f3d0df5d209d
LinuxLinux	Affected ≥ 0474cc8489bda9a8cd6a10252e7e6af29c849438, < 5330afc068e90c538dd25aa8f82b3735bdb6d461	Fixed in 5330afc068e90c538dd25aa8f82b3735bdb6d461
LinuxLinux	Affected ≥ 0474cc8489bda9a8cd6a10252e7e6af29c849438, < 57a79c5df057deb7c1d0ebc066698c795092530f	Fixed in 57a79c5df057deb7c1d0ebc066698c795092530f
LinuxLinux	Affected =6.2	Fixed in–

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]

References

Community reviews

Loading reviews…