Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-49204bpf, sockmap: Fix more uncharged while msg has more_data

Description

In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix more uncharged while msg has more_data In tcp_bpf_send_verdict(), if msg has more data after tcp_bpf_sendmsg_redir(): tcp_bpf_send_verdict() tosend = msg->sg.size //msg->sg.size = 22220 case __SK_REDIRECT: sk_msg_return() //uncharged msg->sg.size(22220) sk->sk_forward_alloc tcp_bpf_sendmsg_redir() //after tcp_bpf_sendmsg_redir, msg->sg.size=11000 goto more_data; tosend = msg->sg.size //msg->sg.size = 11000 case __SK_REDIRECT: sk_msg_return() //uncharged msg->sg.size(11000) to sk->sk_forward_alloc The msg->sg.size(11000) has been uncharged twice, to fix we can charge the remaining msg->sg.size before goto more data. This issue can cause the following info: WARNING: CPU: 0 PID: 9860 at net/core/stream.c:208 sk_stream_kill_queues+0xd4/0x1a0 Call Trace: <TASK> inet_csk_destroy_sock+0x55/0x110 __tcp_close+0x279/0x470 tcp_close+0x1f/0x60 inet_release+0x3f/0x80 __sock_release+0x3d/0xb0 sock_close+0x11/0x20 __fput+0x92/0x250 task_work_run+0x6a/0xa0 do_exit+0x33b/0xb60 do_group_exit+0x2f/0xa0 get_signal+0xb6/0x950 arch_do_signal_or_restart+0xac/0x2a0 ? vfs_write+0x237/0x290 exit_to_user_mode_prepare+0xa9/0x200 syscall_exit_to_user_mode+0x12/0x30 do_syscall_64+0x46/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae </TASK> WARNING: CPU: 0 PID: 2136 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x13c/0x260 Call Trace: <TASK> __sk_destruct+0x24/0x1f0 sk_psock_destroy+0x19b/0x1c0 process_one_work+0x1b3/0x3c0 worker_thread+0x30/0x350 ? process_one_work+0x3c0/0x3c0 kthread+0xe6/0x110 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK>

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 21 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

CVSS scores of CVE-2022-49204, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.27% · top 81% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < 244ce90c8d0bd10ebf957da02c6f3fcd5d920bdf
    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < 7b812a369e6416ab06d83cdd39d8e3f752781dd0
    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < 168ff181f5b6e7fce684c98a30d35da1dbf8f82a
    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < 87d532d41ef937e16f61b3d2094f3a2ac49be365
    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < abb4caa477a5450817d2aa1198edce66450aecf8
    • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < 84472b436e760ba439e1969a9e3c5ae7c86de39d
  • Linux · Linux

    • affected 4.20
    • unaffected < 4.20
    • unaffected 5.4.189 – ≤ 5.4.*
    • unaffected 5.10.110 – ≤ 5.10.*
    • unaffected 5.15.33 – ≤ 5.15.*
    • unaffected 5.16.19 – ≤ 5.16.*
    • unaffected 5.17.2 – ≤ 5.17.*
    • unaffected 5.18 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49204 badge
[![CVE-2022-49204](https://cveledger.app/badge/CVE-2022-49204.svg)](https://cveledger.app/cve/CVE-2022-49204)

Record last updated .