# CVE-2007-3532: Misconfiguration in n/a

> Local users can exploit insecure device file permissions in NVIDIA drivers to cause denial of service or read sensitive information.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q9wq-fgjg-qwhp

## What is CVE-2007-3532?

CVE-2007-3532 is a high-severity vulnerability in n/a, published on 27 Jul 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA drivers (nvidia-drivers) before 1.0.7185, 1.0.9639, and 100.14.11, as used in Gentoo Linux and possibly other distributions, creates /dev/nvidia* device files with insecure permissions, which allows local users to modify video card settings, cause a denial of service (crash or physical video card damage), and obtain sensitive information.

Weakness: CWE-264

## Which versions are affected by CVE-2007-3532?

It affects 1 product.


Products: Nvidia Video Driver.

## How do I fix CVE-2007-3532?

No fix has been published for CVE-2007-3532 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-3532 being exploited?

There is no known exploitation of CVE-2007-3532 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3532 and fix it if it is affected.

What it is: CVE-2007-3532 is a high-severity vulnerability in n/a, published on 27 Jul 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-3532 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2007-3532/ (Markdown: https://insights.sbomify.com/CVE-2007-3532/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2007-3532
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-3532
- OSV: https://osv.dev/vulnerability/CVE-2007-3532

---
From sbomify Insights: https://insights.sbomify.com/CVE-2007-3532/
Summaries are generated and may contain mistakes; the official description above is the record.