PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-63985 Linux CVE debrief

The Linux kernel was vulnerable to an issue in the ethtool EEPROM Netlink fallback path. The fallback_set_params() function did not validate that the offset + length stayed within the eeprom_len, which could lead to surprises in both drivers and device FW. This has been resolved by adding the missing offset + length validation to fallback_set_params(), mirroring the ioctl. The issue could lead to unexpected behavior in drivers and device firmware. The ioctl equivalent, ethtool_get_any_eeprom(), had always enforced both bounds. The eeprom_fallback() function was modified to use kzalloc() instead of kmalloc() to ensure buffer zero-initialization, consistent with ethtool core practices.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-19
Original CVE updated
2026-07-30
Advisory published
2026-07-19
Advisory updated
2026-07-30

Who should care

Linux kernel users and administrators should be aware of this vulnerability and ensure their systems are updated with the latest kernel patches. They should review system configurations for ethtool EEPROM reads and monitor system logs for unusual ethtool activity. Additionally, they should verify the affected scope and severity with the official advisory and plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Technical summary

In the Linux kernel, the ethtool EEPROM Netlink fallback path did not properly validate the offset and length of EEPROM reads. Specifically, the fallback_set_params() function checked that offset < eeprom_len but did not verify that offset + length stayed within eeprom_len. This oversight could lead to unexpected behavior in drivers and device firmware. The ioctl equivalent, ethtool_get_any_eeprom(), had always enforced both bounds. The issue has been addressed by adding the necessary validation to fallback_set_params(), aligning it with the ioctl behavior. Additionally, the eeprom_fallback() function was modified to use kzalloc() instead of kmalloc() to ensure buffer zero-initialization, consistent with ethtool core practices.

Defensive priority

Medium

Recommended defensive actions

  • Update Linux kernel to the latest version
  • Verify system configurations for ethtool EEPROM reads
  • Monitor system logs for unusual ethtool activity
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record was published on 2026-07-19T16:17:17.723Z and has not been modified since then. The NVD entry is currently Received. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the official advisory. The Linux kernel was vulnerable to an issue in the ethtool EEPROM Netlink fallback path, which did not properly validate the offset and length of EEPROM reads. This oversight could lead to unexpected behavior in drivers and device firmware. The issue has been addressed by adding the necessary validation to fallback_set_params(), aligning it with the ioctl behavior.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-63985 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-63985

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-63985 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-63985

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/0e182689831277faf2ef683573a60474c208f690

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/4fe1bc4b3603f621240d5b401742f302190db769

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/65674d2489a12b8efd2ca0effb3de1d12224b596

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/67cfdd9210b99f260b3e0afeb9525e0acc7be31e

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/6ed7ebe22e9c3e3e946b6973c1ce43d3c38aeac1

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/d81376053a00865c70b8d8506a1cb93f2943d413

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/fd0de51c54fa8474a0ddeedd71c65ad09fada390

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.