CVE-2025-38571: sunrpc: fix client side handling of tls alerts
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.34% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 3ee397eaaca4fa04db21bb98c8f1d0c6cc525368, 3feada5baf4dc96e151ff2ca54630e1d274e5458, a55b3d15331859d9fdd261cfa6d34ca2aeb0fb95; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1.
- Severity is disputed: the assigning authority (CNA) scores it 8.2, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 3ee397eaaca4fa04db21bb98c8f1d0c6cc525368, 3feada5baf4dc96e151ff2ca54630e1d274e5458, a55b3d15331859d9fdd261cfa6d34ca2aeb0fb95; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 19, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.3% · 28th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 8.2
- 2.7 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.5 and later · before 6.6.102
- linux linux kernel6.7 and later · before 6.12.42
- linux linux kernel6.13 and later · before 6.15.10
- linux linux kernel6.16 and later · before 6.16.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.5affected
- dea034b963c8901bdcc3d3880c04f0d75c95112f and later · before a55b3d15331859d9fdd261cfa6d34ca2aeb0fb95affected · git
- dea034b963c8901bdcc3d3880c04f0d75c95112f and later · before c36b2fbd60e8f9c6f975522130998608880c93beaffected · git
- dea034b963c8901bdcc3d3880c04f0d75c95112f and later · before 3ee397eaaca4fa04db21bb98c8f1d0c6cc525368affected · git
- dea034b963c8901bdcc3d3880c04f0d75c95112f and later · before 3feada5baf4dc96e151ff2ca54630e1d274e5458affected · git
- dea034b963c8901bdcc3d3880c04f0d75c95112f and later · before cc5d59081fa26506d02de2127ab822f40d88bc5aaffected · git
- before 6.5not affected · semver
- 6.6.102 and later · up to and including 6.6.*not affected · semver
- 6.12.42 and later · up to and including 6.12.*not affected · semver
- 6.15.10 and later · up to and including 6.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-55.40.1.el10_0 | 6.12.0-55.40.1.el10_0 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-55.40.1.el10_0 | 6.12.0-55.40.1.el10_0 |
| AlmaLinux:9 | kernel | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-core | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-570.55.1.el9_6 | 5.14.0-570.55.1.el9_6 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38566Aug 19, 2025 · sunrpc: fix handling of server side tls alerts30Monitor
- ← EarlierCVE-2025-38569Aug 19, 2025 · benet: fix BUG when creating VFs22Monitor
- Later →CVE-2025-38574Aug 19, 2025 · pptp: ensure minimal skb length in pptp_xmit()31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3ee397eaaca4fa04db21bb98c8f1d0c6cc525368 | Vendor (CNA) |
| Linux Linux | 3feada5baf4dc96e151ff2ca54630e1d274e5458 | Vendor (CNA) |
| Linux Linux | a55b3d15331859d9fdd261cfa6d34ca2aeb0fb95 | Vendor (CNA) |
| Linux Linux | c36b2fbd60e8f9c6f975522130998608880c93be | Vendor (CNA) |
| Linux Linux | cc5d59081fa26506d02de2127ab822f40d88bc5a | Vendor (CNA) |
| azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 | 6.6.104.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 5.14.0-570.55.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-570.55.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-570.55.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-570.55.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-570.55.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-570.55.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-570.55.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-570.55.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-570.55.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-570.55.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-570.55.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-570.55.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.12.43-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-570.55.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+2
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.