Skip to main content

Linux Kernel CVE-2026-53297

| EUVDEUVD-2026-39902 MEDIUM
NULL Pointer Dereference (CWE-476)
2026-06-26 Linux GHSA-43rv-4q7x-r3cg
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
4.7 MEDIUM

AC:H applied because exploitation requires a non-attacker-controlled PM resume failure precondition; all other metrics align with the provided vector.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative
Red Hat
5.5 LOW
qualitative

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

5
Analysis Generated
Jul 08, 2026 - 04:35 vuln.today
CVSS changed
Jul 08, 2026 - 04:07 NVD
5.5 (MEDIUM)
Patch available
Jun 26, 2026 - 21:02 EUVD
CVE Published
Jun 26, 2026 - 19:40 nvd
MEDIUM 5.5
CVE Published
Jun 26, 2026 - 19:40 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

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

net: mana: Guard mana_remove against double invocation

If PM resume fails (e.g., mana_attach() returns an error), mana_probe() calls mana_remove(), which tears down the device and sets gd->gdma_context = NULL and gd->driver_data = NULL.

However, a failed resume callback does not automatically unbind the driver. When the device is eventually unbound, mana_remove() is invoked a second time. Without a NULL check, it dereferences gc->dev with gc == NULL, causing a kernel panic.

Add an early return if gdma_context or driver_data is NULL so the second invocation is harmless. Move the dev = gc->dev assignment after the guard so it cannot dereference NULL.

AnalysisAI

Kernel panic via NULL pointer dereference in the Linux kernel MANA (Microsoft Azure Network Adapter) driver allows a local low-privileged user to crash the host when a power management resume failure leaves the driver in a torn-down state. The mana_remove() function is invoked twice - first during a failed mana_probe() recovery path that nullifies gdma_context and driver_data, and again when the driver is subsequently unbound - dereferencing a NULL gc pointer. No public exploit exists and EPSS is 0.17% (6th percentile), indicating minimal real-world exploitation activity; however, the impact on Azure Linux VM availability is complete (kernel panic).

Technical ContextAI

The affected code resides in drivers/net/ethernet/microsoft/mana/ within the Linux kernel, implementing the MANA virtual NIC used by Azure VMs running atop Hyper-V. CWE-476 (NULL Pointer Dereference) describes the root cause: mana_probe() invokes mana_remove() upon failure (e.g., mana_attach() error during PM resume), which sets gd->gdma_context = NULL and gd->driver_data = NULL as part of teardown. Because a failed resume callback does not automatically unbind the driver, a subsequent driver unbind triggers a second mana_remove() invocation. Without a NULL guard on gdma_context, the function executes gc->dev where gc is NULL, producing a kernel panic. The fix adds an early return guarding both pointer values and moves the dev = gc->dev assignment past the guard. CPE confirms the affected product as cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*, covering the mainline kernel from the commit introducing the MANA driver (635096a86edb) up to the respective stable-tree fix commits.

RemediationAI

Upgrade to Linux kernel 6.18.33, 7.0.10, or 7.1 where the NULL guard in mana_remove() has been applied; patch commits are confirmed at the three kernel.org stable links in the references. Distribution-specific kernel packages (RHEL, Ubuntu, SUSE, Debian) should be monitored for backport availability using each vendor's security advisories. If immediate kernel upgrade is not feasible, a practical compensating control is to avoid issuing PM suspend/resume cycles on Azure VMs running affected kernel versions - disabling system suspend via systemctl mask sleep.target hibernate.target suspend.target hybrid-sleep.target prevents the PM resume path that triggers the vulnerability, at the cost of losing power-save functionality. Alternatively, organizations with strict change windows can restrict local shell access to the VM (reducing PR:L exposure) as a defense-in-depth measure, though this does not address the underlying race condition if PM resume failures occur through infrastructure events. No confidentiality or integrity risk means there is no urgency beyond routine patch cycles for environments that do not perform frequent suspend/resume operations.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

CVE-2026-53297 vulnerability details – vuln.today

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