CVE-2026-90102

HIGHCVSS 7.5/10

Last modified

CVE-2026-90102 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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.

Description

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.

Metrics

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= d67ae825a59d639e4d8b82413af84d854617a87e, < ffb100b0da0e217d5d63ce6fe092f9c29e59f7dd; >= d67ae825a59d639e4d8b82413af84d854617a87e, < 02e160922bc83cd25e346a028ed43cbdb0b57e1a; >= d67ae825a59d639e4d8b82413af84d854617a87e, < bc7aa9d8aff826031ffe25eba7f2f3acafcbf7a1; >= d67ae825a59d639e4d8b82413af84d854617a87e, < dd5bd091daa48c6ed8f9235ddf448aa288a0881f; >= d67ae825a59d639e4d8b82413af84d854617a87e, < f2994ba1263d9e88d3d9ae1d097c5cf811d4bfa5; >= d67ae825a59d639e4d8b82413af84d854617a87e, < 27f640cd92eebf5c2f64336be7ca24f4636390cb; >= d67ae825a59d639e4d8b82413af84d854617a87e, < bbc975cfb07a146843fde1126c43441e76177539; >= d67ae825a59d639e4d8b82413af84d854617a87e, < 13c23c5cb977f66390795437fd3837887ce1fd75
LinuxLinux4.0

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-90102?
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.
How severe is CVE-2026-90102?
CVE-2026-90102 has a CVSS score of 7.5/10 (HIGH severity).
How do I fix CVE-2026-90102?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-90102?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST