# CVE-2026-1991: libuvc UVC Descriptor device.c uvc_scan_streaming null pointer dereference

> A local attacker can cause a denial of service via null pointer dereference in libuvc's UVC descriptor handler.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 6 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** DEBIAN-CVE-2026-1991, GHSA-6rqp-5xh4-j422, UBUNTU-CVE-2026-1991

## What is CVE-2026-1991?

CVE-2026-1991 is a medium-severity vulnerability in libuvc, published on 6 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was detected in libuvc up to 0.0.7. Affected is the function uvc_scan_streaming of the file src/device.c of the component UVC Descriptor Handler. The manipulation results in null pointer dereference. The attack needs to be approached locally. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2026-1991?

It affects 1 product.


Products: Libuvc Libuvc.

## How do I fix CVE-2026-1991?

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

## Is CVE-2026-1991 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1991 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1991 and fix it if it is affected.

What it is: CVE-2026-1991 is a medium-severity vulnerability in libuvc, published on 6 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1991 exists.

Affected product: libuvc. 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-2026-1991/ (Markdown: https://insights.sbomify.com/CVE-2026-1991/index.md)
```

## Sources

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

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