{"api_version":"1","generated_at":"2026-07-20T23:54:59+00:00","cve":"CVE-2026-63965","urls":{"html":"https://cve.report/CVE-2026-63965","api":"https://cve.report/api/cve/CVE-2026-63965.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-63965","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-63965"},"summary":{"title":"iio: pressure: bmp280: fix stack leak in bmp580 trigger handler","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niio: pressure: bmp280: fix stack leak in bmp580 trigger handler\n\nbmp580_trigger_handler() declares its scan buffer on the stack without\nan initializer and then memcpy()s 3 bytes of 24-bit sensor data into\neach 4-byte __le32 field.  The high byte of comp_temp and comp_press is\nleft uninitialized, and the channel storagebits is 32, so two bytes of\nstack are pushed to userspace per scan.\n\nThis is a regression from when the buffer lived in the private data, the\nmove to a stack-local struct dropped the implicit zeroing.\nbme280_trigger_handler() was fixed up to handle this bug, but this\ndriver was not fixed because there was no padding hole, but rather a\nshort-fill issue.\n\nFix this all by just zero-initializing the structure on the stack.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-19 16:17:15","updated_at":"2026-07-19 16:17:15"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/387c86b582e0782ab332e7bfcd4e6e3f93922961","name":"https://git.kernel.org/stable/c/387c86b582e0782ab332e7bfcd4e6e3f93922961","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/58dfb6fe9dc80270cf7cc014837af4cbf928e3aa","name":"https://git.kernel.org/stable/c/58dfb6fe9dc80270cf7cc014837af4cbf928e3aa","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a58400f58f82f3d8de9c067aa7cda690228c1ecc","name":"https://git.kernel.org/stable/c/a58400f58f82f3d8de9c067aa7cda690228c1ecc","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-63965","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63965","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 872c8014e05ed47b8a7c0f5ba4311279a637150b a58400f58f82f3d8de9c067aa7cda690228c1ecc git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 872c8014e05ed47b8a7c0f5ba4311279a637150b 58dfb6fe9dc80270cf7cc014837af4cbf928e3aa git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 872c8014e05ed47b8a7c0f5ba4311279a637150b 387c86b582e0782ab332e7bfcd4e6e3f93922961 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.16","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.16 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.35 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.12 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/iio/pressure/bmp280-core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"a58400f58f82f3d8de9c067aa7cda690228c1ecc","status":"affected","version":"872c8014e05ed47b8a7c0f5ba4311279a637150b","versionType":"git"},{"lessThan":"58dfb6fe9dc80270cf7cc014837af4cbf928e3aa","status":"affected","version":"872c8014e05ed47b8a7c0f5ba4311279a637150b","versionType":"git"},{"lessThan":"387c86b582e0782ab332e7bfcd4e6e3f93922961","status":"affected","version":"872c8014e05ed47b8a7c0f5ba4311279a637150b","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/iio/pressure/bmp280-core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.16"},{"lessThan":"6.16","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.35","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.12","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.35","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.12","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"6.16","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\niio: pressure: bmp280: fix stack leak in bmp580 trigger handler\n\nbmp580_trigger_handler() declares its scan buffer on the stack without\nan initializer and then memcpy()s 3 bytes of 24-bit sensor data into\neach 4-byte __le32 field.  The high byte of comp_temp and comp_press is\nleft uninitialized, and the channel storagebits is 32, so two bytes of\nstack are pushed to userspace per scan.\n\nThis is a regression from when the buffer lived in the private data, the\nmove to a stack-local struct dropped the implicit zeroing.\nbme280_trigger_handler() was fixed up to handle this bug, but this\ndriver was not fixed because there was no padding hole, but rather a\nshort-fill issue.\n\nFix this all by just zero-initializing the structure on the stack."}],"providerMetadata":{"dateUpdated":"2026-07-19T14:55:53.809Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/a58400f58f82f3d8de9c067aa7cda690228c1ecc"},{"url":"https://git.kernel.org/stable/c/58dfb6fe9dc80270cf7cc014837af4cbf928e3aa"},{"url":"https://git.kernel.org/stable/c/387c86b582e0782ab332e7bfcd4e6e3f93922961"}],"title":"iio: pressure: bmp280: fix stack leak in bmp580 trigger handler","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-63965","datePublished":"2026-07-19T14:55:53.809Z","dateReserved":"2026-07-19T07:54:57.024Z","dateUpdated":"2026-07-19T14:55:53.809Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-19 16:17:15","lastModifiedDate":"2026-07-19 16:17:15","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"63965","Ordinal":"1","Title":"iio: pressure: bmp280: fix stack leak in bmp580 trigger handler","CVE":"CVE-2026-63965","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"63965","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\niio: pressure: bmp280: fix stack leak in bmp580 trigger handler\n\nbmp580_trigger_handler() declares its scan buffer on the stack without\nan initializer and then memcpy()s 3 bytes of 24-bit sensor data into\neach 4-byte __le32 field.  The high byte of comp_temp and comp_press is\nleft uninitialized, and the channel storagebits is 32, so two bytes of\nstack are pushed to userspace per scan.\n\nThis is a regression from when the buffer lived in the private data, the\nmove to a stack-local struct dropped the implicit zeroing.\nbme280_trigger_handler() was fixed up to handle this bug, but this\ndriver was not fixed because there was no padding hole, but rather a\nshort-fill issue.\n\nFix this all by just zero-initializing the structure on the stack.","Type":"Description","Title":"iio: pressure: bmp280: fix stack leak in bmp580 trigger handler"}]}}}