CVE-2022-49877 json
bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues
published 2025-05-01 18 mo ago modified 2026-11-05 3 d ago also EUVD-2025-12887
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
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;
Patch / fix
- Linux Linux 5.4.225, 5.10.155, 5.15.79, 5.17, 5.18, 6.0.9, 6.1
- linux Debian 14, Debian 13, Debian 12 6.0.10-1
debian advisories DEBIAN-CVE-2022-49877
- linux Ubuntu 20.04 LTS 5.4.0-144.161
- linux Ubuntu 22.04 LTS 5.15.0-67.74
- linux-aws Ubuntu 20.04 LTS 5.4.0-1097.105
- linux-aws Ubuntu 22.04 LTS 5.15.0-1031.35
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1101.110
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1030.37
- linux-gke Ubuntu 22.04 LTS 5.15.0-1028.33
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1045.50
ubuntu advisories UBUNTU-CVE-2022-49877
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-syms SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 4.12.14-122.261.1
- kernel-source SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 4.12.14-122.261.1
- kernel-default SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS, SLE Live Patching 12 SP5 4.12.14-122.261.1
- kgraft-patch-SLE12-SP5_Update_69 SLE Live Patching 12 SP5 1-8.3.1
suse advisories SUSE-SU-2025:01983-1
- git.kernel.org/stable/c/d975bec1eaeb52341acc9273db79ddb078220399 commit
- git.kernel.org/stable/c/cc21dc48a78cc9e5af9a4d039cd456446a6e73ff commit
- git.kernel.org/stable/c/95adbd2ac8de82e43fd6b347e7e1b47f74dc1abb commit
- git.kernel.org/stable/c/14e8bc3bf7bd6af64d7538a0684c8238d96cdfd7 commit
- git.kernel.org/stable/c/8ec95b94716a1e4d126edc3fb2bc426a717e2dba commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-49877 updated cvss 5.5
kernel: bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/d975bec1eaeb52341acc9273db79ddb078220399
patch
-
git.kernel.org
/stable/c/cc21dc48a78cc9e5af9a4d039cd456446a6e73ff
patch
-
git.kernel.org
/stable/c/95adbd2ac8de82e43fd6b347e7e1b47f74dc1abb
patch
-
git.kernel.org
/stable/c/14e8bc3bf7bd6af64d7538a0684c8238d96cdfd7
patch
-
git.kernel.org
/stable/c/8ec95b94716a1e4d126edc3fb2bc426a717e2dba
patch
Sources
- CVE List CVE-2022-49877
- NVD CVE-2022-49877
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.