CVE-2022-47939

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-12-23. NVD baseline CVSS 9.8; sources differ by 0.0.

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

Also known asEUVD-2022-50672 (ENISA EUVD) · GHSA-c5f7-v4rr-qv23 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 49%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

An issue was discovered in ksmbd in the Linux kernel 5.15 through 5.19 before 5.19.2. fs/ksmbd/smb2pdu.c has a use-after-free and OOPS for SMB2_TREE_DISCONNECT.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
64
EG Risk 64/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation49% × 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
49%
EPSS %ILE
98th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
49% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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

December 23, 2022

Last Modified

April 14, 2025

Advisory Details (6)

Auto-updated Oct 10, 2026
Patch available. Sources: github_commit.
GitHub commit

commit cf6531d98190 (torvalds/linux)

Fix landed in torvalds/linux commit cf6531d98190 — awaiting tagged release

https://github.com/torvalds/linux/commit/cf6531d98190fa2cf92a6d8bbc8af0a4740a223c
Web page

ksmbd: fix use-after-free bug in smb2_tree_disconect - kernel/git/torvalds/linux.git - Linux kernel source tree

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=cf6531d98190fa2cf92a6d8bbc8af0a4740a223c
Web page

oss-security - Re: Details on this supposed Linux Kernel ksmbd RCE

http://www.openwall.com/lists/oss-security/2022/12/23/10
Web page

ZDI-22-1690 - TrendAI™ Zero Day Initiative™ (ZDI)

https://www.zerodayinitiative.com/advisories/ZDI-22-1690/

Vendor Advisories for CVE-2022-47939(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.19.6-1: fixed in 5.19.6-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.19.6-1: fixed in 5.19.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.19.6-1: fixed in 5.19.6-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 76× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 262 rows 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. None are among the latest 100 rows. The 162 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2022-47939?
CVE-2022-47939 is a critical-severity vulnerability; its CVE record was published on December 23, 2022. An issue was discovered in ksmbd in the Linux kernel 5.15 through 5.19 before 5.19.2. fs/ksmbd/smb2pdu.c has a use-after-free and OOPS for SMB2_TREE_DISCONNECT.
When was the CVE record for CVE-2022-47939 published?
The CVE record for CVE-2022-47939 was published on December 23, 2022. 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 April 14, 2025; the record at its source may have been updated since.
Is CVE-2022-47939 actively exploited?
CVE-2022-47939 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 49% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-47939?
CVE-2022-47939 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-47939?
A fix for CVE-2022-47939 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-47939 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-47939

Explore →

Is Your Infrastructure Affected by CVE-2022-47939?

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