nfsd: fix nfsd4_deleg_getattr_conflict in presence of third party lease
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1b46a871e980e3daa16fd5e77539966492e8910a and Kernel 40927f3d0972bf86357a32a5749be71a551241b6.
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix nfsd4_deleg_getattr_conflict in presence of third party lease It is not safe to dereference fl->c.flc_owner without first confirming fl->fl_lmops is the expected manager. nfsd4_deleg_getattr_conflict() tests fl_lmops but largely ignores the result and assumes that flc_owner is an nfs4_delegation anyway. This is wrong. With this patch we restore the "!= &nfsd_lease_mng_ops" case to behave as it did before the change mentioned below. This is the same as the current code, but without any reference to a possible delegation.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.9, >=c5967721e1063648b0506481585ba7e2e49a075e <1b46a871e980e3daa16fd5e77539966492e8910a, >=c5967721e1063648b0506481585ba7e2e49a075e <40927f3d0972bf86357a32a5749be71a551241b6 | 1b46a871e980e3daa16fd5e77539966492e8910a, 40927f3d0972bf86357a32a5749be71a551241b6 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket