iio: pressure: bmp280: fix stack leak in bmp580 trigger handler
Summary
| CVE | CVE-2026-63965 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-19 16:17:15 UTC |
| Updated | 2026-07-30 14:51:11 UTC |
| 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. |
Risk And Classification
EPSS: 0.001980000 probability, percentile 0.098250000 (date 2026-08-02)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 872c8014e05ed47b8a7c0f5ba4311279a637150b a58400f58f82f3d8de9c067aa7cda690228c1ecc git | Not specified |
| CNA | Linux | Linux | affected 872c8014e05ed47b8a7c0f5ba4311279a637150b 58dfb6fe9dc80270cf7cc014837af4cbf928e3aa git | Not specified |
| CNA | Linux | Linux | affected 872c8014e05ed47b8a7c0f5ba4311279a637150b 387c86b582e0782ab332e7bfcd4e6e3f93922961 git | Not specified |
| CNA | Linux | Linux | affected 6.16 | Not specified |
| CNA | Linux | Linux | unaffected 6.16 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.35 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0.12 7.0.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/387c86b582e0782ab332e7bfcd4e6e3f93922961 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/58dfb6fe9dc80270cf7cc014837af4cbf928e3aa | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a58400f58f82f3d8de9c067aa7cda690228c1ecc | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.