Skip to content
Threat Brief

← All advisories

CVE-2026-99363

Severity unknownNo known exploitationFix available

NFSD: Map flex file layout IDs through the request's user namespace

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 13% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: NFSD: Map flex file layout IDs through the request's user namespace nfsd4_ff_proc_layoutget() and nfsd4_ff_encode_layoutget() translate the file's owner and group with init_user_ns, but every other identity nfsd places on the wire goes through nfsd_user_namespace(). When the transport carries a credential from a non-initial user namespace, the flex file layout reports host-global IDs. The client copies those IDs into the AUTH_SYS credential it presents to the data server, and svcauth_unix_accept() resolves that credential in the transport's namespace, so data server I/O runs under an identity unrelated to the file's owner. Switching to the request's namespace introduces a second hazard. from_kuid() returns (uid_t)-1 when the target namespace has no mapping for the owner, and the IOMODE_READ arm adds one to that result to derive an identity for which the data server denies writes. The addition would wrap to zero, handing the client uid 0 instead of an identity distinct from the owner. Translate both IDs in nfsd4_ff_proc_layoutget(), which has the svc_rqst, and carry the wire values in struct pnfs_ff_layout. from_kuid_munged() substitutes overflowuid for an unmapped owner and thus never returns (uid_t)-1, so the increment cannot wrap to zero.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 9b9960a0ca4773e21c4b153ed355583946346b25 before 76bb89e8155fe29da36ecf0121e9e98afc0f418476bb89e8155fe29da36ecf0121e9e98afc0f4184CVE Program
LinuxLinuxfrom 9b9960a0ca4773e21c4b153ed355583946346b25 before c0dacde381e1311bba8074e660d41ecc57c3bd2bc0dacde381e1311bba8074e660d41ecc57c3bd2bCVE Program
LinuxLinuxfrom 9b9960a0ca4773e21c4b153ed355583946346b25 before f913d5d2130a584d1a027ffe3dfd88b6be2e0540f913d5d2130a584d1a027ffe3dfd88b6be2e0540CVE Program
LinuxLinuxfrom 9b9960a0ca4773e21c4b153ed355583946346b25 before e10bf0e125ebf6b9669b3158eda5fa67b56809d4e10bf0e125ebf6b9669b3158eda5fa67b56809d4CVE Program
LinuxLinux4.8Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.61 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 4.8Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references