sunrpc: fix client side handling of tls alerts
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sunrpc: fix client side handling of tls alerts
A security exploit was discovered in NFS over TLS in tls_alert_recv due to its assumption that there is valid data in the msghdr's iterator's kvec.
Instead, this patch proposes the rework how control messages are setup and used by sock_recvmsg().
If no control message structure is setup, kTLS layer will read and process TLS data record types. As soon as it encounters a TLS control message, it would return an error. At that point, NFS can setup a kvec backed control buffer and read in the control message such as a TLS alert. Scott found that a msg iterator can advance the kvec pointer as a part of the copy process thus we need to revert the iterator before calling into the tls_alert_recv.
From the CVE record · Linux
The Linux kernel’s NFS over TLS client mishandles TLS alerts because tls_alert_recv assumes the message iterator’s kvec contains valid data. A security exploit was discovered, but the input does not specify what an attacker can achieve or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with NFS over TLS should check their exposure; affected versions are not specified.