CVE-2026-99148

HIGHPre-NVD 7.07.0
EchelonGraph scoreHIGH confidence

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

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-10-28. A secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-111900 (ENISA EUVD) · GHSA-xpw2-c5ch-25qm (GitHub Security Advisories)Source: ENISA EUVD

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

A fix is available — apply it.

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

drm/amdgpu: keep the eviction fence until the last handle is closed

amdgpu_gem_object_close() detaches the user queue eviction fence from the BO before it checks bo_va->ref_count, so closing any handle of a BO removes the fence, even when the file still has another handle to the BO and the bo_va with its GPU mappings stays. The BO can then be evicted without suspending the user queues of the file, which keep accessing it through mappings that are only marked for update.

Seen on navi31 with a SDMA user queue: a BO opened twice in the same file (GEM_FLINK + GEM_OPEN) loses its eviction fence when the second handle is closed (traced attach/detach of the fence):

attach bo=ffff8c78a6c84c00 GEM_CLOSE handle=7 detach bo=ffff8c78a6c84c00

while handle 6 and the mapping are still in use.

Only detach the fence when the last reference to the bo_va goes away, matching amdgpu_gem_object_open(), which attaches it only when the bo_va is created. With this the fence stays until the file is closed.

(cherry picked from commit 8387982f03d4026b7dc11b0b5e3118298eee4d6a)

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

EG Severity
7.0 HIGHCVSS-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. 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

October 28, 2026

Last Modified

October 31, 2026

Advisory Details (3)

Auto-updated Oct 31, 2026
Patch available.
Web page

drm/amdgpu: keep the eviction fence until the last handle is closed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3c44cbcec5eb370713bbd2c315ed7c34d8ccec2b
Web page

drm/amdgpu: keep the eviction fence until the last handle is closed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6467c4cc83b94850bfea614e9f98276edf9a7c3f
Web page

drm/amdgpu: keep the eviction fence until the last handle is closed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dce8f7f03a47b1744dccf506268f9229b67fab47

Vendor Advisories for CVE-2026-99148(2)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (192 versions)
  • every version up to 7.2.13-1: fixed in 7.2.13-1
—

Data Freshness Timeline

(refreshed 6× in last 7d / 30× 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.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-11-16 16:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-11-15 11:31 UTCEchelonGraph re-scored
  9. 2026-11-15 11:31 UTCGHSA enrichmentGHSA-xpw2-c5ch-25qm · GitHub severity HIGH · GitHub CVSS 7.0
  10. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-11-13 16:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-11-08 16:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-11-08 00:28 UTCEchelonGraph re-scored
  17. 2026-11-08 00:28 UTCGHSA enrichmentGHSA-xpw2-c5ch-25qm · GitHub severity HIGH · GitHub CVSS 7.0
  18. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-10-31 13:27 UTCEchelonGraph re-scored
Show 10 more
  1. 2026-10-31 13:27 UTCGHSA enrichmentGHSA-xpw2-c5ch-25qm
  2. 2026-10-31 12:48 UTCEchelonGraph re-scoredFirst assessed: 7.0 HIGH
  3. 2026-10-31 12:48 UTCGHSA enrichmentGHSA-xpw2-c5ch-25qm
  4. 2026-10-31 12:48 UTCMITRE cvelistV5CVSS v3 → 7 · severity → HIGH
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-28 11:26 UTCNVD update
  8. 2026-10-28 11:01 UTCENISA EUVD ID recordedEUVD-2026-111900 · Source: ENISA EUVD
  9. 2026-10-28 10:46 UTCEchelonGraph re-scored
  10. 2026-10-28 10:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-99148?
CVE-2026-99148 is a high-severity vulnerability; its CVE record was published on October 28, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: keep the eviction fence until the last handle is closed amdgpu_gem_object_close() detaches the user queue eviction fence from the BO before it checks bo_va->ref_count, so closing any handle of a BO removes the fence,…
When was the CVE record for CVE-2026-99148 published?
The CVE record for CVE-2026-99148 was published on October 28, 2026. 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 October 31, 2026; the record at its source may have been updated since.
Is CVE-2026-99148 actively exploited?
CVE-2026-99148 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-99148?
CVE-2026-99148 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-99148?
A fix for CVE-2026-99148 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-99148 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-2026-99148

Explore →

Is Your Infrastructure Affected by CVE-2026-99148?

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