# CVE-2026-97983: vduse: return compat ioctl results directly

> A flaw in the Linux kernel's vduse module allows local attackers to leak file descriptors, potentially leading to resource exhaustion and denial of service.

- **Severity:** Not scored
- **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:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-97983, GHSA-qqc3-34rp-574r, UBUNTU-CVE-2026-97983

## What is CVE-2026-97983?

CVE-2026-97983 is a denial of service vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

vduse: return compat ioctl results directly

The compat handler handles VDUSE_IOTLB_GET_FD and VDUSE_VQ_GET_INFO, but
then calls the native handler. Their different command sizes make native
dispatch return -ENOIOCTLCMD.

For GET_FD, this overwrites receive_fd()'s return value after the
descriptor is installed, leaking one fd per call. Return handled compat
results directly and use native dispatch only for other commands.

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


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

Apply the vendor's patch.

## Is CVE-2026-97983 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97983 is a denial of service vulnerability in Linux, published on 25 Sep 2026. 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-2026-97983 in the wild and no public exploit code.

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

## Sources

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

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