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.
Published: 2026-07-19
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

In Linux kernels, the Industrial I/O pressure driver for BMP580 sensors contains a stack leak; the handler allocates a small buffer without zero‑initialization and copies three bytes of sensor data into each 32‑bit field. The uninitialized high byte of the temperature and pressure values remains on the stack and is exposed to userspace on each scan. The vulnerability results in local leaking of residual kernel stack data, exposing sensitive information without affecting control flow or privileges. The weakness corresponds to CWE‑908, a local information disclosure.

Affected Systems

Any Linux kernel that has not incorporated the commit adding zero‑initialization to the bmp580 trigger handler is vulnerable. System administrators should verify whether their running kernel includes the source changes shown in the linked Git repository commits, and apply any kernel release that contains the fix.

Risk and Exploitability

The EPSS score is less than 1%, and the issue is not listed in CISA’s KEV catalog, indicating a low probability of widespread exploitation. An attacker with local access who can read the sensor device node can trigger the handler, capturing leaked stack bytes each time a measurement is requested. The attack does not require elevated privileges or network access; it is a local attack vector. Consequently, the risk is confined to the disclosure of kernel stack contents, with limited impact beyond information leakage.

Generated by OpenCVE AI on August 4, 2026 at 18:10 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the zero‑initialization patch for bmp580 trigger handler
  • Disable the BMP580 sensor interface by removing or commenting out its device tree entry to eliminate the exposure path
  • Restrict permissions on the sensor device node so that only privileged processes can read its output

Generated by OpenCVE AI on August 4, 2026 at 18:10 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
History

Wed, 29 Jul 2026 01:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-788

Wed, 22 Jul 2026 12:15:00 +0000


Tue, 21 Jul 2026 23:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-788

Sun, 19 Jul 2026 15:30:00 +0000

Type Values Removed Values Added
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.
Title iio: pressure: bmp280: fix stack leak in bmp580 trigger handler
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-07-19T14:55:53.809Z

Reserved: 2026-07-19T07:54:57.024Z

Link: CVE-2026-63965

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity :

Publid Date: 2026-07-19T00:00:00Z

Links: CVE-2026-63965 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-04T18:15:03Z

Weaknesses
  • CWE-908

    Use of Uninitialized Resource