CVE-2026-63965

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 30, 2026

Vendor Advisories for CVE-2026-63965(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 11× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 02:54 UTCVendor advisory
  2. 2026-08-30 02:54 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-27 01:17 UTCVendor advisory
  7. 2026-08-27 01:17 UTCGHSA enrichment
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 07:48 UTCVendor advisory
  11. 2026-08-24 07:48 UTCGHSA enrichment
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 14:00 UTCVendor advisory
  14. 2026-08-21 14:00 UTCGHSA enrichment
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-18 19:50 UTCVendor advisory
  18. 2026-08-18 19:50 UTCGHSA enrichment
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 00:49 UTCVendor advisory
  23. 2026-08-16 00:49 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-13 22:00 UTCEPSS rescore
Show 53 more
  1. 2026-08-13 07:19 UTCVendor advisory
  2. 2026-08-13 07:19 UTCGHSA enrichment
  3. 2026-08-12 13:51 UTCEPSS rescore
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 13:38 UTCVendor advisory
  6. 2026-08-10 13:38 UTCGHSA enrichment
  7. 2026-08-09 13:47 UTCEPSS rescore
  8. 2026-08-08 16:37 UTCEPSS rescore
  9. 2026-08-07 20:08 UTCVendor advisory
  10. 2026-08-07 20:08 UTCGHSA enrichment
  11. 2026-08-06 13:47 UTCEPSS rescore
  12. 2026-08-05 19:17 UTCEPSS rescore
  13. 2026-08-05 19:17 UTCEPSS rescore
  14. 2026-08-05 02:39 UTCVendor advisory
  15. 2026-08-05 02:39 UTCGHSA enrichment
  16. 2026-08-04 15:10 UTCEPSS rescore
  17. 2026-08-04 10:39 UTCEPSS rescore
  18. 2026-08-03 10:36 UTCEPSS rescore
  19. 2026-08-02 09:10 UTCVendor advisory
  20. 2026-08-02 09:10 UTCGHSA enrichment
  21. 2026-08-02 02:27 UTCEPSS rescore
  22. 2026-08-01 04:16 UTCEPSS rescore
  23. 2026-07-30 16:28 UTCEPSS rescore
  24. 2026-07-30 15:41 UTCEG score recompute
  25. 2026-07-30 15:41 UTCVendor advisory
  26. 2026-07-30 15:41 UTCGHSA enrichment
  27. 2026-07-30 01:30 UTCEPSS rescore
  28. 2026-07-30 01:30 UTCEPSS rescore
  29. 2026-07-29 04:31 UTCGHSA enrichment
  30. 2026-07-28 15:37 UTCEPSS rescore
  31. 2026-07-27 14:14 UTCEPSS rescore
  32. 2026-07-26 14:54 UTCEPSS rescore
  33. 2026-07-26 14:54 UTCEPSS rescore
  34. 2026-07-26 10:59 UTCEG score recompute
  35. 2026-07-26 10:59 UTCVendor advisory
  36. 2026-07-26 10:58 UTCGHSA enrichment
  37. 2026-07-25 14:18 UTCEPSS rescore
  38. 2026-07-25 14:18 UTCEPSS rescore
  39. 2026-07-24 14:18 UTCEPSS rescore
  40. 2026-07-24 14:18 UTCEPSS rescore
  41. 2026-07-23 14:18 UTCEPSS rescore
  42. 2026-07-23 14:18 UTCEPSS rescore
  43. 2026-07-23 03:22 UTCEG score recompute
  44. 2026-07-22 14:08 UTCEPSS rescore
  45. 2026-07-22 14:08 UTCEPSS rescore
  46. 2026-07-21 15:25 UTCEPSS rescore
  47. 2026-07-21 15:25 UTCEPSS rescore
  48. 2026-07-20 17:33 UTCEG score recompute
  49. 2026-07-20 17:33 UTCGHSA enrichment
  50. 2026-07-20 17:08 UTCEPSS rescore
  51. 2026-07-19 17:49 UTCNVD update
  52. 2026-07-19 15:21 UTCEG score recompute
  53. 2026-07-19 15:19 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-63965?
CVE-2026-63965 is a publicly disclosed vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: iio: pressure: bmp280: fix stack leak in bmp580 trigger handler bmp580triggerhandler() 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…
When was CVE-2026-63965 disclosed?
CVE-2026-63965 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63965 actively exploited?
CVE-2026-63965 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.4% of all scored CVEs.
How do I remediate CVE-2026-63965?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63965, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63965

Explore →

Is Your Infrastructure Affected by CVE-2026-63965?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.