{"id":"CVE-2026-64025","summary":"bpf, skmsg: fix verdict sk_data_ready racing with ktls rx","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf, skmsg: fix verdict sk_data_ready racing with ktls rx\n\nsk_psock_strp_data_ready() already checks tls_sw_has_ctx_rx() and\ndefers to psock-\u003esaved_data_ready when a TLS RX context is present,\navoiding a conflict with the TLS strparser's ownership of the receive\nqueue (commit e91de6afa81c, \"bpf: Fix running sk_skb program types\nwith ktls\").\n\nsk_psock_verdict_data_ready() has no equivalent guard.  When a socket\nis inserted into a sockmap (BPF_SK_SKB_VERDICT) before TLS RX is\nconfigured, tls_sw_strparser_arm() saves sk_psock_verdict_data_ready\nas rx_ctx-\u003esaved_data_ready.  On data arrival:\n\n  tls_data_ready -\u003e tls_strp_data_ready -\u003e tls_rx_msg_ready\n    -\u003e saved_data_ready() = sk_psock_verdict_data_ready()\n      -\u003e tcp_read_skb() drains sk_receive_queue via __skb_unlink()\n         without calling tcp_eat_skb(), so copied_seq is not advanced.\n\ntls_strp_msg_load() then finds tcp_inq() \u003e= full_len (stale), calls\ntcp_recv_skb() on the now-empty queue, hits WARN_ON_ONCE(!first), and\nreturns with rx_ctx-\u003estrp.anchor.frag_list pointing at a psock-owned\n(potentially freed) skb.  tls_decrypt_sg() subsequently walks that\nfrag_list: use-after-free.\n\nApply the same fix as sk_psock_strp_data_ready(): if a TLS RX context\nis present, call psock-\u003esaved_data_ready (sock_def_readable) to wake\nrecv() waiters and return immediately, leaving the receive queue\nuntouched.  TLS retains sole ownership of the queue and decrypts the\nrecord normally through tls_sw_recvmsg().","modified":"2026-07-22T03:31:50.529594882Z","published":"2026-07-19T15:39:17.178Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64025.json"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/1861d369efd62d67796563bf3e01fc22e5626f8b"},{"type":"WEB","url":"https://git.kernel.org/stable/c/7c8cf21bc4efb4af18d6096db3f8bd06d622251c"},{"type":"WEB","url":"https://git.kernel.org/stable/c/8a52139560f833c3975032e1f5762611e3a36d71"},{"type":"WEB","url":"https://git.kernel.org/stable/c/c9ea01768903ae47f210cd457af1dead6de7a9c3"},{"type":"WEB","url":"https://git.kernel.org/stable/c/ddf8029623a1af20e984c040e89ff918158397ab"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64025.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64025"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"ef5659280eb13e8ac31c296f58cfdfa1684ac06b"},{"fixed":"c9ea01768903ae47f210cd457af1dead6de7a9c3"},{"fixed":"7c8cf21bc4efb4af18d6096db3f8bd06d622251c"},{"fixed":"1861d369efd62d67796563bf3e01fc22e5626f8b"},{"fixed":"8a52139560f833c3975032e1f5762611e3a36d71"},{"fixed":"ddf8029623a1af20e984c040e89ff918158397ab"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-64025.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.10.0"},{"fixed":"6.6.142"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.92"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.34"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.0.11"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-64025.json"}}],"schema_version":"1.7.5","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"}]}