CVE-2022-50536

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-10-07. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

bpf, sockmap: Fix repeated calls to sock_put() when msg has more_data

In tcp_bpf_send_verdict() redirection, the eval variable is assigned to __SK_REDIRECT after the apply_bytes data is sent, if msg has more_data, sock_put() will be called multiple times.

We should reset the eval variable to __SK_NONE every time more_data starts.

This causes:

IPv4: Attempt to release TCP socket in state 1 00000000b4c925d7 ------------[ cut here ]------------ refcount_t: addition on 0; use-after-free. WARNING: CPU: 5 PID: 4482 at lib/refcount.c:25 refcount_warn_saturate+0x7d/0x110 Modules linked in: CPU: 5 PID: 4482 Comm: sockhash_bypass Kdump: loaded Not tainted 6.0.0 #1 Hardware name: Red Hat KVM, BIOS 1.11.0-2.el7 04/01/2014 Call Trace: __tcp_transmit_skb+0xa1b/0xb90 ? __alloc_skb+0x8c/0x1a0 ? __kmalloc_node_track_caller+0x184/0x320 tcp_write_xmit+0x22a/0x1110 __tcp_push_pending_frames+0x32/0xf0 do_tcp_sendpages+0x62d/0x640 tcp_bpf_push+0xae/0x2c0 tcp_bpf_sendmsg_redir+0x260/0x410 ? preempt_count_add+0x70/0xa0 tcp_bpf_send_verdict+0x386/0x4b0 tcp_bpf_sendmsg+0x21b/0x3b0 sock_sendmsg+0x58/0x70 __sys_sendto+0xfa/0x170 ? xfd_validate_state+0x1d/0x80 ? switch_fpu_return+0x59/0xe0 __x64_sys_sendto+0x24/0x30 do_syscall_64+0x37/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

October 7, 2025

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

bpf, sockmap: Fix repeated calls to sock_put() when msg has more_data - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7a9841ca025275b5b0edfb0b618934abb6ceec15
generic

bpf, sockmap: Fix repeated calls to sock_put() when msg has more_data - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/113236e8f49f262f318c00ebb14b15f4834e87c1
generic

bpf, sockmap: Fix repeated calls to sock_put() when msg has more_data - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/578a7628b838a3ac8ad61deaab5a816ff032ac13
generic

bpf, sockmap: Fix repeated calls to sock_put() when msg has more_data - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8786bde11a4f31b63b3036731df0b47337a7a245
generic

bpf, sockmap: Fix repeated calls to sock_put() when msg has more_data - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28e4a763cd4a2b1a78852216ef4bd7df3a05cec6
generic

bpf, sockmap: Fix repeated calls to sock_put() when msg has more_data - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7508b9f4daac4ec7dfe0b6fb2d688b1c1c105e10

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
redhatkernel-0:5.14.0-162.6.1.el9_12022-11-15redhat
redhatkernel-0:4.18.0-372.9.1.el82022-05-10redhat
linuxKernel @ 5.4.229osv

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (25 versions)5.10.178-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.4-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.1.4-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.1.4-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 25× 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.

Showing the most recent 100 of 145 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2022-50536?
CVE-2022-50536 is a high vulnerability published on October 7, 2025. In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix repeated calls to sockput() when msg has moredata In tcpbpfsend_verdict() redirection, the eval variable is assigned to SKREDIRECT after the applybytes data is sent, if msg has more_data, sock_put() will be called…
When was CVE-2022-50536 disclosed?
CVE-2022-50536 was first published in the National Vulnerability Database on October 7, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50536 actively exploited?
CVE-2022-50536 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.7% of all scored CVEs.
What is the CVSS score of CVE-2022-50536?
CVE-2022-50536 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-50536?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50536, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-50536

Explore →

Is Your Infrastructure Affected by CVE-2022-50536?

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