Answer in brief
CVE-2025-38566 records a Unknown severity vulnerability in sunrpc: fix handling of server side tls alerts. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5e052dda121e2870dd87181783da4a95d7d2927b <b1df394621710b312f0393e3f240fdac0764f968 || >=5e052dda121e2870dd87181783da4a95d7d2927b <25bb3647d30a20486b5fe7cff2b0e503c16c9692 || >=5e052dda121e2870dd87181783da4a95d7d2927b <3b549da875414989f480b66835d514be80a0bd9c || >=5e052dda121e2870dd87181783da4a95d7d2927b <6b33c31cc788073bfbed9297e1f4486ed73d87da || >=5e052dda121e2870dd87181783da4a95d7d2927b <bee47cb026e762841f3faece47b51f985e215edb | b1df394621710b312f0393e3f240fdac0764f968, 25bb3647d30a20486b5fe7cff2b0e503c16c9692, 3b549da875414989f480b66835d514be80a0bd9c, 6b33c31cc788073bfbed9297e1f4486ed73d87da, bee47cb026e762841f3faece47b51f985e215edb |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Aug 19, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix handling of server side tls alerts Scott Mayhew discovered a security exploit in NFS over TLS in tls_alert_recv() due to its assumption it can read data from the msg iterator's kvec.. kTLS implementation splits TLS non-data record payload between the control message buffer (which includes the type such as TLS aler or TLS cipher change) and the rest of the payload (say TLS alert's level/description) which goes into the msg payload buffer. This patch proposes to 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 msg buffer and read in the control message such as a TLS alert. 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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38566 records a Unknown severity vulnerability in sunrpc: fix handling of server side tls alerts. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5e052dda121e2870dd87181783da4a95d7d2927b <b1df394621710b312f0393e3f240fdac0764f968 || >=5e052dda121e2870dd87181783da4a95d7d2927b <25bb3647d30a20486b5fe7cff2b0e503c16c9692 || >=5e052dda121e2870dd87181783da4a95d7d2927b <3b549da875414989f480b66835d514be80a0bd9c || >=5e052dda121e2870dd87181783da4a95d7d2927b <6b33c31cc788073bfbed9297e1f4486ed73d87da || >=5e052dda121e2870dd87181783da4a95d7d2927b <bee47cb026e762841f3faece47b51f985e215edb | b1df394621710b312f0393e3f240fdac0764f968, 25bb3647d30a20486b5fe7cff2b0e503c16c9692, 3b549da875414989f480b66835d514be80a0bd9c, 6b33c31cc788073bfbed9297e1f4486ed73d87da, bee47cb026e762841f3faece47b51f985e215edb |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Aug 19, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix handling of server side tls alerts Scott Mayhew discovered a security exploit in NFS over TLS in tls_alert_recv() due to its assumption it can read data from the msg iterator's kvec.. kTLS implementation splits TLS non-data record payload between the control message buffer (which includes the type such as TLS aler or TLS cipher change) and the rest of the payload (say TLS alert's level/description) which goes into the msg payload buffer. This patch proposes to 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 msg buffer and read in the control message such as a TLS alert. 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.
Quoted source text, attributed separately from HOL analysis.