CVE-2022-49209

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-03-18. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full

If tcp_bpf_sendmsg() is running while sk msg is full. When sk_msg_alloc() returns -ENOMEM error, tcp_bpf_sendmsg() goes to wait_for_memory. If partial memory has been alloced by sk_msg_alloc(), that is, msg_tx->sg.size is greater than osize after sk_msg_alloc(), memleak occurs. To fix we use sk_msg_trim() to release the allocated memory, then goto wait for memory.

Other call paths of sk_msg_alloc() have the similar issue, such as tls_sw_sendmsg(), so handle sk_msg_trim logic inside sk_msg_alloc(), as Cong Wang suggested.

This issue can cause the following info: WARNING: CPU: 3 PID: 7950 at net/core/stream.c:208 sk_stream_kill_queues+0xd4/0x1a0 Call Trace: 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 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

WARNING: CPU: 3 PID: 2094 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x13c/0x260 Call Trace: __sk_destruct+0x24/0x1f0 sk_psock_destroy+0x19b/0x1c0 process_one_work+0x1b3/0x3c0 kthread+0xe6/0x110 ret_from_fork+0x22/0x30

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
16.9%
KEV
Not listed

Published

February 26, 2025

Last Modified

October 1, 2025

References (6)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.4.189—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:41 UTCOSV refresh
  2. 2026-07-24 14:15 UTCEPSS rescore
  3. 2026-07-23 14:16 UTCEPSS rescore
  4. 2026-07-23 14:16 UTCEPSS rescore
  5. 2026-07-23 02:16 UTCEG score recompute
  6. 2026-07-22 23:04 UTCEG score recompute
  7. 2026-07-22 14:06 UTCEPSS rescore
  8. 2026-07-22 14:06 UTCEPSS rescore
  9. 2026-07-21 15:23 UTCEPSS rescore
  10. 2026-07-21 15:23 UTCEPSS rescore
  11. 2026-07-20 17:05 UTCEPSS rescore
  12. 2026-07-19 14:29 UTCEPSS rescore
  13. 2026-07-19 14:29 UTCEPSS rescore
  14. 2026-07-19 02:27 UTCEPSS rescore
  15. 2026-07-19 02:27 UTCEPSS rescore
  16. 2026-07-18 10:03 UTCEPSS rescore
  17. 2026-07-18 10:03 UTCEPSS rescore
  18. 2026-07-16 17:00 UTCEPSS rescore
  19. 2026-07-15 16:56 UTCEPSS rescore
  20. 2026-07-15 16:56 UTCEPSS rescore
  21. 2026-07-15 01:58 UTCEPSS rescore
  22. 2026-07-15 01:58 UTCEPSS rescore
  23. 2026-07-13 22:28 UTCEPSS rescore
  24. 2026-07-13 22:28 UTCEPSS rescore
  25. 2026-07-13 06:11 UTCEPSS rescore
Show 65 more
  1. 2026-07-13 06:11 UTCEPSS rescore
  2. 2026-07-12 05:44 UTCEPSS rescore
  3. 2026-07-11 08:25 UTCEPSS rescore
  4. 2026-07-11 08:25 UTCEPSS rescore
  5. 2026-07-09 19:08 UTCEPSS rescore
  6. 2026-07-08 15:13 UTCEPSS rescore
  7. 2026-07-07 13:44 UTCEPSS rescore
  8. 2026-07-07 09:51 UTCOSV refresh
  9. 2026-07-06 16:25 UTCEPSS rescore
  10. 2026-07-06 02:21 UTCEPSS rescore
  11. 2026-07-05 02:28 UTCEPSS rescore
  12. 2026-07-04 06:29 UTCEPSS rescore
  13. 2026-07-01 15:04 UTCEPSS rescore
  14. 2026-06-30 23:21 UTCEPSS rescore
  15. 2026-06-30 23:20 UTCEPSS rescore
  16. 2026-06-29 14:04 UTCEPSS rescore
  17. 2026-06-28 14:06 UTCEPSS rescore
  18. 2026-06-28 04:54 UTCEPSS rescore
  19. 2026-06-28 04:54 UTCEPSS rescore
  20. 2026-06-27 03:07 UTCEPSS rescore
  21. 2026-06-27 03:07 UTCEPSS rescore
  22. 2026-06-25 13:48 UTCEPSS rescore
  23. 2026-06-25 13:48 UTCEPSS rescore
  24. 2026-06-24 14:03 UTCEPSS rescore
  25. 2026-06-24 14:03 UTCEPSS rescore
  26. 2026-06-23 21:31 UTCEPSS rescore
  27. 2026-06-23 21:31 UTCEPSS rescore
  28. 2026-06-22 14:24 UTCEPSS rescore
  29. 2026-06-21 14:55 UTCEPSS rescore
  30. 2026-06-21 14:55 UTCEPSS rescore
  31. 2026-06-21 01:58 UTCEPSS rescore
  32. 2026-06-21 01:58 UTCEPSS rescore
  33. 2026-06-19 19:24 UTCEPSS rescore
  34. 2026-06-19 19:24 UTCEPSS rescore
  35. 2026-06-18 21:05 UTCOSV refresh
  36. 2026-06-18 17:51 UTCEPSS rescore
  37. 2026-06-18 17:51 UTCEPSS rescore
  38. 2026-06-17 17:51 UTCEPSS rescore
  39. 2026-06-17 17:51 UTCEPSS rescore
  40. 2026-06-16 17:51 UTCEPSS rescore
  41. 2026-06-16 17:51 UTCEPSS rescore
  42. 2026-06-15 17:47 UTCEPSS rescore
  43. 2026-06-14 23:16 UTCEPSS rescore
  44. 2026-06-13 22:59 UTCEPSS rescore
  45. 2026-06-12 23:10 UTCEPSS rescore
  46. 2026-06-12 23:10 UTCEPSS rescore
  47. 2026-06-11 13:58 UTCEPSS rescore
  48. 2026-06-11 13:58 UTCEPSS rescore
  49. 2026-06-08 14:15 UTCEPSS rescore
  50. 2026-06-08 14:15 UTCEPSS rescore
  51. 2026-06-07 15:23 UTCEPSS rescore
  52. 2026-06-07 15:23 UTCEPSS rescore
  53. 2026-06-05 22:46 UTCEPSS rescore
  54. 2026-06-05 22:46 UTCEPSS rescore
  55. 2026-06-04 13:11 UTCEPSS rescore
  56. 2026-06-02 20:12 UTCEPSS rescore
  57. 2026-06-02 20:12 UTCEPSS rescore
  58. 2026-06-01 13:50 UTCEPSS rescore
  59. 2026-06-01 13:50 UTCEPSS rescore
  60. 2026-05-31 22:29 UTCEPSS rescore
  61. 2026-05-31 22:29 UTCEPSS rescore
  62. 2026-05-30 11:06 UTCEG score recompute
  63. 2026-05-30 11:06 UTCGHSA enrichment
  64. 2026-05-29 20:20 UTCOSV refresh
  65. 2026-05-29 13:43 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-49209?
CVE-2022-49209 is a medium vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix memleak in tcpbpfsendmsg while sk msg is full If tcpbpfsendmsg() is running while sk msg is full. When skmsgalloc() returns -ENOMEM error, tcpbpfsendmsg() goes to waitformemory. If partial memory has been alloced…
When was CVE-2022-49209 disclosed?
CVE-2022-49209 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on October 1, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49209 actively exploited?
CVE-2022-49209 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-49209?
CVE-2022-49209 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49209?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49209, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-49209

Explore →

Is Your Infrastructure Affected by CVE-2022-49209?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs