Vulnerability · Published Oct 1, 2025 · Assigned by Linux

CVE-2025-39913tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork.

High 7.8

In plain English

A high-severity security flaw 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.2% (higher than 8% of all known vulnerabilities). Ready-made attack tooling exists: public proof-of-concept code. Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)7.8High
Exploit odds (30 days)0.2%top 91.6% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack tooling1Public PoC

Official description

In the Linux kernel, the following vulnerability has been resolved: tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork. syzbot reported the splat below. [0] The repro does the following: 1. Load a sk_msg prog that calls bpf_msg_cork_bytes(msg, cork_bytes) 2. Attach the prog to a SOCKMAP 3. Add a socket to the SOCKMAP 4. Activate fault injection 5. Send data less than cork_bytes At 5., the data is carried over to the next sendmsg() as it is smaller than the cork_bytes specified by bpf_msg_cork_bytes(). Then, tcp_bpf_send_verdict() tries to allocate psock->cork to hold the data, but this fails silently due to fault injection + __GFP_NOWARN. If the allocation fails, we need to revert the sk->sk_forward_alloc change done by sk_msg_alloc(). Let's call sk_msg_free() when tcp_bpf_send_verdict fails to allocate psock->cork. The "*copied" also needs to be updated such that a proper error can be returned to the caller, sendmsg. It fails to allocate psock->cork. Nothing has been corked so far, so this patch simply sets "*copied" to 0. [0]: WARNING: net/ipv4/af_inet.c:156 at inet_sock_destruct+0x623/0x730 net/ipv4/af_inet.c:156, CPU#1: syz-executor/5983 Modules linked in: CPU: 1 UID: 0 PID: 5983 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:inet_sock_destruct+0x623/0x730 net/ipv4/af_inet.c:156 Code: 0f 0b 90 e9 62 fe ff ff e8 7a db b5 f7 90 0f 0b 90 e9 95 fe ff ff e8 6c db b5 f7 90 0f 0b 90 e9 bb fe ff ff e8 5e db b5 f7 90 <0f> 0b 90 e9 e1 fe ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 9f fc RSP: 0018:ffffc90000a08b48 EFLAGS: 00010246 RAX: ffffffff8a09d0b2 RBX: dffffc0000000000 RCX: ffff888024a23c80 RDX: 0000000000000100 RSI: 0000000000000fff RDI: 0000000000000000 RBP: 0000000000000fff R08: ffff88807e07c627 R09: 1ffff1100fc0f8c4 R10: dffffc0000000000 R11: ffffed100fc0f8c5 R12: ffff88807e07c380 R13: dffffc0000000000 R14: ffff88807e07c60c R15: 1ffff1100fc0f872 FS: 00005555604c4500(0000) GS:ffff888125af1000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005555604df5c8 CR3: 0000000032b06000 CR4: 00000000003526f0 Call Trace: <IRQ> __sk_destruct+0x86/0x660 net/core/sock.c:2339 rcu_do_batch kernel/rcu/tree.c:2605 [inline] rcu_core+0xca8/0x1770 kernel/rcu/tree.c:2861 handle_softirqs+0x286/0x870 kernel/softirq.c:579 __do_softirq kernel/softirq.c:613 [inline] invoke_softirq kernel/softirq.c:453 [inline] __irq_exit_rcu+0xca/0x1f0 kernel/softirq.c:680 irq_exit_rcu+0x9/0x30 kernel/softirq.c:696 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1052 [inline] sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1052 </IRQ>

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.153-1DEBIAN-CVE-2025-39913
Debian:13linux6.12.48-1DEBIAN-CVE-2025-39913
Debian:14linux6.16.8-1DEBIAN-CVE-2025-39913
Ubuntu:22.04:LTSlinux5.15.0-170.180UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux5.15.0-170.180USN-8033-1
Ubuntu:24.04:LTSlinux6.8.0-106.106UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-aws5.15.0-1100.107UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-aws5.15.0-1100.107USN-8033-1
Ubuntu:24.04:LTSlinux-aws6.8.0-1050.53UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1050.53~22.04.1UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-azure5.15.0-1109.118USN-8163-2
Ubuntu:22.04:LTSlinux-azure5.15.0-1109.118UBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-azure6.8.0-1051.57UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1051.57~22.04.1UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1109.118.1UBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1058.65UBUNTU-CVE-2025-39913
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-gcp5.15.0-1100.109USN-8033-1
Ubuntu:22.04:LTSlinux-gcp5.15.0-1100.109UBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-gcp6.8.0-1052.55UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-gke5.15.0-1096.102UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-gke5.15.0-1096.102USN-8033-1
Ubuntu:24.04:LTSlinux-gke6.8.0-1048.53UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1083.91UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1083.91USN-8033-1
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1035.38UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-106.106~22.04.1UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-ibm5.15.0-1094.97USN-8033-1
Ubuntu:22.04:LTSlinux-ibm5.15.0-1094.97UBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-ibm6.8.0-1049.49UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1049.49~22.04.1UBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-intelno fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1095.101UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1095.101USN-8033-8
Ubuntu:22.04:LTSlinux-kvm5.15.0-1092.97UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-kvm5.15.0-1092.97USN-8033-5
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-170.180UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-170.180USN-8033-1
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-106.106.1UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-106.106.1~22.04.1UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1095.96UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1095.96USN-8033-6
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1049.52UBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1049.52~22.04.1UBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1049.52.1UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1052.52USN-8034-1
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1052.52UBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1020.20UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1041.41UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1041.41USN-8034-2
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-oracle5.15.0-1097.103USN-8033-5
Ubuntu:22.04:LTSlinux-oracle5.15.0-1097.103UBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-oracle6.8.0-1047.48UBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1047.48~22.04.1UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-raspi5.15.0-1097.100UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-raspi5.15.0-1097.100USN-8141-1
Ubuntu:24.04:LTSlinux-raspi6.8.0-1050.54UBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-106.106~22.04.1UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-39913
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1028.29UBUNTU-CVE-2025-39913
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1064.68USN-8033-7
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1064.68UBUNTU-CVE-2025-39913

Affected products (as reported)

VendorProductVersions
Linux Linux 4f738adba30a7cfc006f605707e7aee847ffefa0 – before 08f58d10f5abf11d297cc910754922498c921f914f738adba30a7cfc006f605707e7aee847ffefa0 – before 05366527f44cf4b884f3d9462ae8009be96658564f738adba30a7cfc006f605707e7aee847ffefa0 – before 7429b8b9bfbc276fd304fbaebc405f46b421fedf4f738adba30a7cfc006f605707e7aee847ffefa0 – before 9c2a6456bdf9794474460d885c359b6c4522d6e34f738adba30a7cfc006f605707e7aee847ffefa0 – before 66bcb04a441fbf15d66834b7e3eefb313dd750c84f738adba30a7cfc006f605707e7aee847ffefa0 – before 539920180c55f5e13a2488a2339f94e6b8cb69e04f738adba30a7cfc006f605707e7aee847ffefa0 – before de89e58368f8f07df005ecc1c86ad94898a999f24f738adba30a7cfc006f605707e7aee847ffefa0 – before a3967baad4d533dc254c31e0d221e51c8d223d58
Linux Linux 4.17

References