CVE-2026-63833
What it is
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]
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.1 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-862 · Missing authorization
- Record status
- Analyzed
Affected
- Linux Kernel < 5.15.211
- Linux Kernel < 6.1.177
- Linux Kernel < 6.6.144
- Linux Kernel < 6.12.95
- Linux Kernel < 6.18.38
- Linux Kernel < 7.1.3
Attack profile CVSS 3.1 · 7.1
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-63833.md and follow it. Check whether this project is affected by CVE-2026-63833. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/293a84fa40b3a1b3471c0545722724bc10973f76
- https://git.kernel.org/stable/c/2c3cd6da4a14380ef79e34bd9dff7caf46687477
- https://git.kernel.org/stable/c/5b08dccecf825cbf905f348bc6ccb497507e28e2
- https://git.kernel.org/stable/c/5e658b9245a52d838ef93729a7bc07de8e19deb7
- https://git.kernel.org/stable/c/e574af95234afc3c725988bbc1fdeb46b9f386a4
- https://git.kernel.org/stable/c/e8852ae29868e449fdb47eebc28f35fb80741a5f
- https://git.kernel.org/stable/c/f8d420949b335a4b51d06ab276beee6b8dfdc909
References
- https://git.kernel.org/stable/c/293a84fa40b3a1b3471c0545722724bc10973f76
- https://git.kernel.org/stable/c/2c3cd6da4a14380ef79e34bd9dff7caf46687477
- https://git.kernel.org/stable/c/5b08dccecf825cbf905f348bc6ccb497507e28e2
- https://git.kernel.org/stable/c/5e658b9245a52d838ef93729a7bc07de8e19deb7
- https://git.kernel.org/stable/c/e574af95234afc3c725988bbc1fdeb46b9f386a4
- https://git.kernel.org/stable/c/e8852ae29868e449fdb47eebc28f35fb80741a5f
- https://git.kernel.org/stable/c/f8d420949b335a4b51d06ab276beee6b8dfdc909