CVE-2022-49877

bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues

MEDIUM

5.5

CVSS Score

Published: May 1, 2025 at 02:10 PM UTC

Updated: June 17, 2026 at 05:19 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues When running `test_sockmap` selftests, the following warning appears: WARNING: CPU: 2 PID: 197 at net/core/stream.c:205 sk_stream_kill_queues+0xd3/0xf0 Call Trace: <TASK> inet_csk_destroy_sock+0x55/0x110 tcp_rcv_state_process+0xd28/0x1380 ? tcp_v4_do_rcv+0x77/0x2c0 tcp_v4_do_rcv+0x77/0x2c0 __release_sock+0x106/0x130 __tcp_close+0x1a7/0x4e0 tcp_close+0x20/0x70 inet_release+0x3c/0x80 __sock_release+0x3a/0xb0 sock_close+0x14/0x20 __fput+0xa3/0x260 task_work_run+0x59/0xb0 exit_to_user_mode_prepare+0x1b3/0x1c0 syscall_exit_to_user_mode+0x19/0x50 do_syscall_64+0x48/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae The root case is in commit 84472b436e76 ("bpf, sockmap: Fix more uncharged while msg has more_data"), where I used msg->sg.size to replace the tosend, causing breakage: if (msg->apply_bytes && msg->apply_bytes < tosend) tosend = psock->apply_bytes;

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 5.16.19v ≥ 5.17.25.10.110 ≤ v < 5.10.1555.15.33 ≤ v < 5.15.795.16.19 ≤ v < 5.175.17.2 ≤ v < 5.185.17.2 ≤ v < 6.0.95.18 ≤ v < 6.0.95.18 ≤ v < 6.15.4.189 ≤ v < 5.4.225168ff181f5b6e7fce684c98a30d35da1dbf8f82a244ce90c8d0bd10ebf957da02c6f3fcd5d920bdf5.10.110 5.15.33 5.16.19 5.17.2 5.18 5.4.189 6.1 rc1 6.1 rc2 6.1 rc3 6.1 rc47b812a369e6416ab06d83cdd39d8e3f752781dd084472b436e760ba439e1969a9e3c5ae7c86de39d87d532d41ef937e16f61b3d2094f3a2ac49be365abb4caa477a5450817d2aa1198edce66450aecf8

Vendor states this is fixed in 14e8bc3bf7bd6af64d7538a0684c8238d96cdfd7 (fixed)

Vendor states this is fixed in 8ec95b94716a1e4d126edc3fb2bc426a717e2dba (fixed)

Vendor states this is fixed in 95adbd2ac8de82e43fd6b347e7e1b47f74dc1abb (fixed)

Vendor states this is fixed in cc21dc48a78cc9e5af9a4d039cd456446a6e73ff (fixed)

Vendor states this is fixed in d975bec1eaeb52341acc9273db79ddb078220399 (fixed)

Vendor states this is fixed in 5.10.155 (unaffected)

Vendor states this is fixed in 5.15.79 (unaffected)

Affected range stops below 5.17, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 5.18 (unaffected)

Vendor states this is fixed in 5.4.225 (unaffected)

Vendor states this is fixed in 6.0.9 (unaffected)

Vendor states this is fixed in 6.1 (unaffected)