netfs: Fix NULL pointer dereference in netfs_unbuffered_write() on retry
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
| No fix yet |
In the Linux kernel, the following vulnerability has been resolved:
netfs: Fix NULL pointer dereference in netfs_unbuffered_write() on retry
When a write subrequest is marked NETFS_SREQ_NEED_RETRY, the retry path in netfs_unbuffered_write() unconditionally calls stream->prepare_write() without checking if it is NULL.
Filesystems such as 9P do not set the prepare_write operation, so stream->prepare_write remains NULL. When get_user_pages() fails with -EFAULT and the subrequest is flagged for retry, this results in a NULL pointer dereference at fs/netfs/direct_write.c:189.
Fix this by mirroring the pattern already used in write_retry.c: if stream->prepare_write is NULL, skip renegotiation and directly reissue the subrequest via netfs_reissue_write(), which handles iterator reset, IN_PROGRESS flag, stats update and reissue internally.
From the CVE record · Linux
The Linux kernel's netfs unbuffered-write retry path can call a NULL prepare_write operation on filesystems such as 9P. If get_user_pages() fails with -EFAULT and the write subrequest is flagged for retry, this causes a kernel NULL pointer dereference. The input does not specify attacker access or user-interaction requirements.
Engineers running the Linux kernel with filesystems such as 9P should check their deployments; affected versions are not specified.