NFSv4.0: Fix a use-after-free problem in the asynchronous open()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 24ac23ab88df5b21b5b2df8cde748bf99b289099 · < 229a30ed42bb87bcb044c5523fabd9e4f0e75648| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
NFSv4.0: Fix a use-after-free problem in the asynchronous open()
Yang Erkun reports that when two threads are opening files at the same time, and are forced to abort before a reply is seen, then the call to nfs_release_seqid() in nfs4_opendata_free() can result in a use-after-free of the pointer to the defunct rpc task of the other thread. The fix is to ensure that if the RPC call is aborted before the call to nfs_wait_on_sequence() is complete, then we must call nfs_release_seqid() in nfs4_open_release() before the rpc_task is freed.
From the CVE record · Linux
The Linux kernel’s NFSv4.0 asynchronous open path has a use-after-free bug. It can occur when two threads open files concurrently and both operations are aborted before a reply arrives; the input does not specify how an attacker could trigger this or whether authentication or user interaction is required.
Engineers running Linux kernels that use NFSv4.0 should check their versions; affected versions are not specified.