CVE-2023-39198

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2023-11-09. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week
7.5EG
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: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A race condition was found in the QXL driver in the Linux kernel. The qxl_mode_dumb_create() function dereferences the qobj returned by the qxl_gem_object_create_with_handle(), but the handle is the only one holding a reference to it. This flaw allows an attacker to guess the returned handle value and trigger a use-after-free issue, potentially leading to a denial of service or privilege escalation.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-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-20). 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: 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

November 9, 2023

Last Modified

March 24, 2026

References (6)

Vendor Advisories for CVE-2023-39198(4)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-kvm (6.2.0.1018.18) @ lunar2026-05-23ubuntu
ubuntulinux-tools-gkeop-edge (5.15.0.1034.40~20.04.30) @ focal2026-05-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.91.92) @ jammy2026-05-23ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1046.52~20.04.36) @ focal2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04 (6.2.0.39.40~22.04.16) @ jammy2026-05-23ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1046.46) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.2.0.39.39) @ lunar2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.91.88) @ jammy2026-05-23ubuntu
redhatkernel-rt-0:4.18.0-553.rt7.342.el8_102024-05-22redhat
redhatkernel-0:4.18.0-553.el8_102024-05-22redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat

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

(5 across 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
linux-5.105.10.136-1~deb10u1 ... 5.10.205-2~deb10u1 (12 versions)
  • every version up to 5.10.209-2~deb10u1: fixed in 5.10.209-2~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (37 versions)
  • every version up to 5.10.209-1: fixed in 5.10.209-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)
  • every version up to 6.1.52-1: fixed in 6.1.52-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.13-1: fixed in 6.4.13-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.13-1: fixed in 6.4.13-1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(8)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× 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 86 of 206 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. 14 repeat rows among the latest 100 are merged into the row they repeat. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-20 23:33 UTCEG score recompute
  4. 2026-10-20 23:33 UTCVendor advisory
  5. 2026-10-20 23:33 UTCGHSA enrichmentGHSA-qhp7-446p-xq88 · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  7. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-10-18 07:54 UTCEG score recompute
  10. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-12 18:21 UTCEG score recompute
  16. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-10-11 21:48 UTCEG score recompute
  18. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-10-09 22:25 UTCOSV refresh
  21. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 61 more
  1. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-09-30 16:28 UTCEG score recompute
  5. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-09-26 15:56 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  13. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-09-20 06:13 UTCOSV refresh
  15. 2026-09-18 19:25 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-09-17 19:25 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  19. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  25. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  26. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  27. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  28. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  29. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  30. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  31. 2026-09-01 09:59 UTCOSV refresh
  32. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  33. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  34. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  35. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  36. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  37. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  38. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  39. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  40. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  41. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  42. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  43. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  44. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  45. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  46. 2026-08-15 09:07 UTCOSV refresh
  47. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  48. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  49. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  50. 2026-08-11 13:39 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  51. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  52. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  53. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  54. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  55. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  56. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  57. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  58. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  59. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  60. 2026-07-30 21:20 UTCOSV refresh
  61. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-39198?
CVE-2023-39198 is a high-severity vulnerability; its CVE record was published on November 9, 2023. A race condition was found in the QXL driver in the Linux kernel. The qxlmodedumbcreate() function dereferences the qobj returned by the qxlgemobjectcreatewithhandle(), but the handle is the only one holding a reference to it. This flaw allows an attacker to guess the returned handle value and…
When was CVE-2023-39198 made public?
CVE-2023-39198 was made public on August 17, 2023: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on November 9, 2023. EchelonGraph's copy of the record carries a last-modified date of March 24, 2026; the record at its source may have been updated since.
Is CVE-2023-39198 actively exploited?
CVE-2023-39198 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-2023-39198?
CVE-2023-39198 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2023-39198?
A fix for CVE-2023-39198 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-39198 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-2023-39198

Explore →

Is Your Infrastructure Affected by CVE-2023-39198?

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

Book a Demo →Browse All CVEs