VulnerabilityPublished 19 Jul 2026

CVE-2026-63965: Linux kernel · iio: pressure: bmp280: fix stack leak in bmp580 trigger handler

Source GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-7wfc-wfh5-rxrh

What to do

AI-suggested

A fix is available that zero-initializes the stack structure in the bmp580 trigger handler to prevent uninitialized memory leakage. Users should update their Linux kernel to a version that includes this patch. Since this is a kernel driver issue, applying the official kernel update or patch from the Linux kernel maintainers is the recommended remediation. No additional mitigations are specified.

Description

A vulnerability in the Linux kernel's bmp280 pressure sensor driver involves uninitialized stack memory in the bmp580 trigger handler. The handler copies 3 bytes of sensor data into a 4-byte field on the stack without zero-initializing the buffer, leaving the high byte uninitialized. This causes two bytes of potentially sensitive stack data to be exposed to userspace per scan. The issue is a regression caused by moving the buffer from private data to a stack-local structure without zeroing it. The vulnerability has been resolved by zero-initializing the stack structure.

References

Community reviews

Loading reviews…