CVE-2025-38616: tls: handle data disappearing from under the TLS ULP
Noroxi assessment
Priority: Monitor (action score 28/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.20% (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.
- Fixed version: Linux Linux 2fb97ed9e2672b4f6e24ce206ac1a875ce4bcb38, 6db015fc4b5d5f63a64a193f65d98da3a7fc811d, db3658a12d5ec4db7185ae7476151a50521b7207; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1.
Low priority for now. Upgrade to Linux Linux 2fb97ed9e2672b4f6e24ce206ac1a875ce4bcb38, 6db015fc4b5d5f63a64a193f65d98da3a7fc811d, db3658a12d5ec4db7185ae7476151a50521b7207; 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: tls: handle data disappearing from under the TLS ULP TLS expects that it owns the receive queue of the TCP socket. This cannot be guaranteed in case the reader of the TCP socket entered before the TLS ULP was installed, or uses some non-standard read API (eg. zerocopy ones). Replace the WARN_ON() and a buggy early exit (which leaves anchor pointing to a freed skb) with real error handling. Wipe the parsing state and tell the reader to retry. We already reload the anchor every time we (re)acquire the socket lock, so the only condition we need to avoid is an out of bounds read (not having enough bytes in the socket for previously parsed record len). If some data was read from under TLS but there's enough in the queue we'll reload and decrypt what is most likely not a valid TLS record. Leading to some undefined behavior from TLS perspective (corrupting a stream? missing an alert? missing an attack?) but no kernel crash should take place.
- BDU:2025-15792
- SUSE-SU-2025:21085-1
- SUSE-SU-2025:21086-1
- SUSE-SU-2025:21087-1
- SUSE-SU-2025:21088-1
- SUSE-SU-2025:21089-1
- SUSE-SU-2025:21090-1
- SUSE-SU-2025:21091-1
- SUSE-SU-2025:21092-1
- SUSE-SU-2025:21093-1
- SUSE-SU-2025:21094-1
- SUSE-SU-2025:21095-1
- SUSE-SU-2025:21096-1
- SUSE-SU-2025:21097-1
- SUSE-SU-2025:21098-1
- SUSE-SU-2025:21099-1
- SUSE-SU-2025:21100-1
- SUSE-SU-2025:21101-1
- SUSE-SU-2025:21102-1
- SUSE-SU-2025:21103-1
- Published
- Aug 22, 2025
- Updated
- Aug 27, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-125
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.1
- CNA · Linux
- 7.8
- 0.7 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.0 and later · before 6.6.103
- linux linux kernel6.7 and later · before 6.12.43
- linux linux kernel6.13 and later · before 6.15.11
- linux linux kernel6.16 and later · before 6.16.2
- linux linux kernel6.17
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.0affected
- 84c61fe1a75b4255df1e1e7c054c9e6d048da417 and later · before ef50eaab631f9bf519ddbdfa42ccb0528adc1fc8affected · git
- 84c61fe1a75b4255df1e1e7c054c9e6d048da417 and later · before f1fe99919f629f980d0b8a7ff16950bffe06a859affected · git
- 84c61fe1a75b4255df1e1e7c054c9e6d048da417 and later · before eb0336f213fe88bbdb7d2b19c9c9ec19245a3155affected · git
- 84c61fe1a75b4255df1e1e7c054c9e6d048da417 and later · before db3658a12d5ec4db7185ae7476151a50521b7207affected · git
- 84c61fe1a75b4255df1e1e7c054c9e6d048da417 and later · before 2fb97ed9e2672b4f6e24ce206ac1a875ce4bcb38affected · git
- 84c61fe1a75b4255df1e1e7c054c9e6d048da417 and later · before 6db015fc4b5d5f63a64a193f65d98da3a7fc811daffected · git
- before 6.0not affected · semver
- 6.1.185 and later · up to and including 6.1.*not affected · semver
- 6.6.103 and later · up to and including 6.6.*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 |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:13 | linux | before 6.12.43-1 | 6.12.43-1 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_10 | before 10-150600.2.1 | 10-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_11 | before 9-150600.2.1 | 9-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_12 | before 9-150600.2.1 | 9-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_13 | before 8-150600.2.1 | 8-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_15 | before 4-150600.2.1 | 4-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_6 | before 16-150600.2.1 | 16-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_7 | before 16-150600.2.1 | 16-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_10 | before 10-150600.2.1 | 10-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_11 | before 9-150600.2.1 | 9-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_13 | before 8-150600.2.1 | 8-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_14 | before 4-150600.2.1 | 4-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_5 | before 19-150600.2.1 | 19-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_7 | before 16-150600.2.1 | 16-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_9 | before 11-150600.2.1 | 11-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_0 | before 8-150700.3.21.2 | 8-150700.3.21.2 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_1 | before 8-150700.2.1 | 8-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_4 | before 4-150700.2.1 | 4-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_0 | before 8-150700.3.1 | 8-150700.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_1 | before 8-150700.2.1 | 8-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_2 | before 8-150700.2.1 | 8-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_4 | before 4-150700.2.1 | 4-150700.2.1 |
+22
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-38614Aug 19, 2025 · eventpoll: Fix semi-unbounded recursion22Monitor
- ← EarlierCVE-2025-38615Aug 19, 2025 · fs/ntfs3: cancle set bad inode after removing name fails22Monitor
- Later →CVE-2025-38618Aug 22, 2025 · vsock: Do not allow binding to VMADDR_PORT_ANY31Monitor
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 | 2fb97ed9e2672b4f6e24ce206ac1a875ce4bcb38 | Vendor (CNA) |
| Linux Linux | 6db015fc4b5d5f63a64a193f65d98da3a7fc811d | Vendor (CNA) |
| Linux Linux | db3658a12d5ec4db7185ae7476151a50521b7207 | Vendor (CNA) |
| Linux Linux | eb0336f213fe88bbdb7d2b19c9c9ec19245a3155 | Vendor (CNA) |
| Linux Linux | ef50eaab631f9bf519ddbdfa42ccb0528adc1fc8 | Vendor (CNA) |
| Linux Linux | f1fe99919f629f980d0b8a7ff16950bffe06a859 | Vendor (CNA) |
| azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 | 6.6.104.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_3 | 16-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_4 | 14-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_5 | 12-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_6 | 10-3.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_7 | 9-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_3 | 16-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_4 | 13-1.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_5 | 12-1.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_6 | 10-3.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_7 | 10-1.3 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_8 | 9-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_9 | 8-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
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
- high · data can be read
- 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
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/6db015fc4b5d5f63a64a193f65d98da3a7fc811d
- git.kernel.org/stable/c/db3658a12d5ec4db7185ae7476151a50521b7207
- git.kernel.org/stable/c/eb0336f213fe88bbdb7d2b19c9c9ec19245a3155
- git.kernel.org/stable/c/ef50eaab631f9bf519ddbdfa42ccb0528adc1fc8
- git.kernel.org/stable/c/f1fe99919f629f980d0b8a7ff16950bffe06a859
Vendor advisories and official records. Exploit/PoC links are deliberately left out.