CVE-2022-50373

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

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

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

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

Also known asEUVD-2022-55625 (ENISA EUVD) · GHSA-wp8q-4m36-3vr3 (GitHub Security Advisories)Source: ENISA EUVD

4.7EG
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.4%CVSS: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

fs: dlm: fix race in lowcomms

This patch fixes a race between queue_work() in _dlm_lowcomms_commit_msg() and srcu_read_unlock(). The queue_work() can take the final reference of a dlm_msg and so msg->idx can contain garbage which is signaled by the following warning:

[ 676.237050] ------------[ cut here ]------------ [ 676.237052] WARNING: CPU: 0 PID: 1060 at include/linux/srcu.h:189 dlm_lowcomms_commit_msg+0x41/0x50 [ 676.238945] Modules linked in: dlm_locktorture torture rpcsec_gss_krb5 intel_rapl_msr intel_rapl_common iTCO_wdt iTCO_vendor_support qxl kvm_intel drm_ttm_helper vmw_vsock_virtio_transport kvm vmw_vsock_virtio_transport_common ttm irqbypass crc32_pclmul joydev crc32c_intel serio_raw drm_kms_helper vsock virtio_scsi virtio_console virtio_balloon snd_pcm drm syscopyarea sysfillrect sysimgblt snd_timer fb_sys_fops i2c_i801 lpc_ich snd i2c_smbus soundcore pcspkr [ 676.244227] CPU: 0 PID: 1060 Comm: lock_torture_wr Not tainted 5.19.0-rc3+ #1546 [ 676.245216] Hardware name: Red Hat KVM/RHEL-AV, BIOS 1.16.0-2.module+el8.7.0+15506+033991b0 04/01/2014 [ 676.246460] RIP: 0010:dlm_lowcomms_commit_msg+0x41/0x50 [ 676.247132] Code: fe ff ff ff 75 24 48 c7 c6 bd 0f 49 bb 48 c7 c7 38 7c 01 bd e8 00 e7 ca ff 89 de 48 c7 c7 60 78 01 bd e8 42 3d cd ff 5b 5d c3 <0f> 0b eb d8 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 [ 676.249253] RSP: 0018:ffffa401c18ffc68 EFLAGS: 00010282 [ 676.249855] RAX: 0000000000000001 RBX: 00000000ffff8b76 RCX: 0000000000000006 [ 676.250713] RDX: 0000000000000000 RSI: ffffffffbccf3a10 RDI: ffffffffbcc7b62e [ 676.251610] RBP: ffffa401c18ffc70 R08: 0000000000000001 R09: 0000000000000001 [ 676.252481] R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000005 [ 676.253421] R13: ffff8b76786ec370 R14: ffff8b76786ec370 R15: ffff8b76786ec480 [ 676.254257] FS: 0000000000000000(0000) GS:ffff8b7777800000(0000) knlGS:0000000000000000 [ 676.255239] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 676.255897] CR2: 00005590205d88b8 CR3: 000000017656c003 CR4: 0000000000770ee0 [ 676.256734] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 676.257567] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 676.258397] PKRU: 55555554 [ 676.258729] Call Trace: [ 676.259063] [ 676.259354] dlm_midcomms_commit_mhandle+0xcc/0x110 [ 676.259964] queue_bast+0x8b/0xb0 [ 676.260423] grant_pending_locks+0x166/0x1b0 [ 676.261007] _unlock_lock+0x75/0x90 [ 676.261469] unlock_lock.isra.57+0x62/0xa0 [ 676.262009] dlm_unlock+0x21e/0x330 [ 676.262457] ? lock_torture_stats+0x80/0x80 [dlm_locktorture] [ 676.263183] torture_unlock+0x5a/0x90 [dlm_locktorture] [ 676.263815] ? preempt_count_sub+0xba/0x100 [ 676.264361] ? complete+0x1d/0x60 [ 676.264777] lock_torture_writer+0xb8/0x150 [dlm_locktorture] [ 676.265555] kthread+0x10a/0x130 [ 676.266007] ? kthread_complete_and_exit+0x20/0x20 [ 676.266616] ret_from_fork+0x22/0x30 [ 676.267097] [ 676.267381] irq event stamp: 9579855 [ 676.267824] hardirqs last enabled at (9579863): [] __up_console_sem+0x58/0x60 [ 676.268896] hardirqs last disabled at (9579872): [] __up_console_sem+0x3d/0x60 [ 676.270008] softirqs last enabled at (9579798): [] __do_softirq+0x349/0x4c7 [ 676.271438] softirqs last disabled at (9579897): [] irq_exit_rcu+0xb0/0xf0 [ 676.272796] ---[ end trace 0000000000000000 ]---

I reproduced this warning with dlm_locktorture test which is currently not upstream. However this patch fix the issue by make a additional refcount between dlm_lowcomms_new_msg() and dlm_lowcomms_commit_msg(). In case of the race the kref_put() in dlm_lowcomms_commit_msg() will be the final put.

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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.4%
EPSS %ILE
34th
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 (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% 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 17, 2025

Last Modified

August 5, 2026

References (4)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.15.75 (fixes >=5.14.0)—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 rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 37× 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 98 of 195 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 97 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-50373?
CVE-2022-50373 is a medium-severity vulnerability; its CVE record was published on September 17, 2025. In the Linux kernel, the following vulnerability has been resolved: fs: dlm: fix race in lowcomms This patch fixes a race between queue_work() in _dlm_lowcomms_commit_msg() and srcu_read_unlock(). The queue_work() can take the final reference of a dlm_msg and so msg->idx can contain garbage which…
When was the CVE record for CVE-2022-50373 published?
The CVE record for CVE-2022-50373 was published on September 17, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2022-50373 actively exploited?
CVE-2022-50373 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50373?
CVE-2022-50373 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2022-50373?
A fix for CVE-2022-50373 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-50373?

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

Book a Demo →Browse All CVEs