CVE-2026-63833: Linux kernel · Missing Authorization
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.1 High · fixed in f8d420949b335a4b51d06ab276beee6b8dfdc909 : patch Linux kernel soon.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in f8d420949b335a4b51d06ab276beee6b8dfdc909, e8852ae29868e449fdb47eebc28f35fb80741a5f, e574af95234afc3c725988bbc1fdeb46b9f386a4 +4
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
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]
References
- git.kernel.org/stable/c/e574af95234afc3c725988bbc1fdeb46b9f386a4 (opens in a new tab)
- git.kernel.org/stable/c/2c3cd6da4a14380ef79e34bd9dff7caf46687477 (opens in a new tab)
- git.kernel.org/stable/c/e8852ae29868e449fdb47eebc28f35fb80741a5f (opens in a new tab)
- git.kernel.org/stable/c/f8d420949b335a4b51d06ab276beee6b8dfdc909 (opens in a new tab)
- git.kernel.org/stable/c/5e658b9245a52d838ef93729a7bc07de8e19deb7 (opens in a new tab)
- git.kernel.org/stable/c/293a84fa40b3a1b3471c0545722724bc10973f76 (opens in a new tab)
- git.kernel.org/stable/c/5b08dccecf825cbf905f348bc6ccb497507e28e2 (opens in a new tab)