UBUNTU-CVE-2026-43311: Medium severity ubuntu/linux-hwe-edge vulnerability

Q: Which systems are most likely to be exposed to this issue?

The issue is associated with Tegra platforms during resume from system suspend. The affected Ubuntu kernel packages listed are linux-riscv, linux-realtime, linux-azure, linux-gcp, linux-azure-fde, linux-hwe-edge, linux-gke, and linux-gkeop.

Q: What conditions are required to trigger the problem?

A local attacker requires low privileges, and the vulnerable path is reached when a Tegra system resumes from system suspend. No user interaction is required.

Q: What is the expected security impact?

The listed impact is availability only: confidentiality and integrity are unaffected, while availability is rated high impact. The supplied severity vector rates the issue 5.5 (medium).

Q: Is PREEMPT_RT relevant to the affected behavior?

Yes. On PREEMPT_RT kernels, ordinary IRQ work can run in a per-CPU thread rather than hard IRQ context, so the fix uses IRQ_WORK_INIT_HARD to ensure the deferred handler runs in hard IRQ context.

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

148 affected componentsFixes available

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.8*

ubuntu/linux-intel-5.13*

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-aws-6.8<6.8.0-1066.69~22.04.1

6.8.0-1066.69~22.04.1

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-6.8<6.8.0-1070.78~22.04.1

6.8.0-1070.78~22.04.1

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-azure-fde-6.8<6.8.0-1068.75~22.04.1

6.8.0-1068.75~22.04.1

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-gcp-6.8<6.8.0-1070.78~22.04.1

6.8.0-1070.78~22.04.1

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-ibm-6.8<6.8.0-1066.67~22.04.1

6.8.0-1066.67~22.04.1

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-lowlatency-hwe-6.8<6.8.0-146.146.1~22.04.1

6.8.0-146.146.1~22.04.1

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-nvidia-6.8<6.8.0-1064.67~22.04.1

6.8.0-1064.67~22.04.1

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle-6.5*

ubuntu/linux-oracle-6.8*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-riscv-6.8<6.8.0-146.146~22.04.1

6.8.0-146.146~22.04.1

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-realtime-6.8<6.8.1-1061.62~22.04.1

6.8.1-1061.62~22.04.1

ubuntu/linux<6.8.0-146.146

6.8.0-146.146

ubuntu/linux-aws<6.8.0-1066.69

6.8.0-1066.69

ubuntu/linux-aws-6.14*

ubuntu/linux-aws-6.17*

ubuntu/linux-azure<6.8.0-1070.78

6.8.0-1070.78

ubuntu/linux-azure-6.11*

ubuntu/linux-azure-6.14*

ubuntu/linux-azure-6.17*

ubuntu/linux-azure-fde<6.8.0-1068.75

6.8.0-1068.75

ubuntu/linux-azure-fde-6.14*

ubuntu/linux-azure-fde-6.17*

ubuntu/linux-azure-nvidia*

ubuntu/linux-azure-nvidia-6.14*

ubuntu/linux-gcp<6.8.0-1070.78

6.8.0-1070.78

ubuntu/linux-gcp-6.11*

ubuntu/linux-gcp-6.14*

ubuntu/linux-gke<6.8.0-1065.73

6.8.0-1065.73

ubuntu/linux-gkeop<6.8.0-1051.55

6.8.0-1051.55

ubuntu/linux-hwe-6.11*

ubuntu/linux-hwe-6.14*

ubuntu/linux-hwe-6.17*

ubuntu/linux-ibm<6.8.0-1066.67

6.8.0-1066.67

ubuntu/linux-lowlatency<6.8.0-146.146.1

6.8.0-146.146.1

ubuntu/linux-lowlatency-hwe-6.11*

ubuntu/linux-nvidia<6.8.0-1064.67

6.8.0-1064.67

ubuntu/linux-nvidia-6.11*

ubuntu/linux-nvidia-6.17*

ubuntu/linux-nvidia-lowlatency<6.8.0-1064.67.1

6.8.0-1064.67.1

ubuntu/linux-nvidia-tegra*

ubuntu/linux-oem-6.11*

