CVE-2022-50752

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-24. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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:

md/raid5: Remove unnecessary bio_put() in raid5_read_one_chunk()

When running chunk-sized reads on disks with badblocks duplicate bio free/puts are observed:

============================================================================= BUG bio-200 (Not tainted): Object already free ----------------------------------------------------------------------------- Allocated in mempool_alloc_slab+0x17/0x20 age=3 cpu=2 pid=7504 __slab_alloc.constprop.0+0x5a/0xb0 kmem_cache_alloc+0x31e/0x330 mempool_alloc_slab+0x17/0x20 mempool_alloc+0x100/0x2b0 bio_alloc_bioset+0x181/0x460 do_mpage_readpage+0x776/0xd00 mpage_readahead+0x166/0x320 blkdev_readahead+0x15/0x20 read_pages+0x13f/0x5f0 page_cache_ra_unbounded+0x18d/0x220 force_page_cache_ra+0x181/0x1c0 page_cache_sync_ra+0x65/0xb0 filemap_get_pages+0x1df/0xaf0 filemap_read+0x1e1/0x700 blkdev_read_iter+0x1e5/0x330 vfs_read+0x42a/0x570 Freed in mempool_free_slab+0x17/0x20 age=3 cpu=2 pid=7504 kmem_cache_free+0x46d/0x490 mempool_free_slab+0x17/0x20 mempool_free+0x66/0x190 bio_free+0x78/0x90 bio_put+0x100/0x1a0 raid5_make_request+0x2259/0x2450 md_handle_request+0x402/0x600 md_submit_bio+0xd9/0x120 __submit_bio+0x11f/0x1b0 submit_bio_noacct_nocheck+0x204/0x480 submit_bio_noacct+0x32e/0xc70 submit_bio+0x98/0x1a0 mpage_readahead+0x250/0x320 blkdev_readahead+0x15/0x20 read_pages+0x13f/0x5f0 page_cache_ra_unbounded+0x18d/0x220 Slab 0xffffea000481b600 objects=21 used=0 fp=0xffff8881206d8940 flags=0x17ffffc0010201(locked|slab|head|node=0|zone=2|lastcpupid=0x1fffff) CPU: 0 PID: 34525 Comm: kworker/u24:2 Not tainted 6.0.0-rc2-localyes-265166-gf11c5343fa3f #143 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014 Workqueue: raid5wq raid5_do_work Call Trace: dump_stack_lvl+0x5a/0x78 dump_stack+0x10/0x16 print_trailer+0x158/0x165 object_err+0x35/0x50 free_debug_processing.cold+0xb7/0xbe __slab_free+0x1ae/0x330 kmem_cache_free+0x46d/0x490 mempool_free_slab+0x17/0x20 mempool_free+0x66/0x190 bio_free+0x78/0x90 bio_put+0x100/0x1a0 mpage_end_io+0x36/0x150 bio_endio+0x2fd/0x360 md_end_io_acct+0x7e/0x90 bio_endio+0x2fd/0x360 handle_failed_stripe+0x960/0xb80 handle_stripe+0x1348/0x3760 handle_active_stripes.constprop.0+0x72a/0xaf0 raid5_do_work+0x177/0x330 process_one_work+0x616/0xb20 worker_thread+0x2bd/0x6f0 kthread+0x179/0x1b0 ret_from_fork+0x22/0x30

The double free is caused by an unnecessary bio_put() in the if(is_badblock(...)) error path in raid5_read_one_chunk().

The error path was moved ahead of bio_alloc_clone() in c82aa1b76787c ("md/raid5: move checking badblock before clone bio in raid5_read_one_chunk"). The previous code checked and freed align_bio which required a bio_put. After the move that is no longer needed as raid_bio is returned to the control of the common io path which performs its own endio resulting in a double free on bad device blocks.

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

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (4)

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

md/raid5: Remove unnecessary bio_put() in raid5_read_one_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c66a6f41e09ad386fd2cce22b9cded837bbbc704
generic

md/raid5: Remove unnecessary bio_put() in raid5_read_one_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c0fd5d4d8fd7b1a50306d7a23c720cf808f41fdf
generic

md/raid5: Remove unnecessary bio_put() in raid5_read_one_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

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

md/raid5: Remove unnecessary bio_put() in raid5_read_one_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21a9c7354aa59e97e26ece5f0a609c8bfa43020d

Vendor Advisories for CVE-2022-50752(3)

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-477.10.1.el8_82023-05-16redhat
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat
linuxKernel @ 5.15.75—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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—

Data Freshness Timeline

(refreshed 5× in last 7d / 24× 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 205 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2022-50752?
CVE-2022-50752 is a high vulnerability published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: md/raid5: Remove unnecessary bioput() in raid5readonechunk() When running chunk-sized reads on disks with badblocks duplicate bio free/puts are observed: =============================================================================…
When was CVE-2022-50752 disclosed?
CVE-2022-50752 was first published in the National Vulnerability Database on December 24, 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-50752 actively exploited?
CVE-2022-50752 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 91.1% of all scored CVEs.
What is the CVSS score of CVE-2022-50752?
CVE-2022-50752 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2022-50752?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50752, 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-50752

Explore →

Is Your Infrastructure Affected by CVE-2022-50752?

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

Start Free Scan →Browse All CVEs