SUNRPC: lock against ->sock changing during sysfs read
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
SUNRPC: lock against ->sock changing during sysfs read
->sock can be set to NULL asynchronously unless ->recv_mutex is held. So it is important to hold that mutex. Otherwise a sysfs read can trigger an oops. Commit 17f09d3f619a ("SUNRPC: Check if the xprt is connected before handling sysfs reads") appears to attempt to fix this problem, but it only narrows the race window.
From the CVE record · Linux
A race in Linux kernel SUNRPC can set a socket pointer to NULL during a sysfs read. A local sysfs read can then trigger a kernel oops; the input does not specify authentication requirements beyond access to that read.
Engineers running Linux kernels with SUNRPC should check whether their kernel includes the fix; affected versions are not specified.