CVE-2026-90102

published 17 Sep 2026 · updated 12 Nov 2026

NFSv4/pnfs: key the data server cache on the NFS version

7.5HighCVSS 7.5EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 02e160922bc83cd25e346a028ed43cbdb0b57e1a, Kernel 13c23c5cb977f66390795437fd3837887ce1fd75, Kernel 27f640cd92eebf5c2f64336be7ca24f4636390cb and 5 more.

In the Linux kernel, the following vulnerability has been resolved: NFSv4/pnfs: key the data server cache on the NFS version nfs4_pnfs_ds_add() keys the per-net data server cache on the multipath address set alone, and struct nfs4_pnfs_ds records no version. That suffices for the files layout driver, which always connects with version 4, but flexfiles takes its version tuple from GETDEVICEINFO per device, and one address can legitimately serve both NFSv3 and NFSv4. Two deviceids on one address with different ds_versions[0].version therefore share a single nfs4_pnfs_ds, and whichever mirror connects first pins ds_clp to its own version. The other one is handed that client anyway, so it selects rpc_call_ops for a version the connection does not speak, and the mismatched sequence-slot handling dereferences NULL. Add the version to the cache key so the two cannot alias, giving each version its own nfs4_pnfs_ds and connection while both mirrors stay usable. Only the major version is compared, since that is what selects rpc_call_ops and rpc_ops; v4.0 and v4.1 keep sharing a client. The files layout driver passes the 4 it already hardcodes at connect time.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.0, >=d67ae825a59d639e4d8b82413af84d854617a87e <02e160922bc83cd25e346a028ed43cbdb0b57e1a, >=d67ae825a59d639e4d8b82413af84d854617a87e <13c23c5cb977f66390795437fd3837887ce1fd75, >=d67ae825a59d639e4d8b82413af84d854617a87e <27f640cd92eebf5c2f64336be7ca24f4636390cb, >=d67ae825a59d639e4d8b82413af84d854617a87e <bbc975cfb07a146843fde1126c43441e76177539, >=d67ae825a59d639e4d8b82413af84d854617a87e <bc7aa9d8aff826031ffe25eba7f2f3acafcbf7a1, >=d67ae825a59d639e4d8b82413af84d854617a87e <dd5bd091daa48c6ed8f9235ddf448aa288a0881f, >=d67ae825a59d639e4d8b82413af84d854617a87e <f2994ba1263d9e88d3d9ae1d097c5cf811d4bfa5, >=d67ae825a59d639e4d8b82413af84d854617a87e <ffb100b0da0e217d5d63ce6fe092f9c29e59f7dd02e160922bc83cd25e346a028ed43cbdb0b57e1a, 13c23c5cb977f66390795437fd3837887ce1fd75, 27f640cd92eebf5c2f64336be7ca24f4636390cb, bbc975cfb07a146843fde1126c43441e76177539, bc7aa9d8aff826031ffe25eba7f2f3acafcbf7a1, dd5bd091daa48c6ed8f9235ddf448aa288a0881f, f2994ba1263d9e88d3d9ae1d097c5cf811d4bfa5, ffb100b0da0e217d5d63ce6fe092f9c29e59f7dd

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-90102 severity on Zeptric[![CVE-2026-90102](https://zeptric.io/badge/cve/CVE-2026-90102.svg)](https://zeptric.io/cve/CVE-2026-90102)