CVE-2026-64120
Last modified
CVE-2026-64120 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 9dd2ad5e92b962d1349a7541d167e8e214e49f95, < 61f53c1e58d68723bc1db10912a53f1991f08719; >= 9dd2ad5e92b962d1349a7541d167e8e214e49f95, < 3dbe20a3809347bacda890822e7ca013bd85a18c; >= 9dd2ad5e92b962d1349a7541d167e8e214e49f95, < 4908f1395fb1b832ceec11584af649874a2732ea |
| Linux | Linux | 6.16 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64120?
How severe is CVE-2026-64120?
How do I fix CVE-2026-64120?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64115In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64116In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64117In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64118In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-64119In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6412Certificate policy and RFC 8446 compliance concerns regardin…4.3
- CVE-2026-64121In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64122In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64123In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64124In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64125In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64126In the Linux kernel, the following vulnerability has been re…7.3
Are you affected by CVE-2026-64120?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
