CVE-2022-50168

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

bpf, x86: fix freeing of not-finalized bpf_prog_pack

syzbot reported a few issues with bpf_prog_pack [1], [2]. This only happens with multiple subprogs. In jit_subprogs(), we first call bpf_int_jit_compile() on each sub program. And then, we call it on each sub program again. jit_data is not freed in the first call of bpf_int_jit_compile(). Similarly we don't call bpf_jit_binary_pack_finalize() in the first call of bpf_int_jit_compile().

If bpf_int_jit_compile() failed for one sub program, we will call bpf_jit_binary_pack_finalize() for this sub program. However, we don't have a chance to call it for other sub programs. Then we will hit "goto out_free" in jit_subprogs(), and call bpf_jit_free on some subprograms that haven't got bpf_jit_binary_pack_finalize() yet.

At this point, bpf_jit_binary_pack_free() is called and the whole 2MB page is freed erroneously.

Fix this with a custom bpf_jit_free() for x86_64, which calls bpf_jit_binary_pack_finalize() if necessary. Also, with custom bpf_jit_free(), bpf_prog_aux->use_bpf_prog_pack is not needed any more, remove it.

[1] https://syzkaller.appspot.com/bug?extid=2f649ec6d2eea1495a8f [2] https://syzkaller.appspot.com/bug?extid=87f65c75f4a72db05445

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
11.4%
KEV
Not listed

Published

June 18, 2025

Last Modified

December 3, 2025

References (3)

Vendor Advisories for CVE-2022-50168(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat

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.

Data Freshness Timeline

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-50168?
CVE-2022-50168 is a high vulnerability published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: bpf, x86: fix freeing of not-finalized bpfprogpack syzbot reported a few issues with bpfprogpack [1], [2]. This only happens with multiple subprogs. In jitsubprogs(), we first call bpfintjitcompile() on each sub program. And then,…
When was CVE-2022-50168 disclosed?
CVE-2022-50168 was first published in the National Vulnerability Database on June 18, 2025, with the most recent update on December 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50168 actively exploited?
CVE-2022-50168 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-50168?
CVE-2022-50168 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-50168?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50168, 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-50168

Explore →

Is Your Infrastructure Affected by CVE-2022-50168?

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

Start Free Scan →Browse All CVEs