nfsd: hold cl_lock in client_has_openowners()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel a596d1979fcb4e5011d3d48ac4d927f81c9c9cab, Kernel 202b7a6c462daa55a9f4b01f0a25eca2b8d5f2e3, Kernel 5336899b5491eaa2ac22c2925d87daab2b140eb3 and 4 more.
In the Linux kernel, the following vulnerability has been resolved: nfsd: hold cl_lock in client_has_openowners() client_has_openowners() walks clp->cl_openowners and reads so_stateids without clp->cl_lock. nfs4_put_stateowner() unhashes that openowner under cl_lock and then frees it, so a concurrent EXCHANGE_ID with mismatched creds can use-after-free the nfs4_openowner. BUG: KASAN: slab-use-after-free in client_has_state+0x10a/0x140 fs/nfsd/nfs4state.c:3718 client_has_openowners() nfsd4_exchange_id nfsd4_proc_compound nfsd_dispatch svc_process Take clp->cl_lock while client_has_openowners() walks the openowner list.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=4eaea13425078272895ec37814c6878d78b8db9f <a596d1979fcb4e5011d3d48ac4d927f81c9c9cab, >=4eaea13425078272895ec37814c6878d78b8db9f <202b7a6c462daa55a9f4b01f0a25eca2b8d5f2e3, >=4eaea13425078272895ec37814c6878d78b8db9f <5336899b5491eaa2ac22c2925d87daab2b140eb3, >=4eaea13425078272895ec37814c6878d78b8db9f <540649cb8543472f6edfe9ae8b42c04aa3bd67e9, =4.4 | a596d1979fcb4e5011d3d48ac4d927f81c9c9cab, 202b7a6c462daa55a9f4b01f0a25eca2b8d5f2e3, 5336899b5491eaa2ac22c2925d87daab2b140eb3, 540649cb8543472f6edfe9ae8b42c04aa3bd67e9 |
| linux-kernel: Kernel | >=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=4.4.0 <6.12.117 | 6.18.61, 7.3.2, 6.12.117 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket