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]
| Vendor | Product | Versions |
|---|---|---|
| linux | linux kernel | be71b5cba2e6485e8959da7a9f9a44461a1bb074, be71b5cba2e6485e8959da7a9f9a44461a1bb074, be71b5cba2e6485e8959da7a9f9a44461a1bb074, be71b5cba2e6485e8959da7a9f9a44461a1bb074, be71b5cba2e6485e8959da7a9f9a44461a1bb074, be71b5cba2e6485e8959da7a9f9a44461a1bb074, be71b5cba2e6485e8959da7a9f9a44461a1bb074, 5.15 |
Downstream vendors/products affected by this vulnerability
| Vendor | Product | Source | Confidence |
|---|---|---|---|
| open source | open source linux kernel | cert_advisory | 90% |
Updated severity from HIGH to CRITICAL and assigned CVSS estimate of 9.0 based on article's assessment as 'very critical'.
Updated severity from NONE to HIGH based on the privilege escalation impact (unprivileged user gaining euid 0)
Initial creation
