Home / Security / Advisories / NTAP-20250509-0008

NTAP-20250509-0008 — CVE-2024-35890 Linux Kernel Vulnerability in NetApp Products

Published 2025-05-09 · Updated 2025-09-30 · Status: Final · Exploitation: Public · Severity: HIGH 7.8 · ONTAP affected: Yes

Official advisory: NTAP-20250509-0008 on security.netapp.com ↗. Affected versions, fixed releases, and workarounds live there — this page is a summary.

Product family: SolidFire / NetApp HCI · ONTAP | ONTAP-relevant | highest CVSS: 7.8

CVEs in this advisory

CVE-2024-35890 — HIGH · CVSS 7.8 · site index

What the CVE records say

CVE-2024-35890 — In the Linux kernel, the following vulnerability has been resolved: gro: fix ownership transfer If packets are GROed with fraglist they might be segmented later on and continue their journey in the stack. In skb_segment_list those skbs can be reused as-is. This is an issue as their destructor was removed in skb_gro_receive_list but not the reference to their socket, and then they can't be orphaned. Fix this by also removing the reference to the socket. For example this could be observed, kernel BUG at include/linux/skbuff.h:3131! (skb_orphan) RIP: 0010:ip6_rcv_core+0x11bc/0x19a0 Call Trace: ipv6_list_rcv+0x250/0x3f0 __netif_receive_skb_list_core+0x49d/0x8f0 netif_receive_skb_list_internal+0x634/0xd40 napi_complete_done+0x1d2/0x7d0 gro_cell_poll+0x118/0x1f0 A similar construction is found in skb_gro_receive, apply the same change there.

Impact

Successful exploitation of this vulnerability could lead to Denial of Service (DoS).

Affected products

NetApp HCI Baseboard Management Controller (BMC) - H300S/H500S/H700S/H410S
NetApp HCI Baseboard Management Controller (BMC) - H410C
NetApp HCI Compute Node (Bootstrap OS)
ONTAP tools for VMware vSphere 9

References

https://lore.kernel.org/linux-cve-announce/2024051948-CVE-2024-35890-beaa@gregkh/T/#u ↗

What to do

Check the affected products listed above against the official advisory's affected-versions table — that is where the exact ONTAP 9 release, ONTAP tool, or management product versions are named.
If affected and a fixed release exists, plan the upgrade — see the ONTAP upgrade runbook.
If exploitation is listed as "active", treat remediation as urgent and review exposure (management LIFs, ONTAP S3, SnapMirror endpoints).
Harden in parallel: security hardening baseline and ransomware protection on ONTAP.