NFS: Fix use-after-free in nfs4_init_client()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8dcbec6d20eb881ba368d0aebc3a8a678aebb1da · < 476bdb04c501fc64bf3b8464ffddefc8dbe01577| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
NFS: Fix use-after-free in nfs4_init_client()
KASAN reports a use-after-free when attempting to mount two different exports through two different NICs that belong to the same server.
Olga was able to hit this with kernels starting somewhere between 5.7 and 5.10, but I traced the patch that introduced the clear_bit() call to 4.13. So something must have changed in the refcounting of the clp pointer to make this call to nfs_put_client() the very last one.
From the CVE record · Linux
The Linux kernel’s nfs4_init_client() has a use-after-free vulnerability. It can be triggered when mounting two different exports through different network interfaces connected to the same server; the input does not specify what access is needed to perform the mounts.
Engineers running Linux kernels should check their NFS configurations, particularly kernels from 5.7 through 5.10, where the issue was observed.