Vulnerability · Published Jul 19, 2026 · Assigned by Linux
CVE-2026-64025bpf, skmsg: fix verdict sk_data_ready racing with ktls rx
Critical 9.8
In plain English
A critical-severity race condition in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 31% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: bpf, skmsg: fix verdict sk_data_ready racing with ktls rx sk_psock_strp_data_ready() already checks tls_sw_has_ctx_rx() and defers to psock->saved_data_ready when a TLS RX context is present, avoiding a conflict with the TLS strparser's ownership of the receive queue (commit e91de6afa81c, "bpf: Fix running sk_skb program types with ktls"). sk_psock_verdict_data_ready() has no equivalent guard. When a socket is inserted into a sockmap (BPF_SK_SKB_VERDICT) before TLS RX is configured, tls_sw_strparser_arm() saves sk_psock_verdict_data_ready as rx_ctx->saved_data_ready. On data arrival: tls_data_ready -> tls_strp_data_ready -> tls_rx_msg_ready -> saved_data_ready() = sk_psock_verdict_data_ready() -> tcp_read_skb() drains sk_receive_queue via __skb_unlink() without calling tcp_eat_skb(), so copied_seq is not advanced. tls_strp_msg_load() then finds tcp_inq() >= full_len (stale), calls tcp_recv_skb() on the now-empty queue, hits WARN_ON_ONCE(!first), and returns with rx_ctx->strp.anchor.frag_list pointing at a psock-owned (potentially freed) skb. tls_decrypt_sg() subsequently walks that frag_list: use-after-free. Apply the same fix as sk_psock_strp_data_ready(): if a TLS RX context is present, call psock->saved_data_ready (sock_def_readable) to wake recv() waiters and return immediately, leaving the receive queue untouched. TLS retains sole ownership of the queue and decrypts the record normally through tls_sw_recvmsg().
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | no fix listed | DEBIAN-CVE-2026-64025 |
| Debian:13 | linux | 6.12.94-1 | DEBIAN-CVE-2026-64025 |
| Debian:14 | linux | 7.0.12-1 | DEBIAN-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux | 6.8.0-139.139 | USN-8729-1 |
| Ubuntu:24.04:LTS | linux | 6.8.0-139.139 | UBUNTU-CVE-2026-64025 |
| Ubuntu:26.04:LTS | linux | 7.0.0-28.28 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-aws | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1064.67 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1064.67 | USN-8729-6 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1009.9 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1064.67~22.04.1 | USN-8729-6 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1064.67~22.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1067.75 | USN-8761-1 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1067.75 | UBUNTU-CVE-2026-64025 |
| Ubuntu:26.04:LTS | linux-azure | 7.0.0-1010.10 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1067.75~22.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1067.75~22.04.1 | USN-8761-3 |
| Ubuntu:24.04:LTS | linux-azure-7.0 | 7.0.0-1014.14~24.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1065.72 | UBUNTU-CVE-2026-64025 |
| Ubuntu:26.04:LTS | linux-azure-fde | 7.0.0-1009.9 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.17 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1065.72~22.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1013.13~24.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-gcp | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1067.75 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1067.75 | USN-8729-1 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1008.8 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1067.75~22.04.1 | USN-8729-3 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1067.75~22.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-gcp-7.0 | 7.0.0-1011.11~24.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-gke | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1062.70 | USN-8729-1 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1062.70 | UBUNTU-CVE-2026-64025 |
| Ubuntu:26.04:LTS | linux-gke | 7.0.0-1003.4 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-gkeop | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1049.53 | USN-8729-1 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1049.53 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-28.28~24.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-ibm | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1064.65 | USN-8729-3 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1064.65 | UBUNTU-CVE-2026-64025 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1010.10 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1066.67~22.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-intel-iotg | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-kvm | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-lowlatency | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-139.139.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-139.139.1 | USN-8729-4 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-139.139.1~22.04.1 | USN-8729-4 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-139.139.1~22.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1062.65 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1062.65 | USN-8729-1 |
| Ubuntu:26.04:LTS | linux-nvidia | 7.0.0-1016.16 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1062.65~22.04.1 | USN-8729-1 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1062.65~22.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-nvidia-7.0 | 7.0.0-1016.16~24.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:26.04:LTS | linux-nvidia-bos | 7.0.0-2016.16 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1062.65.1 | USN-8729-1 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1062.65.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1035.38 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1009.9 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-oracle | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1061.64 | USN-8802-1 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1061.64 | UBUNTU-CVE-2026-64025 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1008.8 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1061.64~22.04.1 | USN-8802-1 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1061.64~22.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-oracle-7.0 | 7.0.0-1011.11~24.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1064.68 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1064.68 | USN-8729-1 |
| Ubuntu:26.04:LTS | linux-raspi | 7.0.0-1015.15 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-28.28.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-28.28.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-139.139~22.04.1 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-riscv-7.0 | 7.0.0-28.28.1~24.04.3 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-vmware | 6.8.0-1008.8 | UBUNTU-CVE-2026-64025 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1036.37 | USN-8729-3 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1036.37 | UBUNTU-CVE-2026-64025 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | no fix listed | UBUNTU-CVE-2026-64025 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | ef5659280eb13e8ac31c296f58cfdfa1684ac06b – before d698bdba0f9969a6e390d1b1a9a3e283f1f174a7ef5659280eb13e8ac31c296f58cfdfa1684ac06b – before c9ea01768903ae47f210cd457af1dead6de7a9c3ef5659280eb13e8ac31c296f58cfdfa1684ac06b – before 7c8cf21bc4efb4af18d6096db3f8bd06d622251cef5659280eb13e8ac31c296f58cfdfa1684ac06b – before 1861d369efd62d67796563bf3e01fc22e5626f8bef5659280eb13e8ac31c296f58cfdfa1684ac06b – before 8a52139560f833c3975032e1f5762611e3a36d71ef5659280eb13e8ac31c296f58cfdfa1684ac06b – before ddf8029623a1af20e984c040e89ff918158397ab |
| Linux | Linux | 5.10 |
Weakness: CWE-362 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References
- https://git.kernel.org/stable/c/d698bdba0f9969a6e390d1b1a9a3e283f1f174a7
- https://git.kernel.org/stable/c/c9ea01768903ae47f210cd457af1dead6de7a9c3
- https://git.kernel.org/stable/c/7c8cf21bc4efb4af18d6096db3f8bd06d622251c
- https://git.kernel.org/stable/c/1861d369efd62d67796563bf3e01fc22e5626f8b
- https://git.kernel.org/stable/c/8a52139560f833c3975032e1f5762611e3a36d71
- https://git.kernel.org/stable/c/ddf8029623a1af20e984c040e89ff918158397ab