CVE-2025-38608: bpf, ktls: Fix data corruption when using bpf_msg_pop_data() in ktls
In the Linux kernel, the following vulnerability has been resolved:
bpf, ktls: Fix data corruption when using bpf_msg_pop_data() in ktls
When sending plaintext data, we initially calculated the corresponding
ciphertext length. However, if we later reduced the plaintext data length
via socket policy, we failed to recalculate the ciphertext length.
This results in transmitting buffers containing uninitialized data during
ciphertext transmission.
This causes uninitialized bytes to be appended after a complete
"Application Data" packet, leading to errors on the receiving end when
parsing TLS record.
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw can cause systems using kernel TLS with a specific BPF socket policy operation to send unintended, uninitialized bytes. This may expose residual data and cause receiving applications to reject malformed TLS records. Exposure depends on whether the affected kTLS and BPF features are used together.
Executive priority
Treat as a high-priority, targeted kernel update rather than an indiscriminate emergency. Rapidly identify systems using kTLS with BPF socket policy, patch those first, and follow normal accelerated maintenance for remaining affected kernels. Escalate if sensitive workloads expose the vulnerable path.
Technical view
When bpf_msg_pop_data() shortens plaintext governed by socket policy, kTLS previously retained the original ciphertext-length calculation. Transmission could therefore include uninitialized bytes after a complete TLS Application Data record, creating potential confidentiality loss, limited corruption, and receiver-side parsing failures.
Likely exposure
Likely exposure is limited to Linux systems using kTLS together with BPF socket policy that invokes bpf_msg_pop_data(). The bundle lists multiple affected kernel branches, but does not provide reliable distribution-specific package ranges. Systems not using this feature combination are unlikely to reach the vulnerable path.
Exploitation context
The supplied record has a CVSS 3.1 score of 8.6 and a network attack vector, but it is not listed in KEV. No supplied source reports active exploitation or a public exploit. Practical reachability and attacker control over the relevant BPF policy path remain unclear from the evidence.
Researcher notes
The defect is a stale length calculation after plaintext reduction, not a conventional TLS cryptographic break. Uninitialized trailing bytes create an information-disclosure concern and can disrupt TLS parsing. The bundle supplies multiple stable-branch fixes but insufficient information to establish exploitability, attacker prerequisites, or precise distribution package boundaries.
Mitigation direction
Update to a vendor-supported kernel containing the applicable upstream stable fix.
Check the Linux distribution's advisory for exact fixed package versions and reboot requirements.
Prioritize systems confirmed to use both kTLS and relevant BPF socket policies.
If updates are delayed, seek vendor guidance for safely avoiding the affected feature combination.
Validation and detection
Inventory running kernel and distribution package versions across Linux systems.
Determine whether kTLS and BPF socket policies using bpf_msg_pop_data() are deployed.
Compare installed kernels with vendor advisories or the applicable upstream stable fix.
Confirm updated systems booted into the fixed kernel.
Review TLS receiver logs for unexplained record-parsing failures or malformed trailing data.
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-38608 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
12Source 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.