Home / Security / Advisories / NTAP-20261030-0005

NTAP-20261030-0005 — CVE-2026-31448 Linux Kernel Vulnerability in NetApp Products

Published 2026-10-30 · Updated 2026-10-30 · Status: Interim · Exploitation: Public · Severity: CRITICAL 9.4 · ONTAP affected: No — other NetApp product

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

Product family: Brocade SAN firmware · Baseboard management controllers · NetApp Console / BlueXP · SolidFire / NetApp HCI · SnapCenter | other NetApp product | highest CVSS: 9.4

CVEs in this advisory

CVE-2026-31448 — CRITICAL · CVSS 9.4 · site index

What the CVE records say

CVE-2026-31448 — In the Linux kernel, the following vulnerability has been resolved: ext4: avoid infinite loops caused by residual data On the mkdir/mknod path, when mapping logical blocks to physical blocks, if inserting a new extent into the extent tree fails (in this example, because the file system disabled the huge file feature when marking the inode as dirty), ext4_ext_map_blocks() only calls ext4_free_blocks() to reclaim the physical block without deleting the corresponding data in the extent tree. This causes subsequent mkdir operations to reference the previously reclaimed physical block number again, even though this physical block is already being used by the xattr block. Therefore, a situation arises where both the directory and xattr are using the same buffer head block in memory simultaneously. The above causes ext4_xattr_block_set() to enter an infinite loop about "inserted" and cannot release the inode lock, ultimately leading to the 143s blocking problem mentioned in [1]. If the metadata is corrupted, then trying to remove some extent space can do even more harm. Also in case EXT4_GET_BLOCKS_DELALLOC_RESERVE was passed, remove space wrongly update quota information. Jan Kara suggests distinguishing between two cases: 1) The error is ENOSPC or EDQUOT - in this case the filesystem is fully consistent and we must maintain its consistency including all the accounting. However these errors can happen only early before we've inserted the extent into the extent tree. So current code works correctly for this case. 2) Some other error - this means metadata is corrupted. We should strive to do as few modifications as possible to limit damage. So I'd just skip freeing of allocated blocks. [1] INFO: task syz.0.17:5995 blocked for more than 143 seconds. Call Trace: inode_lock_nested include/linux/fs.h:1073 [inline] __start_dirop fs/namei.c:2923 [inline] start_dirop fs/namei.c:2934 [inline]

Impact

Successful exploitation of this vulnerability could lead to disclosure of sensitive information, addition or modification of data or Denial of Service (DoS).

Affected products

Brocade Fabric Operating System Firmware
FAS/AFF Baseboard Management Controller (BMC) - A250/500f/C250
NetApp Console Agent OVA
NetApp HCI Baseboard Management Controller (BMC) - H610S
NetApp SolidFire & HCI Management Node
NetApp SolidFire & HCI Storage Node (Element Software)
SnapCenter Plug-in for VMware vSphere

References

https://lore.kernel.org/linux-cve-announce/2026042247-CVE-2026-31448-3c50@gregkh/ ↗

What to do

Compare your installed product and version against the affected list above and the official advisory's affected-versions table.
Apply the fixed release named in the official advisory, or the documented workaround if no fix ships yet.
Limit management-plane exposure (BMC/management interfaces, web UIs, SNMP) until patched.
Track follow-ups in the site CVE index and the security RSS feed.