Wind River Support Network

Description

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

CVEs

• CVE-2025-39913