CVE-2022-50626

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: Exploit: NoneExposed: 0

A fix is available — apply it.

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

media: dvb-usb: fix memory leak in dvb_usb_adapter_init()

Syzbot reports a memory leak in "dvb_usb_adapter_init()". The leak is due to not accounting for and freeing current iteration's adapter->priv in case of an error. Currently if an error occurs, it will exit before incrementing "num_adapters_initalized", which is used as a reference counter to free all adap->priv in "dvb_usb_adapter_exit()". There are multiple error paths that can exit from before incrementing the counter. Including the error handling paths for "dvb_usb_adapter_stream_init()", "dvb_usb_adapter_dvb_init()" and "dvb_usb_adapter_frontend_init()" within "dvb_usb_adapter_init()".

This means that in case of an error in any of these functions the current iteration is not accounted for and the current iteration's adap->priv is not freed.

Fix this by freeing the current iteration's adap->priv in the "stream_init_err:" label in the error path. The rest of the (accounted for) adap->priv objects are freed in dvb_usb_adapter_exit() as expected using the num_adapters_initalized variable.

Syzbot report:

BUG: memory leak unreferenced object 0xffff8881172f1a00 (size 512): comm "kworker/0:2", pid 139, jiffies 4294994873 (age 10.960s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [] dvb_usb_adapter_init drivers/media/usb/dvb-usb/dvb-usb-init.c:75 [inline] [] dvb_usb_init drivers/media/usb/dvb-usb/dvb-usb-init.c:184 [inline] [] dvb_usb_device_init.cold+0x4e5/0x79e drivers/media/usb/dvb-usb/dvb-usb-init.c:308 [] dib0700_probe+0x8d/0x1b0 drivers/media/usb/dvb-usb/dib0700_core.c:883 [] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396 [] call_driver_probe drivers/base/dd.c:542 [inline] [] really_probe.part.0+0xe7/0x310 drivers/base/dd.c:621 [] really_probe drivers/base/dd.c:583 [inline] [] __driver_probe_device+0x10c/0x1e0 drivers/base/dd.c:752 [] driver_probe_device+0x2a/0x120 drivers/base/dd.c:782 [] __device_attach_driver+0xf6/0x140 drivers/base/dd.c:899 [] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:427 [] __device_attach+0x122/0x260 drivers/base/dd.c:970 [] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:487 [] device_add+0x5fb/0xdf0 drivers/base/core.c:3405 [] usb_set_configuration+0x8f2/0xb80 drivers/usb/core/message.c:2170 [] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238 [] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293 [] call_driver_probe drivers/base/dd.c:542 [inline] [] really_probe.part.0+0xe7/0x310 drivers/base/dd.c:621 [] really_probe drivers/base/dd.c:583 [inline] [] __driver_probe_device+0x10c/0x1e0 drivers/base/dd.c:752

CVSS v3
EG Score
0.0(none)
EG Risk
EPSS
10.4%
KEV
Not listed

Published

December 8, 2025

Last Modified

April 15, 2026

Vendor Advisories for CVE-2022-50626(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 4.9.337osv

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 13× in last 7d / 46× 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 133 total refreshes for this CVE.

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

Frequently asked(4)

What is CVE-2022-50626?
CVE-2022-50626 is a none vulnerability published on December 8, 2025. In the Linux kernel, the following vulnerability has been resolved: media: dvb-usb: fix memory leak in dvbusbadapter_init() Syzbot reports a memory leak in "dvbusbadapter_init()". The leak is due to not accounting for and freeing current iteration's adapter->priv in case of an error. Currently if…
When was CVE-2022-50626 disclosed?
CVE-2022-50626 was first published in the National Vulnerability Database on December 8, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50626 actively exploited?
CVE-2022-50626 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2022-50626?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50626, 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-50626

Explore →

Is Your Infrastructure Affected by CVE-2022-50626?

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