ZeroHour

CVE-2026-90048

mass

Heap buffer overflow in Linux kernel NTFS3 driver via crafted NTFS image

CVSS 3.1
9.8 critical
EPSS
Published
()
Modified
AI analysis

CVE-2026-90048 is a slab-out-of-bounds (heap) write in ni_create_attr_list() in the Linux kernel's NTFS3 filesystem driver: the attribute-list buffer is allocated at the fixed MFT record size, but a record packed with many minimal-size resident attributes generates an attribute list larger than that buffer, and the code advances its write cursor without any bounds check (the total size is only computed after the loop). It is triggered from a crafted, loop-mounted NTFS image - opening a file and adding an attribute (e.g., via setxattr) drives ntfs_set_ea() -> ni_insert_resident() -> ni_insert_attr() -> ni_ins_attr_ext() -> ni_create_attr_list(), with KASAN reporting a 4-byte write landing just past the end of a 1024-byte kmalloc-1k object. An attacker who can get a crafted image mounted gains kernel heap memory corruption, which typically enables local privilege escalation or a kernel crash (denial of service); despite the network-vector CVSS of 9.8, the practical trigger requires locally mounting untrusted NTFS media. Any Linux system with the NTFS3 driver enabled is affected, most notably desktops and multi-user servers where unprivileged users can mount removable drives or disk images. No public proof-of-concept, no CISA KEV listing, and no confirmed in-the-wild exploitation are known at this time.

What to do: Update affected systems to a kernel that includes the upstream fs/ntfs3 fix that sizes the attribute-list buffer from the actual attributes (fixed-release version numbers were not available in the data - track your distro's kernel security updates). Until patched, avoid mounting untrusted NTFS images or removable media, restrict unprivileged loop mounting and use of setxattr on NTFS volumes, and blacklist/unload the ntfs3 module if NTFS support is not needed. Check your kernel config for CONFIG_NTFS3_FS/ntfs3 to determine exposure.

Affected
Linux kernel (NTFS3 filesystem driver, fs/ntfs3)
Estimated exposure
mass>1,000,000 Linux systems plausibly affected (NTFS3 ships with mainline kernels and is built/enabled by most distributions) — Estimated from deployment patterns: the NTFS3 driver has been bundled with mainline Linux since kernel 5.15 and is typically built as a module by major distributions, so effectively any modern Linux desktop or server that can mount NTFS…

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: fix slab-out-of-bounds write in ni_create_attr_list() ni_create_attr_list() allocates a fixed buffer of al_aligned(record_size) (== record_size) bytes and then walks every attribute of the primary MFT record, writing one ATTR_LIST_ENTRY per attribute and advancing the cursor by le_size(name_len), with no check against the end of the buffer; the total size is only computed after the loop. A minimum-size resident attribute occupies SIZEOF_RESIDENT (0x18 = 24) bytes on disk, but an unnamed attribute expands to le_size(0) (0x20 = 32) bytes in the list. Because the number of attributes in a record is not bounded (mi_enum_attr() accepts arbitrarily many equal-type, nameless minimum-size attributes), a crafted record packed with such attributes produces a list larger than record_size and overflows the heap buffer. This is reachable from a crafted, loop-mounted NTFS image: opening the file and adding an attribute (e.g. via setxattr) drives ntfs_set_ea() -> ni_insert_resident() -> ni_insert_attr() -> ni_ins_attr_ext() -> ni_create_attr_list(). BUG: KASAN: slab-out-of-bounds in ni_create_attr_list+0xc48/0x1058 Write of size 4 at addr ffff000008984c00 by task setfattr/345 ni_create_attr_list+0xc48/0x1058 ni_ins_attr_ext+0x510/0x7c0 ni_insert_attr+0x3f8/0x70c ni_insert_resident+0xc8/0x3b0 ntfs_set_ea+0x66c/0xd28 ntfs_setxattr+0x4d8/0x5b0 __arm64_sys_setxattr+0xa4/0x124 Allocated by task 345: ni_create_attr_list+0x188/0x1058 The buggy address belongs to the cache kmalloc-1k of size 1024 (the write lands at object+1024). Size the buffer from the actual attributes instead of assuming a single record_size is always enough.

Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

In the news

No ingested article mentions this CVE yet.