CVE-2025-68227
mptcp: Fix proto fallback detection with BPF
Reported by linux · Published December 16, 2025
In the Linux kernel, the following vulnerability has been resolved: mptcp: Fix proto fallback detection with BPF The sockmap feature allows bpf syscall from userspace, or based on bpf sockops, replacing the sk_prot of sockets during protocol stack processing with sockmap's custom read/write interfaces. ''' tcp_rcv_state_process() syn_recv_sock()/subflow_syn_recv_sock() tcp_init_transfer(BPF_SOCK_OPS_PASSIVE_ESTABLISHED_CB) bpf_skops_established <== sockops bpf_sock_map_update(sk) <== call bpf helper tcp_bpf_update_proto() <== update sk_prot ''' When the server has MPTCP enabled but the client sends a TCP SYN without MPTCP, subflow_syn_recv_sock() performs a fallback on the subflow, replacing the subflow sk's sk_prot with the native sk_prot. ''' subflow_syn_recv_sock() subflow_ulp_fallback() subflow_drop_ctx() mptcp_subflow_ops_undo_override() ''' Then, this subflow can be normally used by sockmap, which replaces the native sk_prot with sockmap's custom sk_prot. The issue occurs when the user executes accept::mptcp_stream_accept::mptcp_fallback_tcp_ops(). Here, it uses sk->sk_prot to compare with the native sk_prot, but this is incorrect when sockmap is used, as we may incorrectly set sk->sk_socket->ops. This fix uses the more generic sk_family for the comparison instead. Additionally, this also prevents a WARNING from occurring: result from ./scripts/decode_stacktrace.sh: ------------[ cut here ]------------ WARNING: CPU: 0 PID: 337 at net/mptcp/protocol.c:68 mptcp_stream_accept \ (net/mptcp/protocol.c:4005) Modules linked in: ... PKRU: 55555554 Call Trace: <TASK> do_accept (net/socket.c:1989) __sys_accept4 (net/socket.c:2028 net/socket.c:2057) __x64_sys_accept (net/socket.c:2067) x64_sys_call (arch/x86/entry/syscall_64.c:41) do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) RIP: 0033:0x7f87ac92b83d ---[ end trace 0000000000000000 ]---
EPSS 0.23% · 14.1th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.12-libbpf-devel | Amazon Linux | 1:6.12.63-84.121.amzn2023 |
| kernel-libbpf-static | Amazon Linux | 1:6.1.159-181.297.amzn2023 |
| kernel-tools | Amazon Linux | 1:6.1.159-181.297.amzn2023 |
| python3-perf6.12 | Amazon Linux | 1:6.12.63-84.121.amzn2023 |
| Linux | Linux | c77b3b79a92e3345aa1ee296180d1af4e7031f8f, 9b1980b6f23fa30bf12add19f37c7458625099eb, 5.7, 1a0d5c74af9b6ba9ffdf1172de5a1a6df5922a00 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 0b4f33def7bbde1ce2fea05f116639270e7acdc7, 0b4f33def7bbde1ce2fea05f116639270e7acdc7, 0b4f33def7bbde1ce2fea05f116639270e7acdc7 |
| Linux | Linux | 5.7, 0, 5.10.247 |
| amazon:2023 | kernel6.12-libbpf-devel | 0 |
| amazon:2023 | kernel-libbpf-static | 0 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| Linux | Linux | 6.12.60, 6.6.118, 6.1.159 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | kernel6.12 | 0 |
| linux | linux_kernel | 5.7, 5.7, 5.7 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | kernel-libbpf-devel | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2023 | kernel6.12-libbpf | 0 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel-devel | 0 |
| amazon:2023 | kernel6.12-libbpf-static | 0 |
| amazon:2023 | kernel-libbpf | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | perf6.12 | 0 |
…and 12 more
Timeline
- Dec 16, 2025 CVE Published
- Dec 17, 2025 EPSS Score (30 in total, the first dated here)
- Mar 26, 2026 Coalition ESS Score (2 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (174 in total, the first dated here)
- Mar 29, 2026 Security Advisory (181 in total, the first dated here)
- May 11, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-68227
vulnetix vdb fixes CVE-2025-68227
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-68227/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart