ntfs3: reject direct userspace writes to reserved $LX* xattrs
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ be71b5cba2e6485e8959da7a9f9a44461a1bb074 · < 293a84fa40b3a1b3471c0545722724bc10973f76| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ntfs3: reject direct userspace writes to reserved $LX* xattrs
NTFS3 uses $LXUID, $LXGID, $LXMOD and $LXDEV as internal WSL permission metadata and reloads them into i_uid, i_gid and i_mode from ntfs_get_wsl_perm().
Because the empty-prefix xattr handler also lets file owners call setxattr() on these names directly, an unprivileged writer on a writable ntfs3 mount can plant root ownership and S_ISUID on their own file and gain euid 0 after inode reload.
Reject direct userspace writes to the reserved $LX* names. Internal ntfs3 metadata updates are unchanged because ntfs_save_wsl_perm() writes them via ntfs_set_ea() directly.
[almaz.alexandrovich@paragon-software.com: added an additional check for non privileged users]
From the CVE record · Linux
The Linux kernel’s ntfs3 driver allows file owners to write reserved $LX* permission metadata through setxattr(). An unprivileged user with write access on a writable ntfs3 mount can set root ownership and S_ISUID on their own file, then gain effective root privileges after the inode reloads.
Administrators running Linux systems with writable ntfs3 mounts should check their kernel versions; affected versions were not specified.