In the Linux kernel, the following vulnerability has been resolved: ethtool: eeprom: add more safeties to EEPROM Netlink fallback The Netlink… (CVE-2026-63985)
In the Linux kernel, the following vulnerability has been resolved: ethtool: eeprom: add more safeties to EEPROM Netlink fallback The Netlink fallback path for reading module EEPROM (fallback_set_params()) validates that offset < eeprom_len, but does not check that offset + length stays within eeprom_len. The ioctl equivalent (ethtool_get_any_eeprom() in ioctl.c) has always enforced both bounds: if (eeprom.offset + eeprom.len > total_len) return -EINVAL; This could lead to surprises in both drivers and device FW. Add the missing offset + length validation to fallback_set_params(), mirroring the ioctl. Similarly - ethtool core in general, and ethtool_get_any_eeprom() in particular tries to zero-init all buffers passed to the drivers to avoid any extra work of zeroing things out. eeprom_fallback() uses a plain kmalloc(), change it to zalloc.
AI Analysis
Technical Summary
The Linux kernel's ethtool utility had a vulnerability in its EEPROM Netlink fallback function (fallback_set_params()) where it only checked that the offset was less than the EEPROM length but did not verify that offset plus length remained within the EEPROM length. This incomplete bounds checking could lead to out-of-bounds reads or other unexpected behavior affecting drivers and device firmware. The ioctl equivalent function already enforced proper bounds checking. The fix added the missing offset plus length validation to the fallback path to mirror the ioctl behavior. Additionally, the fallback buffer allocation was changed from kmalloc() to zero-initialized allocation (zalloc) to avoid uninitialized data issues.
Potential Impact
Improper bounds checking in the EEPROM reading fallback path could lead to out-of-bounds memory access, potentially causing unexpected behavior in device drivers and firmware. While no known exploits are reported, this could affect system stability or security depending on the driver and device firmware involved.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to add the missing offset plus length validation in the EEPROM Netlink fallback path and to zero-initialize buffers properly. Users should update to a Linux kernel version that includes this fix. Since this is a kernel vulnerability, applying the official kernel update from the vendor or distribution is the recommended remediation. Patch status is not explicitly confirmed here; check the vendor advisory or Linux kernel release notes for the exact fixed version.
In the Linux kernel, the following vulnerability has been resolved: ethtool: eeprom: add more safeties to EEPROM Netlink fallback The Netlink… (CVE-2026-63985)
Description
In the Linux kernel, the following vulnerability has been resolved: ethtool: eeprom: add more safeties to EEPROM Netlink fallback The Netlink fallback path for reading module EEPROM (fallback_set_params()) validates that offset < eeprom_len, but does not check that offset + length stays within eeprom_len. The ioctl equivalent (ethtool_get_any_eeprom() in ioctl.c) has always enforced both bounds: if (eeprom.offset + eeprom.len > total_len) return -EINVAL; This could lead to surprises in both drivers and device FW. Add the missing offset + length validation to fallback_set_params(), mirroring the ioctl. Similarly - ethtool core in general, and ethtool_get_any_eeprom() in particular tries to zero-init all buffers passed to the drivers to avoid any extra work of zeroing things out. eeprom_fallback() uses a plain kmalloc(), change it to zalloc.
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's ethtool utility had a vulnerability in its EEPROM Netlink fallback function (fallback_set_params()) where it only checked that the offset was less than the EEPROM length but did not verify that offset plus length remained within the EEPROM length. This incomplete bounds checking could lead to out-of-bounds reads or other unexpected behavior affecting drivers and device firmware. The ioctl equivalent function already enforced proper bounds checking. The fix added the missing offset plus length validation to the fallback path to mirror the ioctl behavior. Additionally, the fallback buffer allocation was changed from kmalloc() to zero-initialized allocation (zalloc) to avoid uninitialized data issues.
Potential Impact
Improper bounds checking in the EEPROM reading fallback path could lead to out-of-bounds memory access, potentially causing unexpected behavior in device drivers and firmware. While no known exploits are reported, this could affect system stability or security depending on the driver and device firmware involved.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to add the missing offset plus length validation in the EEPROM Netlink fallback path and to zero-initialize buffers properly. Users should update to a Linux kernel version that includes this fix. Since this is a kernel vulnerability, applying the official kernel update from the vendor or distribution is the recommended remediation. Patch status is not explicitly confirmed here; check the vendor advisory or Linux kernel release notes for the exact fixed version.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-69m3-xqhx-p784
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63985"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27aa2a4a8d598912e238
Added to database: 07/19/2026, 19:38:18 UTC
Last enriched: 07/19/2026, 20:02:41 UTC
Last updated: 07/20/2026, 21:51:33 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.