Security readout for executives and security teams
Plain-English summary
A Linux kernel TLS receive-path flaw can crash the operating system when memory allocation fails and later processing uses invalid queue state. The primary business risk is service outage or host reboot, not data theft or modification.
Executive priority
Treat as a high-priority availability issue for exposed, availability-critical Linux workloads using kernel TLS. Patch through supported vendor channels promptly, while avoiding emergency assumptions for systems that do not use the affected path.
Technical view
During kernel TLS record reception, an alloc_page failure can detach the receive queue while full_len remains set. A later tls_strp_read_sock call continues the partial record and tls_strp_check_queue_ok reaches a NULL pointer, causing a kernel panic. The assigned CVSS 3.1 score is 7.5 for network-reachable availability impact.
Likely exposure
Exposure is limited to Linux systems running an affected kernel and using the kernel TLS receive path. The bundle lists affected kernel versions through 6.15, but its version data is ambiguous; distribution backports and exact package status require vendor verification.
Exploitation context
No active exploitation is established: the bundle marks this CVE as absent from KEV and provides no cited exploitation report. Triggering requires the vulnerable kernel TLS path and an allocation failure; practical attacker control is not demonstrated.
Researcher notes
The failure is a stale-state problem after allocation failure: full_len is retained although the receive queue is detached from frag_list. The published resolution prevents a NULL frag_list state. The sources establish a panic condition but do not establish reliable exploitation, prevalence, or confidentiality impact.
Mitigation direction
- Install a vendor-supported kernel containing the referenced upstream or stable fix.
- Check distribution advisories for backported package versions before relying on upstream version numbers.
- Prioritize internet-facing or availability-critical systems where kernel TLS is enabled.
- If immediate patching is impossible, consult vendor guidance about safely limiting kernel TLS exposure.
Validation and detection
- Inventory running kernel versions and identify systems using kernel TLS receive processing.
- Compare installed packages with distribution advisories and referenced stable-kernel fixes.
- Confirm the patched kernel is actually running after maintenance or reboot.
- Monitor affected systems for kernel NULL-pointer traces involving tls_strp_check_rcv or tls_strp_data_ready.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2025-38018 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6LinuxVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/8f7f96549bc55e4ef3a6b499bc5011e5de2f46c4CVE reference, Linux
- https://git.kernel.org/stable/c/406d05da26835943568e61bb751c569efae071d4CVE reference, Linux
- https://git.kernel.org/stable/c/a11b8c0be6acd0505a58ff40d474bd778b25b93aCVE reference, Linux
- https://git.kernel.org/stable/c/5f1f833cb388592bb46104463a1ec1b7c41975b6CVE reference, Linux
- https://git.kernel.org/stable/c/491deb9b8c4ad12fe51d554a69b8165b9ef9429fCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/08/msg00010.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.