fs/ntfs3: validate ef->size covers the record's name and value
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Linux kernel's NTFS3 filesystem driver (fs/ntfs3), which handles extended attributes, is affected. A specially crafted NTFS disk image can cause extended attribute reads to access memory beyond the allocated buffer, potentially exposing kernel heap contents to a local user via the getxattr() system call.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 333feb7ba84f69f9b423422417aaac54fd9e7c84 · fixed in b27e68ad818a4ca2cef8f35f97e75d756714c818; From 000a9a72efa4a9df289bab9c9e8ba1639c72e0d6 · fixed in 28a924c7e67e6d71abeb04860b61166fecb027fc; From 0e8235d28f3a0e9eda9f02ff67ee566d5f42b66b · fixed in d585ed08308909c7e6fefb4e8a258aeb29b19ff9; From 0e8235d28f3a0e9eda9f02ff67ee566d5f42b66b · fixed in 077df8464cf24f8ffc82fb6efec2ae600686e699; From 0e8235d28f3a0e9eda9f02ff67ee566d5f42b66b · fixed in aab1880058ac767d3ea9388a9a7221c776c22c44; From 0e8235d28f3a0e9eda9f02ff67ee566d5f42b66b · fixed in c8a109c9e23a2c7fd548473dde728b2cb8188146; From 0e8235d28f3a0e9eda9f02ff67ee566d5f42b66b · fixed in c22f91d82cb9a29d22bdffdce6c803467984ad0c; From 5.15.121 · fixed in 5.15.221; From 6.1.40 · fixed in 6.1.188
- Linux Linux
6.2
- KernelLinux
fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; fixed in 6.12.110; From 6.7.0 · fixed in 6.18.52; From 6.13.0 · fixed in 7.2.6
References 7
git.kernel.org
- stable/c/b27e68ad818a4ca2cef8f35f97e75d756714c818
- stable/c/28a924c7e67e6d71abeb04860b61166fecb027fc
- stable/c/d585ed08308909c7e6fefb4e8a258aeb29b19ff9
- stable/c/077df8464cf24f8ffc82fb6efec2ae600686e699
- stable/c/aab1880058ac767d3ea9388a9a7221c776c22c44
- stable/c/c8a109c9e23a2c7fd548473dde728b2cb8188146
- stable/c/c22f91d82cb9a29d22bdffdce6c803467984ad0c