CVE-2026-63833
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. [[email protected]: added an additional check for non privileged users]
Affected versions
Fixed in
5.15.211,
6.1.177,
6.6.144,
6.12.95,
6.18.38,
7.1.3,
7.2-rc1
and their respective stable series.
References
7 totalFrequently asked questions
-
What is CVE-2026-63833?
CVE-2026-63833 is a unscored severity Linux kernel vulnerability . CVE-2026-63833 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-63833?
Yes — CVE-2026-63833 has been patched. Fixed versions include 5.15.211, 6.1.177, 6.6.144 and others.
-
Is CVE-2026-63833 actively exploited?
No — CVE-2026-63833 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.