Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-63833ntfs3: reject direct userspace writes to reserved $LX* xattrs

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. [[email protected]: added an additional check for non privileged users]

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63833, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVDNVD · Analyzed3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS (exploitation in 30 days)
0.14% · top 96% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected be71b5cba2e6485e8959da7a9f9a44461a1bb074 – < e574af95234afc3c725988bbc1fdeb46b9f386a4
    • affected be71b5cba2e6485e8959da7a9f9a44461a1bb074 – < 2c3cd6da4a14380ef79e34bd9dff7caf46687477
    • affected be71b5cba2e6485e8959da7a9f9a44461a1bb074 – < e8852ae29868e449fdb47eebc28f35fb80741a5f
    • affected be71b5cba2e6485e8959da7a9f9a44461a1bb074 – < f8d420949b335a4b51d06ab276beee6b8dfdc909
    • affected be71b5cba2e6485e8959da7a9f9a44461a1bb074 – < 5e658b9245a52d838ef93729a7bc07de8e19deb7
    • affected be71b5cba2e6485e8959da7a9f9a44461a1bb074 – < 293a84fa40b3a1b3471c0545722724bc10973f76
    • affected be71b5cba2e6485e8959da7a9f9a44461a1bb074 – < 5b08dccecf825cbf905f348bc6ccb497507e28e2
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.211 – ≤ 5.15.*
    • unaffected 6.1.177 – ≤ 6.1.*
    • unaffected 6.6.144 – ≤ 6.6.*
    • unaffected 6.12.95 – ≤ 6.12.*
    • unaffected 6.18.38 – ≤ 6.18.*
    • unaffected 7.1.3 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63833 badge
[![CVE-2026-63833](https://cveledger.app/badge/CVE-2026-63833.svg)](https://cveledger.app/cve/CVE-2026-63833)

Record last updated .