CVE-2022-50381

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-29984 (ENISA EUVD) · GHSA-qr3p-w2mh-mg9q (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

md: fix a crash in mempool_free

There's a crash in mempool_free when running the lvm test shell/lvchange-rebuild-raid.sh.

The reason for the crash is this: * super_written calls atomic_dec_and_test(&mddev->pending_writes) and wake_up(&mddev->sb_wait). Then it calls rdev_dec_pending(rdev, mddev) and bio_put(bio). * so, the process that waited on sb_wait and that is woken up is racing with bio_put(bio). * if the process wins the race, it calls bioset_exit before bio_put(bio) is executed. * bio_put(bio) attempts to free a bio into a destroyed bio set - causing a crash in mempool_free.

We fix this bug by moving bio_put before atomic_dec_and_test.

We also move rdev_dec_pending before atomic_dec_and_test as suggested by Neil Brown.

The function md_end_flush has a similar bug - we must call bio_put before we decrement the number of in-progress bios.

BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 11557f0067 P4D 11557f0067 PUD 0 Oops: 0002 [#1] PREEMPT SMP CPU: 0 PID: 73 Comm: kworker/0:1 Not tainted 6.1.0-rc3 #5 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 Workqueue: kdelayd flush_expired_bios [dm_delay] RIP: 0010:mempool_free+0x47/0x80 Code: 48 89 ef 5b 5d ff e0 f3 c3 48 89 f7 e8 32 45 3f 00 48 63 53 08 48 89 c6 3b 53 04 7d 2d 48 8b 43 10 8d 4a 01 48 89 df 89 4b 08 <48> 89 2c d0 e8 b0 45 3f 00 48 8d 7b 30 5b 5d 31 c9 ba 01 00 00 00 RSP: 0018:ffff88910036bda8 EFLAGS: 00010093 RAX: 0000000000000000 RBX: ffff8891037b65d8 RCX: 0000000000000001 RDX: 0000000000000000 RSI: 0000000000000202 RDI: ffff8891037b65d8 RBP: ffff8891447ba240 R08: 0000000000012908 R09: 00000000003d0900 R10: 0000000000000000 R11: 0000000000173544 R12: ffff889101a14000 R13: ffff8891562ac300 R14: ffff889102b41440 R15: ffffe8ffffa00d05 FS: 0000000000000000(0000) GS:ffff88942fa00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000001102e99000 CR4: 00000000000006b0 Call Trace: clone_endio+0xf4/0x1c0 [dm_mod] clone_endio+0xf4/0x1c0 [dm_mod] __submit_bio+0x76/0x120 submit_bio_noacct_nocheck+0xb6/0x2a0 flush_expired_bios+0x28/0x2f [dm_delay] process_one_work+0x1b4/0x300 worker_thread+0x45/0x3e0 ? rescuer_thread+0x380/0x380 kthread+0xc2/0x100 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30 Modules linked in: brd dm_delay dm_raid dm_mod af_packet uvesafb cfbfillrect cfbimgblt cn cfbcopyarea fb font fbdev tun autofs4 binfmt_misc configfs ipv6 virtio_rng virtio_balloon rng_core virtio_net pcspkr net_failover failover qemu_fw_cfg button mousedev raid10 raid456 libcrc32c async_raid6_recov async_memcpy async_pq raid6_pq async_xor xor async_tx raid1 raid0 md_mod sd_mod t10_pi crc64_rocksoft crc64 virtio_scsi scsi_mod evdev psmouse bsg scsi_common [last unloaded: brd] CR2: 0000000000000000 ---[ end trace 0000000000000000 ]---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 18, 2025

Last Modified

January 14, 2026

References (9)

Vendor Advisories for CVE-2022-50381(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 / EcosystemFix (by version range) / 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 @ 4.9.337 (fixes >=2.6.13)—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (25 versions)
  • every version up to 5.10.178-1: fixed in 5.10.178-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.4-1: fixed in 6.1.4-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.4-1: fixed in 6.1.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.4-1: fixed in 6.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 / 36× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 191 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 94 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-50381?
CVE-2022-50381 is a medium-severity vulnerability; its CVE record was published on September 18, 2025. In the Linux kernel, the following vulnerability has been resolved: md: fix a crash in mempool_free There's a crash in mempool_free when running the lvm test shell/lvchange-rebuild-raid.sh. The reason for the crash is this: super_written calls atomic_dec_and_test(&mddev->pending_writes) and…
When was the CVE record for CVE-2022-50381 published?
The CVE record for CVE-2022-50381 was published on September 18, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of January 14, 2026; the record at its source may have been updated since.
Is CVE-2022-50381 actively exploited?
CVE-2022-50381 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50381?
CVE-2022-50381 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-50381?
A fix for CVE-2022-50381 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-50381 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-50381?

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

Book a Demo →Browse All CVEs