NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 7e65ea887d0c0997f3053acd91a027af45e71c5b · < b090d110e66636bca473fd8b98d5c97b555a965a| No fix yet |
| Linux Linux |
| No fix yet |
In the Linux kernel, the following vulnerability has been resolved:
NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return()
Commit de144ff4234f changes _pnfs_return_layout() to call pnfs_mark_matching_lsegs_return() passing NULL as the struct pnfs_layout_range argument. Unfortunately, pnfs_mark_matching_lsegs_return() doesn't check if we have a value here before dereferencing it, causing an oops.
I'm able to hit this crash consistently when running connectathon basic tests on NFS v4.1/v4.2 against Ontap.
From the CVE record · Linux
A NULL pointer dereference in the Linux kernel’s NFSv4 layout-return code can cause a kernel crash. The crash was reproduced during NFS v4.1/v4.2 connectathon basic tests against Ontap. The input does not specify attacker access requirements or whether user interaction is needed.
Operators running the Linux kernel with NFS v4.1 or v4.2 should check their systems; affected versions are not specified.