fs: ntfs3: fix infinite loop triggered by zero-sized ATTR_LIST
- 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.202, 6.1.165, 6.6.128, 6.12.75, 6.18.16, 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
In the Linux kernel, the following vulnerability has been resolved: fs: ntfs3: fix infinite loop triggered by zero-sized ATTR_LIST We found an infinite loop bug in the ntfs3 file system that can lead to a Denial-of-Service (DoS) condition. A malformed NTFS image can cause an infinite loop when an ATTR_LIST attribute indicates a zero data size while the driver allocates memory for it. When ntfs_load_attr_list() processes a resident ATTR_LIST with data_size set to zero, it still allocates memory because of al_aligned(0). This creates an inconsistent state where ni->attr_list.size is zero, but ni->attr_list.le is non-null. This causes ni_enum_attr_ex to incorrectly assume that no attribute list exists and enumerates only the primary MFT record. When it finds ATTR_LIST, the code reloads it and restarts the enumeration, repeating indefinitely. The mount operation never completes, hanging the kernel thread. This patch adds validation to ensure that data_size is non-zero before memory allocation. When a zero-sized ATTR_LIST is detected, the function returns -EINVAL, preventing a DoS vulnerability.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From be71b5cba2e6485e8959da7a9f9a44461a1bb074 · fixed in 9267d99fade76d44d4a133599524031fe684156e; From be71b5cba2e6485e8959da7a9f9a44461a1bb074 · fixed in 976e6a7c51fabf150478decbe8ef5d9a26039b7c; From be71b5cba2e6485e8959da7a9f9a44461a1bb074 · fixed in 8d8c70b57dbeda3eb165c0940b97e85373ca9354; From be71b5cba2e6485e8959da7a9f9a44461a1bb074 · fixed in 7ef219656febf5ae06ae56b1fce47ebd05f92b68; From be71b5cba2e6485e8959da7a9f9a44461a1bb074 · fixed in 9779a6eaaabdf47aa57910d352b398ad742e6a5f; From be71b5cba2e6485e8959da7a9f9a44461a1bb074 · fixed in fd508939dbca5eceefb2d0c2564beb15469572f2; From be71b5cba2e6485e8959da7a9f9a44461a1bb074 · fixed in 06909b2549d631a47fcda249d34be26f7ca1711d
- Linux Linux
5.15
- KernelLinux
From 5.15.0 · fixed in 5.15.202; From 5.16.0 · fixed in 6.1.165; From 6.2.0 · fixed in 6.6.128; From 6.7.0 · fixed in 6.12.75; From 6.13.0 · fixed in 6.18.16; From 6.19.0 · fixed in 6.19.6
References 7
git.kernel.org
- stable/c/9267d99fade76d44d4a133599524031fe684156e
- stable/c/976e6a7c51fabf150478decbe8ef5d9a26039b7c
- stable/c/8d8c70b57dbeda3eb165c0940b97e85373ca9354
- stable/c/7ef219656febf5ae06ae56b1fce47ebd05f92b68
- stable/c/9779a6eaaabdf47aa57910d352b398ad742e6a5f
- stable/c/fd508939dbca5eceefb2d0c2564beb15469572f2
- stable/c/06909b2549d631a47fcda249d34be26f7ca1711d