# CVE-2022-49877: bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues

Status: published. Published: 2025-05-01. Updated: 2026-11-05.

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;

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 244ce90c8d0bd10ebf957da02c6f3fcd5d920bdf; < d975bec1eaeb52341acc9273db79ddb078220399 (affected, git); ≥ 7b812a369e6416ab06d83cdd39d8e3f752781dd0; < cc21dc48a78cc9e5af9a4d039cd456446a6e73ff (affected, git); ≥ 168ff181f5b6e7fce684c98a30d35da1dbf8f82a; < 95adbd2ac8de82e43fd6b347e7e1b47f74dc1abb (affected, git); ≥ 84472b436e760ba439e1969a9e3c5ae7c86de39d; < 14e8bc3bf7bd6af64d7538a0684c8238d96cdfd7 (affected, git); ≥ 84472b436e760ba439e1969a9e3c5ae7c86de39d; < 8ec95b94716a1e4d126edc3fb2bc426a717e2dba (affected, git); 87d532d41ef937e16f61b3d2094f3a2ac49be365 (affected, git); abb4caa477a5450817d2aa1198edce66450aecf8 (affected, git); ≥ 5.4.189; < 5.4.225 (affected, semver); ≥ 5.10.110; < 5.10.155 (affected, semver); ≥ 5.15.33; < 5.15.79 (affected, semver); ≥ 5.16.19; < 5.17 (affected, semver); ≥ 5.17.2; < 5.18 (affected, semver). Source: CNA: Linux
- Linux / Linux: 5.18 (affected); ≥ 0; < 5.18 (unaffected, semver); ≥ 5.4.225; ≤ 5.4.* (unaffected, semver); ≥ 5.10.155; ≤ 5.10.* (unaffected, semver); ≥ 5.15.79; ≤ 5.15.* (unaffected, semver); ≥ 6.0.9; ≤ 6.0.* (unaffected, semver); ≥ 6.1; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.20% as of 2026-11-05; percentile 10.16%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/d975bec1eaeb52341acc9273db79ddb078220399 (CNA: Linux)

- https://git.kernel.org/stable/c/cc21dc48a78cc9e5af9a4d039cd456446a6e73ff (CNA: Linux)

- https://git.kernel.org/stable/c/95adbd2ac8de82e43fd6b347e7e1b47f74dc1abb (CNA: Linux)

- https://git.kernel.org/stable/c/14e8bc3bf7bd6af64d7538a0684c8238d96cdfd7 (CNA: Linux)

- https://git.kernel.org/stable/c/8ec95b94716a1e4d126edc3fb2bc426a717e2dba (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2022-49877; retrieved 2026-11-05; source updated 2026-11-05

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2022-49877; retrieved 2026-11-05; source updated Not reported

Revision: c7faaccadbac0306714c5531454b84b714c2230cd6f99ae67cc46f56c8dc7c11

Canonical: https://y2.dev/cve/CVE-2022-49877

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.