# CVE-2026-63965: iio: pressure: bmp280: fix stack leak in bmp580 trigger handler

> A stack leak in the BMP580 pressure sensor driver allows local attackers to read uninitialized kernel stack memory via sensor data channels.

- **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:** 19 Jul 2026
- **Updated:** 19 Jul 2026
- **Also known as:** BELL-CVE-2026-63965, DEBIAN-CVE-2026-63965, GHSA-7wfc-wfh5-rxrh, UBUNTU-CVE-2026-63965

## What is CVE-2026-63965?

CVE-2026-63965 is a vulnerability in Linux, published on 19 Jul 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:

iio: pressure: bmp280: fix stack leak in bmp580 trigger handler

bmp580_trigger_handler() declares its scan buffer on the stack without
an initializer and then memcpy()s 3 bytes of 24-bit sensor data into
each 4-byte __le32 field.  The high byte of comp_temp and comp_press is
left uninitialized, and the channel storagebits is 32, so two bytes of
stack are pushed to userspace per scan.

This is a regression from when the buffer lived in the private data, the
move to a stack-local struct dropped the implicit zeroing.
bme280_trigger_handler() was fixed up to handle this bug, but this
driver was not fixed because there was no padding hole, but rather a
short-fill issue.

Fix this all by just zero-initializing the structure on the stack.

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


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

Apply the vendor's patch.

## Is CVE-2026-63965 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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