In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: correct reservation fence slots for userq per-vm BOs eviction
It fixes both the move overflow and the eviction fence add for evicting these per-vm BOs.
CVE-2026-99261
UNRATEDCVSS · not yet scoredTrending — 6 sources updated this week
Also known asEUVD-2026-115772 (ENISA EUVD) · GHSA-grq3-hpv5-rc78 (GitHub Security Advisories)Source: ENISA EUVD
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- —
- EchelonGraph score
- Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
- EG Score
- —
- EG Risk
- —
- EPSS PROB
- 0.2%
- EPSS %ILE
- 7th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
- EG Severity
- Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
- 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
- No SSVC decision: EchelonGraph has not assessed this CVECISA 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 BOD 26-04 block below.
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
November 3, 2026
Last Modified
November 3, 2026
References (2)
Vendor Advisories for CVE-2026-99261(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× 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.
- 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
- 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
- 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 7th percentile
- 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 7th percentile
- 2026-11-03 19:26 UTCNVD update
- 2026-11-03 19:19 UTCGHSA enrichmentGHSA-grq3-hpv5-rc78
- 2026-11-03 19:16 UTCMITRE cvelistV5
- 2026-11-03 12:26 UTCNVD update
- 2026-11-03 12:03 UTCENISA EUVD ID recordedEUVD-2026-115772 · Source: ENISA EUVD
- 2026-11-03 11:29 UTCEG score recompute
- 2026-11-03 11:26 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-99261?
CVE-2026-99261 is a vulnerability whose severity is not yet rated; its CVE record was published on November 3, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: correct reservation fence slots for userq per-vm BOs eviction It fixes both the move overflow and the eviction fence add for evicting these per-vm BOs.
When was the CVE record for CVE-2026-99261 published?
The CVE record for CVE-2026-99261 was published on November 3, 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 November 3, 2026; the record at its source may have been updated since.
Is CVE-2026-99261 actively exploited?
CVE-2026-99261 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-99261?
A fix for CVE-2026-99261 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-99261 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-99261
Is Your Infrastructure Affected by CVE-2026-99261?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.