LiveActive security incident?Get immediate response
CVE Record

CVE-2025-37756: net: tls: explicitly disallow disconnect

In the Linux kernel, the following vulnerability has been resolved: net: tls: explicitly disallow disconnect syzbot discovered that it can disconnect a TLS socket and then run into all sort of unexpected corner cases. I have a vague recollection of Eric pointing this out to us a long time ago. Supporting disconnect is really hard, for one thing if offload is enabled we'd need to wait for all packets to be _acked_. Disconnect is not commonly used, disallow it. The immediate problem syzbot run into is the warning in the strp, but that's just the easiest bug to trigger: WARNING: CPU: 0 PID: 5834 at net/tls/tls_strp.c:486 tls_strp_msg_load+0x72e/0xa80 net/tls/tls_strp.c:486 RIP: 0010:tls_strp_msg_load+0x72e/0xa80 net/tls/tls_strp.c:486 Call Trace: <TASK> tls_rx_rec_wait+0x280/0xa60 net/tls/tls_sw.c:1363 tls_sw_recvmsg+0x85c/0x1c30 net/tls/tls_sw.c:2043 inet6_recvmsg+0x2c9/0x730 net/ipv6/af_inet6.c:678 sock_recvmsg_nosec net/socket.c:1023 [inline] sock_recvmsg+0x109/0x280 net/socket.c:1045 __sys_recvfrom+0x202/0x380 net/socket.c:2237

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A locally authenticated user may abuse an unsupported disconnect operation on a Linux kernel TLS socket, sending the kernel into unexpected states. The reported symptom is a kernel warning, but the maintainer indicates other corner cases exist. The supplied CVSS 3.1 score is 7.8, reflecting potentially serious confidentiality, integrity, and availability impact.

Executive priority

Prioritize internet-facing multi-user hosts, container platforms, and systems where untrusted local workloads can access kernel networking features. Treat remediation as high priority, but not as an emergency driven by known exploitation. Use normal expedited kernel patching and reboot procedures.

Technical view

The Linux kernel's TLS implementation permitted socket disconnect despite incomplete handling across TLS parsing, receive, and offload states. syzbot triggered a warning in tls_strp_msg_load after disconnecting a TLS socket. Stable fixes explicitly reject disconnect instead of attempting to preserve unsafe or inconsistent TLS state.

Likely exposure

Exposure requires an affected Linux kernel, local low-privilege access, and the ability to exercise kernel TLS sockets. The bundle lists affected releases beginning with 4.13 and multiple fixed stable releases, but its version encoding is ambiguous. Confirm exposure against the running distribution's advisory and kernel package changelog.

Exploitation context

The source bundle identifies a syzbot-generated trigger and marks this CVE as absent from KEV. It provides no evidence of active exploitation or public weaponization. The CVSS vector describes local, low-complexity, low-privilege exploitation without user interaction; network-only attackers are not established as an exposure path.

Researcher notes

The observed warning in tls_strp_msg_load is described as the easiest symptom, not necessarily the complete impact. Disconnect becomes especially difficult with TLS offload because outstanding packets may require acknowledgement. No CWE is assigned in the bundle. Validate affected ranges through vendor backport records rather than version-string comparison alone.

Mitigation direction

  • Install the distribution kernel update incorporating the applicable upstream stable fix.
  • Check vendor advisories because backported package versions may not match upstream release numbers.
  • Restrict unnecessary local access and kernel TLS use until affected systems are updated.
  • Reboot into the updated kernel and remove vulnerable kernels from normal boot options.

Validation and detection

  • Record each system's running kernel version and distribution package revision.
  • Compare package revisions with vendor advisories and the referenced stable fixes.
  • Confirm the updated kernel is active after reboot, not merely installed.
  • Review kernel logs for TLS parser warnings or related unexpected socket failures.
Prepared
Confidence
medium
Sources
12

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-37756 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
11Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-37756Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3c4d7559159bfe1e3b94df3a657b2cda3a34e218, 3c4d7559159bfe1e3b94df3a657b2cda3a34e218, 3c4d7559159bfe1e3b94df3a657b2cda3a34e218, 3c4d7559159bfe1e3b94df3a657b2cda3a34e218, 3c4d7559159bfe1e3b94df3a657b2cda3a34e218, 3c4d7559159bfe1e3b94df3a657b2cda3a34e218, 3c4d7559159bfe1e3b94df3a657b2cda3a34e218, 3c4d7559159bfe1e3b94df3a657b2cda3a34e218unaffected
LinuxLinux4.13, 0, 5.10.237, 5.15.181, 6.1.135, 6.6.88, 6.12.24, 6.13.12, 6.14.3, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.