CVE-2022-49337

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-22. 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-2022-54891 (ENISA EUVD) · GHSA-xw4w-p39h-frx8 (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:

ocfs2: dlmfs: fix error handling of user_dlm_destroy_lock

When user_dlm_destroy_lock failed, it didn't clean up the flags it set before exit. For USER_LOCK_IN_TEARDOWN, if this function fails because of lock is still in used, next time when unlink invokes this function, it will return succeed, and then unlink will remove inode and dentry if lock is not in used(file closed), but the dlm lock is still linked in dlm lock resource, then when bast come in, it will trigger a panic due to user-after-free. See the following panic call trace. To fix this, USER_LOCK_IN_TEARDOWN should be reverted if fail. And also error should be returned if USER_LOCK_IN_TEARDOWN is set to let user know that unlink fail.

For the case of ocfs2_dlm_unlock failure, besides USER_LOCK_IN_TEARDOWN, USER_LOCK_BUSY is also required to be cleared. Even though spin lock is released in between, but USER_LOCK_IN_TEARDOWN is still set, for USER_LOCK_BUSY, if before every place that waits on this flag, USER_LOCK_IN_TEARDOWN is checked to bail out, that will make sure no flow waits on the busy flag set by user_dlm_destroy_lock(), then we can simplely revert USER_LOCK_BUSY when ocfs2_dlm_unlock fails. Fix user_dlm_cluster_lock() which is the only function not following this.

[ 941.336392] (python,26174,16):dlmfs_unlink:562 ERROR: unlink 004fb0000060000b5a90b8c847b72e1, error -16 from destroy [ 989.757536] ------------[ cut here ]------------ [ 989.757709] kernel BUG at fs/ocfs2/dlmfs/userdlm.c:173! [ 989.757876] invalid opcode: 0000 [#1] SMP [ 989.758027] Modules linked in: ksplice_2zhuk2jr_ib_ipoib_new(O) ksplice_2zhuk2jr(O) mptctl mptbase xen_netback xen_blkback xen_gntalloc xen_gntdev xen_evtchn cdc_ether usbnet mii ocfs2 jbd2 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfsv3 nfs_acl nfs fscache lockd grace ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs bnx2fc fcoe libfcoe libfc scsi_transport_fc sunrpc ipmi_devintf bridge stp llc rds_rdma rds bonding ib_sdp ib_ipoib rdma_ucm ib_ucm ib_uverbs ib_umad rdma_cm ib_cm iw_cm falcon_lsm_serviceable(PE) falcon_nf_netcontain(PE) mlx4_vnic falcon_kal(E) falcon_lsm_pinned_13402(E) mlx4_ib ib_sa ib_mad ib_core ib_addr xenfs xen_privcmd dm_multipath iTCO_wdt iTCO_vendor_support pcspkr sb_edac edac_core i2c_i801 lpc_ich mfd_core ipmi_ssif i2c_core ipmi_si ipmi_msghandler [ 989.760686] ioatdma sg ext3 jbd mbcache sd_mod ahci libahci ixgbe dca ptp pps_core vxlan udp_tunnel ip6_udp_tunnel megaraid_sas mlx4_core crc32c_intel be2iscsi bnx2i cnic uio cxgb4i cxgb4 cxgb3i libcxgbi ipv6 cxgb3 mdio libiscsi_tcp qla4xxx iscsi_boot_sysfs libiscsi scsi_transport_iscsi wmi dm_mirror dm_region_hash dm_log dm_mod [last unloaded: ksplice_2zhuk2jr_ib_ipoib_old] [ 989.761987] CPU: 10 PID: 19102 Comm: dlm_thread Tainted: P OE 4.1.12-124.57.1.el6uek.x86_64 #2 [ 989.762290] Hardware name: Oracle Corporation ORACLE SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30350100 06/17/2021 [ 989.762599] task: ffff880178af6200 ti: ffff88017f7c8000 task.ti: ffff88017f7c8000 [ 989.762848] RIP: e030:[] [] __user_dlm_queue_lockres.part.4+0x76/0x80 [ocfs2_dlmfs] [ 989.763185] RSP: e02b:ffff88017f7cbcb8 EFLAGS: 00010246 [ 989.763353] RAX: 0000000000000000 RBX: ffff880174d48008 RCX: 0000000000000003 [ 989.763565] RDX: 0000000000120012 RSI: 0000000000000003 RDI: ffff880174d48170 [ 989.763778] RBP: ffff88017f7cbcc8 R08: ffff88021f4293b0 R09: 0000000000000000 [ 989.763991] R10: ffff880179c8c000 R11: 0000000000000003 R12: ffff880174d48008 [ 989.764204] R13: 0000000000000003 R14: ffff880179c8c000 R15: ffff88021db7a000 [ 989.764422] FS: 0000000000000000(0000) GS:ffff880247480000(0000) knlGS:ffff880247480000 [ 989.764685] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 989.764865] CR2: ffff8000007f6800 CR3: 0000000001ae0000 CR4: 0000000000042660 [ 989.765081] Stack: [ 989.765167] 00000000000 ---truncated---

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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
11th
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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

February 26, 2025

Last Modified

August 5, 2026

References (9)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 4.9.318 (fixes >=2.6.17)—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 (14 versions)
  • every version up to 5.10.127-1: fixed in 5.10.127-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-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 99 of 197 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 98 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% · 11th percentile
  2. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-25 17:55 UTCEG score recompute
  10. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-24 17:54 UTCEG score recompute
  12. 2026-10-24 17:54 UTCGHSA enrichmentGHSA-xw4w-p39h-frx8 · GitHub CVSS 5.5
  13. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-19 11:55 UTCOSV refresh
  20. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-18 08:20 UTCEG score recompute
  22. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 74 more
  1. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-12 18:42 UTCEG score recompute
  3. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-11 22:05 UTCEG score recompute
  5. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-09-30 16:12 UTCEG score recompute
  15. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-09-26 19:03 UTCOSV refresh
  18. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  26. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  27. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  28. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  29. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  30. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  31. 2026-09-07 04:18 UTCOSV refresh
  32. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  33. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  34. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  35. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  36. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  37. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  38. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  39. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  40. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  41. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  42. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  43. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  44. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  45. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  46. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  47. 2026-08-20 14:31 UTCOSV refresh
  48. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  49. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  50. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  51. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  52. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  53. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  54. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  55. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  56. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  57. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  58. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  59. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  60. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  61. 2026-08-05 09:31 UTCEG score recompute
  62. 2026-08-05 09:31 UTCGHSA enrichmentGHSA-xw4w-p39h-frx8 · GitHub CVSS 5.5
  63. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  64. 2026-08-04 11:13 UTCEG score recompute
  65. 2026-08-04 11:13 UTCGHSA enrichmentGHSA-xw4w-p39h-frx8 · GitHub CVSS 5.5
  66. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  67. 2026-08-04 09:46 UTCEG score recompute
  68. 2026-08-04 09:46 UTCGHSA enrichmentGHSA-xw4w-p39h-frx8 · GitHub CVSS 5.5
  69. 2026-08-03 10:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  70. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  71. 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  72. 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  73. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  74. 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.2% · 10th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-49337?
CVE-2022-49337 is a medium-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: ocfs2: dlmfs: fix error handling of user_dlm_destroy_lock When user_dlm_destroy_lock failed, it didn't clean up the flags it set before exit. For USER_LOCK_IN_TEARDOWN, if this function fails because of lock is still in used, next…
When was the CVE record for CVE-2022-49337 published?
The CVE record for CVE-2022-49337 was published on February 26, 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-49337 actively exploited?
CVE-2022-49337 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49337?
CVE-2022-49337 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49337?
A fix for CVE-2022-49337 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-49337

Explore →

Is Your Infrastructure Affected by CVE-2022-49337?

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

Book a Demo →Browse All CVEs