Skip to main content
VulnerabilityPublished Updated

CVE-2026-63833: Linux kernel · Missing Authorization

Affects Linux kernelSource CVE Database V5

0

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

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ be71b5cba2e6485e8959da7a9f9a44461a1bb074, < f8d420949b335a4b51d06ab276beee6b8dfdc909
Fixed in
  • f8d420949b335a4b51d06ab276beee6b8dfdc909
LinuxLinuxAffected
  • ≥ be71b5cba2e6485e8959da7a9f9a44461a1bb074, < e8852ae29868e449fdb47eebc28f35fb80741a5f
Fixed in
  • e8852ae29868e449fdb47eebc28f35fb80741a5f
LinuxLinuxAffected
  • ≥ be71b5cba2e6485e8959da7a9f9a44461a1bb074, < e574af95234afc3c725988bbc1fdeb46b9f386a4
Fixed in
  • e574af95234afc3c725988bbc1fdeb46b9f386a4
LinuxLinuxAffected
  • ≥ be71b5cba2e6485e8959da7a9f9a44461a1bb074, < 293a84fa40b3a1b3471c0545722724bc10973f76
Fixed in
  • 293a84fa40b3a1b3471c0545722724bc10973f76
LinuxLinuxAffected
  • ≥ be71b5cba2e6485e8959da7a9f9a44461a1bb074, < 5e658b9245a52d838ef93729a7bc07de8e19deb7
Fixed in
  • 5e658b9245a52d838ef93729a7bc07de8e19deb7
LinuxLinuxAffected
  • ≥ be71b5cba2e6485e8959da7a9f9a44461a1bb074, < 5b08dccecf825cbf905f348bc6ccb497507e28e2
Fixed in
  • 5b08dccecf825cbf905f348bc6ccb497507e28e2

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

Community reviews

Loading reviews…