Home / Security / Advisories / NTAP-20261030-0012

NTAP-20261030-0012 — CVE-2026-52999 Linux Kernel Vulnerability in NetApp Products

Published 2026-10-30 · Updated 2026-10-30 · Status: Interim · Exploitation: Public · Severity: CRITICAL 9.1 · ONTAP affected: Yes

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

Product family: SolidFire / NetApp HCI · Active IQ Unified Manager · Brocade SAN firmware · Baseboard management controllers · NetApp Console / BlueXP · ONTAP · SnapCenter  |  ONTAP-relevant  |  highest CVSS: 9.1

CVEs in this advisory

What the CVE records say

CVE-2026-52999 — In the Linux kernel, the following vulnerability has been resolved: netfilter: nfnetlink_osf: fix out-of-bounds read on option matching In nf_osf_match(), the nf_osf_hdr_ctx structure is initialized once and passed by reference to nf_osf_match_one() for each fingerprint checked. During TCP option parsing, nf_osf_match_one() advances the shared ctx->optp pointer. If a fingerprint perfectly matches, the function returns early without restoring ctx->optp to its initial state. If the user has configured NF_OSF_LOGLEVEL_ALL, the loop continues to the next fingerprint. However, because ctx->optp was not restored, the next call to nf_osf_match_one() starts parsing from the end of the options buffer. This causes subsequent matches to read garbage data and fail immediately, making it impossible to log more than one match or logging incorrect matches. Instead of using a shared ctx->optp pointer, pass the context as a constant pointer and use a local pointer (optp) for TCP option traversal. This makes nf_osf_match_one() strictly stateless from the caller's perspective, ensuring every fingerprint check starts at the correct option offset.

Impact

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

Affected products

References

What to do

  1. 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.
  2. If affected and a fixed release exists, plan the upgrade — see the ONTAP upgrade runbook.
  3. If exploitation is listed as "active", treat remediation as urgent and review exposure (management LIFs, ONTAP S3, SnapMirror endpoints).
  4. Harden in parallel: security hardening baseline and ransomware protection on ONTAP.

Related reading

Browse all ONTAP CVEs → · Security hub