ntfs: propagate reparse index insertion failure
- 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 7.2.7
- 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: ntfs: propagate reparse index insertion failure update_reparse_data() ignores the return value of set_reparse_index(). When index insertion fails, the code removes the just-written reparse data as cleanup but still returns 0, so symlink(2) (and WSL special file creation) reports success while no reparse data exists on disk. When there was no previous reparse data (oldsize == 0), the failure was likewise silently ignored. Propagate the error to the caller.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From fc053f05ca282a5e760b41f6560ac835c4e28037 · fixed in c62f446c63398dc7151f413069bf617032cf7a71; From fc053f05ca282a5e760b41f6560ac835c4e28037 · fixed in 9692b1b4fc00cf89628bc43f71729ab21f14f8d3
- Linux Linux
7.1
- KernelLinux
From 7.1.0 · fixed in 7.2.7