CVE-2022-49877
bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues
- Published
- Updated
- Reserved
- Assigned by
- Linux
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;
Timeline
ID reserved
By Linux
Published
- 18 months later
· 18 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.20% · top 90% of all CVEs (7 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 244ce90c8d0bd10ebf957da02c6f3fcd5d920bdf – < d975bec1eaeb52341acc9273db79ddb078220399
- affected 7b812a369e6416ab06d83cdd39d8e3f752781dd0 – < cc21dc48a78cc9e5af9a4d039cd456446a6e73ff
- affected 168ff181f5b6e7fce684c98a30d35da1dbf8f82a – < 95adbd2ac8de82e43fd6b347e7e1b47f74dc1abb
- affected 84472b436e760ba439e1969a9e3c5ae7c86de39d – < 14e8bc3bf7bd6af64d7538a0684c8238d96cdfd7
- affected 84472b436e760ba439e1969a9e3c5ae7c86de39d – < 8ec95b94716a1e4d126edc3fb2bc426a717e2dba
- affected 87d532d41ef937e16f61b3d2094f3a2ac49be365
- affected abb4caa477a5450817d2aa1198edce66450aecf8
- affected 5.4.189 – < 5.4.225
- affected 5.10.110 – < 5.10.155
- affected 5.15.33 – < 5.15.79
- affected 5.16.19 – < 5.17
- affected 5.17.2 – < 5.18
- affected 5.18
- unaffected < 5.18
- unaffected 5.4.225 – ≤ 5.4.*
- unaffected 5.10.155 – ≤ 5.10.*
- unaffected 5.15.79 – ≤ 5.15.*
- unaffected 6.0.9 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References (5)
- https://git.kernel.org/stable/c/d975bec1eaeb52341acc9273db79ddb078220399 (opens in a new tab)
- https://git.kernel.org/stable/c/cc21dc48a78cc9e5af9a4d039cd456446a6e73ff (opens in a new tab)
- https://git.kernel.org/stable/c/95adbd2ac8de82e43fd6b347e7e1b47f74dc1abb (opens in a new tab)
- https://git.kernel.org/stable/c/14e8bc3bf7bd6af64d7538a0684c8238d96cdfd7 (opens in a new tab)
- https://git.kernel.org/stable/c/8ec95b94716a1e4d126edc3fb2bc426a717e2dba (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-49877)Record last updated .