CVE-2026-63965: Linux kernel · iio: pressure: bmp280: fix stack leak in bmp580 trigger handler
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 30 Oct 2026, 20:25 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- 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
Weaponized: 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 30 Oct 2026.
What to do
AI-suggested
A fix is available that zero-initializes the stack buffer in the bmp280 trigger handler to prevent uninitialized stack memory leakage. Users should apply the updated Linux kernel patches that include this fix once available.
Description
A vulnerability in the Linux kernel's bmp280 pressure sensor driver caused uninitialized stack memory to be leaked to userspace. The issue arose because a stack-local buffer was not zero-initialized before copying 24-bit sensor data into 32-bit fields, leaving high bytes uninitialized and leaking stack data. This was a regression introduced when the buffer was moved from private data to the stack. The vulnerability has been fixed by zero-initializing the stack structure.