nfsd: Initialize ssc before laundromat_work to prevent NULL dereference
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f4e44b393389c77958f7c58bf4415032b4cda15b · < 83ac1ba8ca102ab5c0ed4351f8ac6e74ac4d5d64| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nfsd: Initialize ssc before laundromat_work to prevent NULL dereference
In nfs4_state_start_net(), laundromat_work may access nfsd_ssc through nfs4_laundromat -> nfsd4_ssc_expire_umount. If nfsd_ssc isn't initialized, this can cause NULL pointer dereference.
Normally the delayed start of laundromat_work allows sufficient time for nfsd_ssc initialization to complete. However, when the kernel waits too long for userspace responses (e.g. in nfs4_state_start_net -> nfsd4_end_grace -> nfsd4_record_grace_done -> nfsd4_cld_grace_done -> cld_pipe_upcall -> __cld_pipe_upcall -> wait_for_completion path), the delayed work may start before nfsd_ssc initialization finishes.
Fix this by moving nfsd_ssc initialization before starting laundromat_work.
From the CVE record · Linux
In the Linux kernel's nfsd component, laundromat work can access nfsd_ssc before it is initialized if the kernel waits too long for a userspace response. This can cause a NULL pointer dereference; the input does not establish how an attacker could trigger it or whether authentication or user interaction is required.
Operators running the Linux kernel should check their versions; affected versions are not specified.