PT-2026-151544

CVE-2026-99363

·

Published

2026-11-19

·

Updated

2026-11-19

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

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.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