NFSv4/pnfs: key the data server cache on the NFS version
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.69% (FIRST EPSS); higher than 52% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 02e160922bc83cd25e346a028ed43cbdb0b57e1a, 13c23c5cb977f66390795437fd3837887ce1fd75, 27f640cd92eebf5c2f64336be7ca24f4636390cb; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 02e160922bc83cd25e346a028ed43cbdb0b57e1a, 13c23c5cb977f66390795437fd3837887ce1fd75, 27f640cd92eebf5c2f64336be7ca24f4636390cb; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- EPSS
- 0.6% · 52th percentile
- CWE
- —
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.0affected
- d67ae825a59d639e4d8b82413af84d854617a87e and later · before ffb100b0da0e217d5d63ce6fe092f9c29e59f7ddaffected · git
- d67ae825a59d639e4d8b82413af84d854617a87e and later · before 02e160922bc83cd25e346a028ed43cbdb0b57e1aaffected · git
- d67ae825a59d639e4d8b82413af84d854617a87e and later · before bc7aa9d8aff826031ffe25eba7f2f3acafcbf7a1affected · git
- d67ae825a59d639e4d8b82413af84d854617a87e and later · before dd5bd091daa48c6ed8f9235ddf448aa288a0881faffected · git
- d67ae825a59d639e4d8b82413af84d854617a87e and later · before f2994ba1263d9e88d3d9ae1d097c5cf811d4bfa5affected · git
- d67ae825a59d639e4d8b82413af84d854617a87e and later · before 27f640cd92eebf5c2f64336be7ca24f4636390cbaffected · git
- d67ae825a59d639e4d8b82413af84d854617a87e and later · before bbc975cfb07a146843fde1126c43441e76177539affected · git
- d67ae825a59d639e4d8b82413af84d854617a87e and later · before 13c23c5cb977f66390795437fd3837887ce1fd75affected · git
- before 4.0not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90100Sep 17, 2026 · ptp: netc: fix period truncation and potential divide-by-zero in PEROUT0Monitor
- ← EarlierCVE-2026-90101Sep 17, 2026 · bnxt_en: Fix call to hardware monitoring event handler0Monitor
- Later →CVE-2026-90103Sep 17, 2026 · NFSv4.2: fix LAYOUTSTATS send buffer exhaustion30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 02e160922bc83cd25e346a028ed43cbdb0b57e1a | Vendor (CNA) |
| Linux Linux | 13c23c5cb977f66390795437fd3837887ce1fd75 | Vendor (CNA) |
| Linux Linux | 27f640cd92eebf5c2f64336be7ca24f4636390cb | Vendor (CNA) |
| Linux Linux | bbc975cfb07a146843fde1126c43441e76177539 | Vendor (CNA) |
| Linux Linux | bc7aa9d8aff826031ffe25eba7f2f3acafcbf7a1 | Vendor (CNA) |
| Linux Linux | dd5bd091daa48c6ed8f9235ddf448aa288a0881f | Vendor (CNA) |
| Linux Linux | f2994ba1263d9e88d3d9ae1d097c5cf811d4bfa5 | Vendor (CNA) |
| Linux Linux | ffb100b0da0e217d5d63ce6fe092f9c29e59f7dd | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/13c23c5cb977f66390795437fd3837887ce1fd75
- git.kernel.org/stable/c/27f640cd92eebf5c2f64336be7ca24f4636390cb
- git.kernel.org/stable/c/bbc975cfb07a146843fde1126c43441e76177539
- git.kernel.org/stable/c/bc7aa9d8aff826031ffe25eba7f2f3acafcbf7a1
- git.kernel.org/stable/c/dd5bd091daa48c6ed8f9235ddf448aa288a0881f
- git.kernel.org/stable/c/f2994ba1263d9e88d3d9ae1d097c5cf811d4bfa5
- git.kernel.org/stable/c/ffb100b0da0e217d5d63ce6fe092f9c29e59f7dd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.