Skip to main content

Linux Kernel CVE-2026-43311

| EUVDEUVD-2026-28581 MEDIUM
2026-05-08 Linux GHSA-5vxj-rjpg-8mhr
5.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Gain local shell access
  2. Delivery
    Trigger system suspend via /sys/power/state
  3. Exploit
    System enters S3 sleep
  4. Install
    Resume initiated
  5. C2
    PMC wake handler executes
  6. Execute
    generic_handle_irq() called in wrong context
  7. Impact
    Kernel warning triggers
  8. Step 8
    Repeat to cause IRQ subsystem instability
  9. Step 9
    System denial of service

Vulnerability Assessment

Exploitation Conditions

Requires Nvidia Tegra186/194/234 SoC platform running vulnerable Linux kernel with Tegra PMC driver compiled and active (standard configuration for Tegra boards). Attacker must have local authenticated shell access with permissions to trigger system suspend operations via /sys/power/state interface or systemd-logind. Exploitation occurs automatically during normal resume from suspend-to-RAM (S3) power state when PMC wake events are processed. No special kernel boot parameters or non-default configurations required beyond Tegra platform support being enabled at compile time. User interaction not required for exploitation once suspend initiated. Attack limited to specific ARM64 Tegra hardware platforms - does not affect x86, other ARM vendors, or non-Tegra configurations even with same kernel version.

Impact

Real-world risk is moderate to low. CVSS 5.5 reflects local access requirement (AV:L), low attack complexity (AC:L), and authenticated attacker (PR:L) causing high availability impact (A:H) through kernel warnings and potential system instability during suspend/resume cycles. However, EPSS score of 0.02% (5th percentile) indicates near-zero observed exploitation probability in the wild, consistent with this being an availability issue rather than memory corruption or privilege escalation. The vulnerability triggers during legitimate system operations (suspend/resume) rather than attacker-controlled code paths, limiting practical exploitability. While CVSS suggests high availability impact, the actual consequence is kernel warning messages and potential resume failures rather than hard crashes or data loss. No CISA KEV listing confirms this is not being actively exploited. Primary risk is to Tegra-based embedded systems requiring reliable suspend/resume functionality (automotive infotainment, industrial controllers). Standard desktop/server Linux deployments are unaffected as they don't use Tegra PMC drivers. Patches available in stable kernel branches reduce urgency. Key missing data: No public POC identified, no reports of exploitation causing actual system failures beyond warning messages.

Exploit ScenarioDerived

Local authenticated attacker with standard user privileges on Tegra-based system triggers repeated suspend/resume cycles through systemd, ACPI interface, or direct /sys/power/state writes. Each resume operation invokes tegra186_pmc_wake_syscore_resume which calls generic_handle_irq() from process context, generating kernel warnings and potentially destabilizing IRQ handling subsystem. Repeated exploitation causes kernel log flooding, IRQ descriptor corruption, or resume failures leading to denial of service requiring system reboot.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 15, 2026

Linux kernel's Tegra PMC driver can trigger kernel warnings and potential denial of service during system resume by calling generic_handle_irq() from non-interrupt context. Affects Tegra186 and later platforms running Linux kernel versions prior to 6.19.6 and 7.0. CVSS 5.5 indicates local low-complexity exploitation requiring authenticated access. EPSS score of 0.02% (5th percentile) suggests minimal observed exploitation activity. Vendor patches available via stable kernel tree commits.

RemediationAI

