CVE-2026-63833 json
ntfs3: reject direct userspace writes to reserved $LX* xattrs
published 3mo ago modified 20d ago also EUVD-2026-45499
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
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]
Patch / fix
- Linux Linux 5.15.211, 6.1.177, 6.6.144, 6.12.95, 6.18.38, 7.1.3, 7.2
- linux Debian 12 6.1.177-1
- linux Debian 13 6.12.95-1
- linux Debian 14 7.1.3-1
debian advisories DEBIAN-CVE-2026-63833
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-31.31
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1012.12
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
ubuntu advisories UBUNTU-CVE-2026-63833
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.1.4-1.1
opensuse advisories openSUSE-SU-2026:11339-1
- git.kernel.org/stable/c/e574af95234afc3c725988bbc1fdeb46b9f386a4 commit
- git.kernel.org/stable/c/2c3cd6da4a14380ef79e34bd9dff7caf46687477 commit
- git.kernel.org/stable/c/e8852ae29868e449fdb47eebc28f35fb80741a5f commit
- git.kernel.org/stable/c/f8d420949b335a4b51d06ab276beee6b8dfdc909 commit
- git.kernel.org/stable/c/5e658b9245a52d838ef93729a7bc07de8e19deb7 commit
- git.kernel.org/stable/c/293a84fa40b3a1b3471c0545722724bc10973f76 commit
- git.kernel.org/stable/c/5b08dccecf825cbf905f348bc6ccb497507e28e2 commit
Is CVE-2026-63833 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-63833 updated cvss 7.1
kernel: ntfs3: reject direct userspace writes to reserved $LX* xattrs
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 26d ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
-
git.kernel.org
/stable/c/e574af95234afc3c725988bbc1fdeb46b9f386a4
patch
-
git.kernel.org
/stable/c/2c3cd6da4a14380ef79e34bd9dff7caf46687477
patch
-
git.kernel.org
/stable/c/e8852ae29868e449fdb47eebc28f35fb80741a5f
patch
-
git.kernel.org
/stable/c/f8d420949b335a4b51d06ab276beee6b8dfdc909
patch
-
git.kernel.org
/stable/c/5e658b9245a52d838ef93729a7bc07de8e19deb7
patch
-
git.kernel.org
/stable/c/293a84fa40b3a1b3471c0545722724bc10973f76
patch
-
git.kernel.org
/stable/c/5b08dccecf825cbf905f348bc6ccb497507e28e2
patch
Sources
- CVE List CVE-2026-63833
- NVD CVE-2026-63833
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.