ubuntu/linux-oem-6.14*

ubuntu/linux-oem-6.17*

ubuntu/linux-oem-6.8*

ubuntu/linux-oracle<6.8.0-1063.66

6.8.0-1063.66

ubuntu/linux-oracle-6.14*

ubuntu/linux-oracle-6.17*

ubuntu/linux-raspi*

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-6.14*

ubuntu/linux-riscv-6.17*

ubuntu/linux-xilinx*

ubuntu/linux-bluefield<6.8.0-1032.37

6.8.0-1032.37

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime<6.8.1-1061.62

6.8.1-1061.62

ubuntu/linux-realtime-6.14*

ubuntu/linux-realtime-6.17*

ubuntu/linux-aws-fips<6.8.0-1066.69+fips1

6.8.0-1066.69+fips1

ubuntu/linux-azure-fips<6.8.0-1069.77+fips1

6.8.0-1069.77+fips1

ubuntu/linux-fips<6.8.0-146.146+fips1

6.8.0-146.146+fips1

ubuntu/linux-gcp-fips<6.8.0-1070.78+fips1

6.8.0-1070.78+fips1

ubuntu/linux*

ubuntu/linux-aws*

ubuntu/linux-azure*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp*

ubuntu/linux-oracle*

ubuntu/linux-raspi*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1066.69~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1070.78~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1068.75~22.04.1
Upgrade
Upgrade ubuntu/linux-gcp-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1070.78~22.04.1
Upgrade
Upgrade ubuntu/linux-ibm-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1066.67~22.04.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-146.146.1~22.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1064.67~22.04.1
Upgrade
Upgrade ubuntu/linux-riscv-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-146.146~22.04.1
Upgrade
Upgrade ubuntu/linux-realtime-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.1-1061.62~22.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.8.0-146.146
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.8.0-1066.69
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.8.0-1070.78
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 6.8.0-1068.75
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.8.0-1070.78
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 6.8.0-1065.73
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 6.8.0-1051.55
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 6.8.0-1066.67
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-146.146.1
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1064.67
Upgrade
Upgrade ubuntu/linux-nvidia-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-1064.67.1
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.8.0-1063.66
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 6.8.0-1032.37
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.8.1-1061.62
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1066.69+fips1
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1069.77+fips1
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-146.146+fips1
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1070.78+fips1
Compensating control
In the Linux kernel soc/tegra PMC resume path, defer the generic_handle_irq() call to IRQ work and initialize that work with IRQ_WORK_INIT_HARD so it executes in hard IRQ context, including on PREEMPT_RT kernels.

Event History

May 8, 2026

CVE Published

via OSV·02:16 PM

Data Sourced

via OSV·02:16 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

Which systems are most likely to be exposed to this issue?

The issue is associated with Tegra platforms during resume from system suspend. The affected Ubuntu kernel packages listed are linux-riscv, linux-realtime, linux-azure, linux-gcp, linux-azure-fde, linux-hwe-edge, linux-gke, and linux-gkeop.

What conditions are required to trigger the problem?

A local attacker requires low privileges, and the vulnerable path is reached when a Tegra system resumes from system suspend. No user interaction is required.

What is the expected security impact?

The listed impact is availability only: confidentiality and integrity are unaffected, while availability is rated high impact. The supplied severity vector rates the issue 5.5 (medium).

Is PREEMPT_RT relevant to the affected behavior?

Yes. On PREEMPT_RT kernels, ordinary IRQ work can run in a per-CPU thread rather than hard IRQ context, so the fix uses IRQ_WORK_INIT_HARD to ensure the deferred handler runs in hard IRQ context.

UBUNTU-CVE-2026-43311: Medium severity ubuntu/linux-hwe-edge vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

Which systems are most likely to be exposed to this issue?

What conditions are required to trigger the problem?

What is the expected security impact?

Is PREEMPT_RT relevant to the affected behavior?

Company

Resources

Contact

Frequently Asked Questions

Which systems are most likely to be exposed to this issue?

What conditions are required to trigger the problem?

What is the expected security impact?

Is PREEMPT_RT relevant to the affected behavior?