Upgrade to Linux kernel version 6.19.6 or 7.0 or later, which contain vendor-released patches (upstream commits e6d96073af681780820c94079b978474a8a44413 and 64016227dcdb968b7030eda04304f3d0df5d209d available at https://git.kernel.org/stable/). For systems unable to upgrade immediately, apply compensating controls: disable suspend/resume functionality via kernel command line parameter 'no_console_suspend' or systemd sleep configuration to prevent execution of vulnerable code path (trade-off: loss of power management features increases energy consumption). On PREEMPT_RT kernels specifically, ensure IRQ threading is properly configured to isolate IRQ context violations. For embedded systems with custom kernel builds, backport the two-commit fix series which refactors tegra186_pmc_wake_syscore_resume to use init_irq_work with IRQ_WORK_INIT_HARD flag. Compensating controls significantly impact power efficiency and are unsuitable for battery-powered or automotive applications requiring suspend/resume. Long-term mitigation requires kernel upgrade to stable release incorporating vendor fix.

Affected VersionsENISA

Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e6d96073af681780820c94079b978474a8a44413
Linux patch: 6.19.6
Linux patch: 7.0
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <64016227dcdb968b7030eda04304f3d0df5d209d

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in the Tegra PMC (Power Management Controller) driver's system suspend/resume infrastructure (soc/tegra/pmc). The tegra186_pmc_wake_syscore_resume() function incorrectly invokes generic_handle_irq() directly from syscore_resume context, which executes in process context during system resume operations. The kernel's IRQ descriptor handling code (kernel/irq/irqdesc.c:666) explicitly validates execution context and generates warnings when generic_handle_irq() is called outside hard IRQ context, as this violates IRQ handling safety invariants. On PREEMPT_RT configurations, the safety violation becomes more severe since regular IRQ work executes in preemptible kthreads rather than hardirq context. The fix defers IRQ handling to IRQ work infrastructure using IRQ_WORK_INIT_HARD to guarantee hard IRQ context execution across both standard and PREEMPT_RT kernel builds. This affects Nvidia Tegra186/194/234 SoC platforms which are ARM64-based systems commonly used in automotive and embedded applications.

Know when Nvidia gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SUSE MEDIUM
Red Hat 5.5 LOW

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

3
CVSS changed
May 15, 2026 - 18:07 NVD
5.5 (MEDIUM)
Patch available
May 08, 2026 - 14:33 EUVD
CVE Published
May 08, 2026 - 13:11 nvd
UNKNOWN (no severity yet)

DescriptionNVD

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]

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in Nvidia

View all
CVE-2017-14491 CRITICAL POC
9.8 Oct 04

Heap-based buffer overflow in dnsmasq before 2.78 allows remote attackers to cause a denial of service (crash) or execut

CVE-2018-3639 MEDIUM POC
5.5 May 22

Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addres

CVE-2016-1741 CRITICAL POC
9.8 Mar 24

The NVIDIA driver in the Graphics Drivers subsystem in Apple OS X before 10.11.4 allows attackers to execute arbitrary c

CVE-2013-0109 HIGH POC
7.2 Apr 08

The NVIDIA driver before 307.78, and Release 310 before 311.00, in the NVIDIA Display Driver service on Windows does not

CVE-2019-5684 CRITICAL POC
10.0 Aug 06

NVIDIA Windows GPU Display Driver (all versions) contains a vulnerability in DirectX drivers, in which a specially craft

CVE-2026-24207 CRITICAL POC
9.8 May 20

Authentication bypass in NVIDIA Triton Inference Server allows unauthenticated remote attackers to reach protected funct

CVE-2019-5685 CRITICAL POC
9.8 Aug 06

NVIDIA Windows GPU Display Driver (all versions) contains a vulnerability in DirectX drivers, in which a specially craft

CVE-2025-23359 HIGH POC
8.3 Feb 12

NVIDIA Container Toolkit for Linux contains a Time-of-Check Time-of-Use (TOCTOU) vulnerability when used with default co

CVE-2016-8812 HIGH POC
8.8 Nov 08

For the NVIDIA Quadro, NVS, and GeForce products, NVIDIA GeForce Experience R340 before GFE 2.11.4.125 and R375 before G

CVE-2017-1000251 HIGH POC
8.0 Sep 12

The native Bluetooth stack in the Linux Kernel (BlueZ), starting at the Linux kernel version 2.6.32 and up to and includ

CVE-2016-1861 HIGH POC
7.8 Jun 19

The NVIDIA Graphics Drivers subsystem in Apple OS X before 10.11.5 allows attackers to execute arbitrary code in a privi

CVE-2024-0132 HIGH POC
8.3 Sep 26

NVIDIA Container Toolkit 1.16.1 or earlier contains a Time-of-check Time-of-Use (TOCTOU) vulnerability when used with de

Vendor StatusVendor

SUSE

Severity: Medium
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy