Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Aug 22, 2025
Updated
Aug 27, 2026
EPSS
0.2% · 11th percentile

Report tools

JSON

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.

Follow CVE-2025-38616

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux 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.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:13linuxbefore 6.12.43-16.12.43-1
Debian:14linuxbefore 6.16.3-16.16.3-1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_10before 10-150600.2.110-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_11before 9-150600.2.19-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_12before 9-150600.2.19-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_13before 8-150600.2.18-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_15before 4-150600.2.14-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_6before 16-150600.2.116-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_7before 16-150600.2.116-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_10before 10-150600.2.110-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_11before 9-150600.2.19-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_13before 8-150600.2.18-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_14before 4-150600.2.14-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_5before 19-150600.2.119-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_7before 16-150600.2.116-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_9before 11-150600.2.111-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_0before 8-150700.3.21.28-150700.3.21.2
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_1before 8-150700.2.18-150700.2.1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_4before 4-150700.2.14-150700.2.1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_0before 8-150700.3.18-150700.3.1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_1before 8-150700.2.18-150700.2.1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_2before 8-150700.2.18-150700.2.1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_4before 4-150700.2.14-150700.2.1

+22

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38614Aug 19, 2025 · eventpoll: Fix semi-unbounded recursion
    22Monitor
  • ← EarlierCVE-2025-38615Aug 19, 2025 · fs/ntfs3: cancle set bad inode after removing name fails
    22Monitor
  • Later →CVE-2025-38618Aug 22, 2025 · vsock: Do not allow binding to VMADDR_PORT_ANY
    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 / packageFixed versionSource
Linux Linux2fb97ed9e2672b4f6e24ce206ac1a875ce4bcb38Vendor (CNA)
Linux Linux6db015fc4b5d5f63a64a193f65d98da3a7fc811dVendor (CNA)
Linux Linuxdb3658a12d5ec4db7185ae7476151a50521b7207Vendor (CNA)
Linux Linuxeb0336f213fe88bbdb7d2b19c9c9ec19245a3155Vendor (CNA)
Linux Linuxef50eaab631f9bf519ddbdfa42ccb0528adc1fc8Vendor (CNA)
Linux Linuxf1fe99919f629f980d0b8a7ff16950bffe06a859Vendor (CNA)
azl3 kernel 6.6.96.2-2 on Azure Linux 3.06.6.104.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0_Update_316-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0_Update_414-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0_Update_512-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0_Update_610-3.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0_Update_79-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_316-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_413-1.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_512-1.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_610-3.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_710-1.3 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_89-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_98-1.2 · SUSE:Linux Micro 6.0Package 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.

Finders, 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 Read

CVSS 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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records