# CVE-2026-80595: Input: ims-pcu - add response length checks

> A missing length check in the Linux kernel ims-pcu driver allows local attackers to read out-of-bounds memory or stale data from device buffers.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** BELL-CVE-2026-80595, DEBIAN-CVE-2026-80595, GHSA-xgp4-6595-v35f, UBUNTU-CVE-2026-80595

## What is CVE-2026-80595?

CVE-2026-80595 is a vulnerability in Linux, published on 28 Aug 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:

Input: ims-pcu - add response length checks

The driver processes response data from device buffers without verifying
that the device actually sent enough data. This can lead to
out-of-bounds reads or processing stale data.

Add checks for the expected response length before accessing the
buffers.

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


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

Apply the vendor's patch.

## Is CVE-2026-80595 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80595 is a vulnerability in Linux, published on 28 Aug 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-80595 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-80595/ (Markdown: https://insights.sbomify.com/CVE-2026-80595/index.md)
```

## Sources

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

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