CVE-2026-63985: ethtool: eeprom: add more safeties to EEPROM Netlink fallback

Published Jul 19, 2026
·
Updated

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 (fallbacksetparams()) validates that offset < eepromlen, but does not check that offset + length stays within eepromlen. The ioctl equivalent (ethtoolgetanyeeprom() in ioctl.c) has always enforced both bounds:

if (eeprom.offset + eeprom.len > totallen) return -EINVAL;

This could lead to surprises in both drivers and device FW. Add the missing offset + length validation to fallbacksetparams(), mirroring the ioctl.

Similarly - ethtool core in general, and ethtoolgetanyeeprom() in particular tries to zero-init all buffers passed to the drivers to avoid any extra work of zeroing things out. eepromfallback() uses a plain kmalloc(), change it to zalloc.

Affected Software

12 affected components
Linux Linux kernel
Linux Linux kernel>=5.13<5.15.210
Linux Linux kernel>=5.16<6.1.176
Linux Linux kernel>=6.2<6.6.143
Linux Linux kernel>=6.7<6.12.93
Linux Linux kernel>=6.13<6.18.35
Linux Linux kernel>=6.19<7.0.12
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4
Linux Linux kernel=7.1-rc5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    In fallback_set_params(), validate that offset + length stays within eeprom_len; reject the request with -EINVAL when eeprom.offset + eeprom.len > total_len.

  2. Compensating control

    In the Netlink EEPROM fallback path, use zero-initializing allocation (zalloc) instead of plain kmalloc() for buffers passed to drivers.

Event History

Jul 19, 2026
CVE Published
via MITRE·02:56 PM
Data Sourced
via MITRE·02:56 PM
DescriptionSeverity
Data Sourced
via NVD·04:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-63985?

CVE-2026-63985 has been assigned a risk score of 15, indicating a critical severity level.

2

How do I fix CVE-2026-63985?

To fix CVE-2026-63985, update the Linux kernel to the latest patched version that resolves this vulnerability.

3

What systems are affected by CVE-2026-63985?

CVE-2026-63985 affects the Linux kernel, specifically in the ethtool functionality related to EEPROM handling.

4

What kind of attacks can exploit CVE-2026-63985?

Exploitation of CVE-2026-63985 could allow unauthorized access to sensitive EEPROM data or result in denial of service.

5

When was CVE-2026-63985 published?

CVE-2026-63985 was published on July 19, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203