CVE-2026-89779
- Published16 Sept 2026
Description
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: validate ef->size covers the record's name and value When an EA record has a non-zero ef->size, ntfs_read_ea() only checks that the record fits in the remaining buffer (ea_size > bytes), not that ef->size is large enough to hold the record's own name_len + 1 + elength. A crafted image can pass validation with, e.g., ef->size = 24 but elength = 0xffff. ntfs_get_ea() then trusts elength and copies it out of the undersized record, reading past the kmalloc(info->size) allocation and leaking heap memory to userspace via getxattr(): BUG: KASAN: slab-out-of-bounds in ntfs_get_ea (fs/ntfs3/xattr.c:302) Read of size 65535 at addr ffff888100794550 by task exploit __asan_memcpy (mm/kasan/shadow.c:105) ntfs_get_ea (fs/ntfs3/xattr.c:302) ntfs_getxattr (fs/ntfs3/xattr.c:848) __vfs_getxattr (fs/xattr.c:441) vfs_getxattr (fs/xattr.c:474) do_getxattr (fs/xattr.c:800) path_getxattrat (fs/xattr.c:868) do_syscall_64 (arch/x86/entry/syscall_64.c:94) The buggy address is located 80 bytes inside of allocated 84-byte region in cache kmalloc-96 Compute the size the record needs and require ef->size to cover it.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/077df8464cf24f8ffc82fb6efec2ae600686e699
- https://git.kernel.org/stable/c/28a924c7e67e6d71abeb04860b61166fecb027fc
- https://git.kernel.org/stable/c/aab1880058ac767d3ea9388a9a7221c776c22c44
- https://git.kernel.org/stable/c/b27e68ad818a4ca2cef8f35f97e75d756714c818
- https://git.kernel.org/stable/c/c22f91d82cb9a29d22bdffdce6c803467984ad0c
- https://git.kernel.org/stable/c/c8a109c9e23a2c7fd548473dde728b2cb8188146
- https://git.kernel.org/stable/c/d585ed08308909c7e6fefb4e8a258aeb29b19ff9
Frequently asked
Is CVE-2026-89779 being actively exploited?
CVE-2026-89779 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.21%.
How severe is CVE-2026-89779?
CVE-2026-89779 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.21% probability of exploitation.
How do I fix CVE-2026-89779?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-89779 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.