# CVE-2026-80605: HID: picolcd: prevent NULL pointer dereference in picolcd_send_and_wait()

> A local attacker with access to the picolcd HID device can trigger a kernel crash via integer overflow leading to NULL pointer dereference.

- **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:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** BELL-CVE-2026-80605, DEBIAN-CVE-2026-80605, GHSA-g689-gjw8-39fq, UBUNTU-CVE-2026-80605

## What is CVE-2026-80605?

CVE-2026-80605 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:

HID: picolcd: prevent NULL pointer dereference in picolcd_send_and_wait()

In picolcd_send_and_wait(), an integer overflow of the signed loop counter
'k' can theoretically lead to a NULL pointer dereference of 'raw_data'.
If the loop executes more than INT_MAX times, 'k' becomes negative,
making the condition 'k < size' true even when 'size' is 0.

Change the type of 'k' to 'unsigned int' to prevent the overflow and
eliminate the out-of-bounds access.

Found by Linux Verification Center (linuxtesting.org) with the Svace static
analysis tool.

[jkosina@suse.com: extended hash length]

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


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

Apply the vendor's patch.

## Is CVE-2026-80605 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80605 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-80605 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-80605/ (Markdown: https://insights.sbomify.com/CVE-2026-80605/index.md)
```

## Sources

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

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