Skip to main content

Linux Kernel CVE-2026-64120

| EUVDEUVD-2026-45805 MEDIUM
NULL Pointer Dereference (CWE-476)
2026-07-19 Linux GHSA-4j8v-vv2j-8xpv
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
5.5 MEDIUM

Local attack vector and low-privilege access confirmed by ethtool interface access pattern; purely availability impact via kernel panic with no confidentiality or integrity exposure.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/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
Aug 13, 2026 - 15:28 vuln.today
CVSS changed
Aug 13, 2026 - 15:22 NVD
5.5 (MEDIUM)
Patch available
Jul 19, 2026 - 17:03 EUVD
CVE Published
Jul 19, 2026 - 15:40 nvd
MEDIUM 5.5
CVE Published
Jul 19, 2026 - 15:40 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

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

net: ethtool: fix NULL pointer dereference in phy_reply_size

In phy_prepare_data(), several strings such as 'name', 'drvname', 'upstream_sfp_name', and 'downstream_sfp_name' are allocated using kstrdup(). However, these allocations were not checked for failure.

If kstrdup() fails for 'name', it returns NULL while the function continues. This leads to a kernel NULL pointer dereference and panic later in phy_reply_size() when it unconditionally calls strlen() on the NULL pointer.

While other strings like 'upstream_sfp_name' might be checked before access in certain code paths, failing to handle these allocations consistently can lead to incomplete data reporting or hidden bugs.

Fix this by adding proper NULL checks for all kstrdup() calls in phy_prepare_data() and implement a centralized error handling path using goto labels to ensure all previously allocated resources are freed on failure.

AnalysisAI

NULL pointer dereference in the Linux kernel's ethtool PHY subsystem allows a local low-privileged user to crash the kernel and cause a denial of service. The flaw in phy_prepare_data() fails to check return values from kstrdup() for the strings name, drvname, upstream_sfp_name, and downstream_sfp_name; when allocation fails and returns NULL, phy_reply_size() subsequently calls strlen() unconditionally on the NULL pointer, triggering a kernel oops and system panic. No public exploit code has been identified and EPSS stands at 0.17% (6th percentile), but the availability impact is total - a kernel panic - making this a standard patching priority for any multi-user or shared Linux environment.

Technical ContextAI

The vulnerability resides in the Linux kernel's ethtool netlink subsystem under net/ethtool, specifically in the code path that prepares PHY (physical layer) device data for netlink replies. phy_prepare_data() uses kstrdup() - a kernel-space string duplication function that can legitimately return NULL under memory pressure - to allocate string fields including device name, driver name, and SFP upstream/downstream names. Without NULL-checks on these allocations, execution falls through to phy_reply_size(), which unconditionally calls strlen() on what may be a NULL pointer. On all major Linux architectures, a NULL pointer dereference in kernel context produces an oops and typically a kernel panic, crashing the system. The root cause class is CWE-476 (NULL Pointer Dereference), a pervasive class of defect in C-language kernel code arising from inconsistent allocation-failure handling. The affected CPE is cpe:2.3:a:linux:linux:* across kernel versions from the introducing commit (9dd2ad5e92b962d1349a7541d167e8e214e49f95) up to the stable-branch fixes in 6.18.34, 7.0.11, and mainline 7.1. The fix introduces explicit NULL checks on each kstrdup() return and a centralized goto-based cleanup path to free all previously allocated resources on any allocation failure.

RemediationAI

The primary remediation is to upgrade the Linux kernel to version 6.18.34, 7.0.11, or 7.1, which incorporate the NULL-check patches and centralized error handling via goto cleanup in phy_prepare_data(). Upstream fix commits are available at https://git.kernel.org/stable/c/61f53c1e58d68723bc1db10912a53f1991f08719 (6.18.x stable), https://git.kernel.org/stable/c/4908f1395fb1b832ceec11584af649874a2732ea (7.0.x stable), and https://git.kernel.org/stable/c/3dbe20a3809347bacda890822e7ca013bd85a18c (7.1 mainline). Ubuntu users should apply the update referenced in USN-8593-1 at https://ubuntu.com/security/notices/USN-8593-1. As a compensating control prior to patching, restricting unprivileged access to ethtool PHY operations - for example by tightening CAP_NET_ADMIN requirements via seccomp profiles, confining users to network namespaces, or deploying LSM policies (AppArmor or SELinux) that deny ethtool socket operations - reduces exposure, though this may impact legitimate network diagnostics and monitoring tooling. There is no configuration toggle to disable the vulnerable code path without patching.

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-64120 vulnerability details – vuln.today

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