A remote denial-of-service vulnerability exists in the way the Nouveau Display Driver (the default Ubuntu Nvidia display driver) handles GPU
A remote denial-of-service vulnerability exists in the way the Nouveau Display Driver (the default Ubuntu Nvidia display driver) handles GPU shader execution. A specially crafted pixel shader can cause remote denial-of-service issues. An attacker can provide a specially crafted website to trigger this vulnerability. This vulnerability can be triggered remotely after the user visits a malformed website. No further user interaction is required. Vulnerable versions include Ubuntu 18.04 LTS (linux 4.15.0-29-generic x86_64), Nouveau Display Driver NV117 (vermagic: 4.15.0-29-generic SMP mod_unload).
- Published
- Apr 1, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.4% · 72th percentile
- CWE
- CWE-400
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
CNA vs NVD score
- NVD
- 6.5
- CNA · talos
- 7.4
- 0.9 point gap
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| nvidia | geforce gtx 745 firmware | cpe:2.3:o:nvidia:geforce_gtx_745_firmware |
| nvidia | geforce gtx 745 | cpe:2.3:h:nvidia:geforce_gtx_745 |
| nvidia | geforce gtx 750 firmware | cpe:2.3:o:nvidia:geforce_gtx_750_firmware |
| nvidia | geforce gtx 750 | cpe:2.3:h:nvidia:geforce_gtx_750 |
| nvidia | geforce gtx 750 ti firmware | cpe:2.3:o:nvidia:geforce_gtx_750_ti_firmware |
| nvidia | geforce gtx 750 ti | cpe:2.3:h:nvidia:geforce_gtx_750_ti |
| nvidia | geforce gtx 840m firmware | cpe:2.3:o:nvidia:geforce_gtx_840m_firmware |
| nvidia | geforce gtx 840m | cpe:2.3:h:nvidia:geforce_gtx_840m |
| nvidia | geforce gtx 845m firmware | cpe:2.3:o:nvidia:geforce_gtx_845m_firmware |
| nvidia | geforce gtx 845m | cpe:2.3:h:nvidia:geforce_gtx_845m |
| nvidia | geforce gtx 850m firmware | cpe:2.3:o:nvidia:geforce_gtx_850m_firmware |
| nvidia | geforce gtx 850m | cpe:2.3:h:nvidia:geforce_gtx_850m |
and 21 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux18.04
- nvidia geforce gtx 745 firmwareall versions
- nvidia geforce gtx 750 firmwareall versions
- nvidia geforce gtx 750 ti firmwareall versions
- nvidia geforce gtx 840m firmwareall versions
- nvidia geforce gtx 845m firmwareall versions
- nvidia geforce gtx 850m firmwareall versions
- nvidia geforce gtx 860m firmwareall versions
- nvidia geforce gtx 950m firmwareall versions
- nvidia geforce gtx 960m firmwareall versions
- nvidia grid m30 firmwareall versions
- nvidia grid m40 firmwareall versions
- nvidia quadro k1200 firmwareall versions
- nvidia quadro k2200 firmwareall versions
- nvidia quadro k620 firmwareall versions
- nvidia quadro m1000m firmwareall versions
- nvidia quadro m1200m firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (talos). Independent of NVD's CPE analysis and usually ahead of it.
Nouveau Nouveau
- Ubuntu 18.04 LTS (linux 4.15.0-29-generic x86_64), Nouveau Display Driver NV117 (vermagic: 4.15.0-29-generic SMP mod_unload)affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | xserver-xorg-video-nouveau | all versions | — |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
- NVIDIA Public Bug BountyIntigriti · paid · up to $15,000
- NVIDIA Vulnerability Disclosure ProgramIntigriti · disclosure only (VDP)
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.