{
  "affected": [
    {
      "ranges": [
        {
          "events": [
            {
              "introduced": "872c8014e05ed47b8a7c0f5ba4311279a637150b"
            },
            {
              "fixed": "a58400f58f82f3d8de9c067aa7cda690228c1ecc"
            },
            {
              "fixed": "58dfb6fe9dc80270cf7cc014837af4cbf928e3aa"
            },
            {
              "fixed": "387c86b582e0782ab332e7bfcd4e6e3f93922961"
            }
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "type": "GIT"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Linux",
        "name": "Kernel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "6.16.0"
            },
            {
              "fixed": "6.18.35"
            }
          ],
          "type": "ECOSYSTEM"
        },
        {
          "events": [
            {
              "introduced": "6.19.0"
            },
            {
              "fixed": "7.0.12"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/63xxx/CVE-2026-63965.json"
  },
  "details": "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.",
  "id": "CVE-2026-63965",
  "modified": "2026-07-21T03:42:12.742450448Z",
  "published": "2026-07-19T14:55:53.809Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/387c86b582e0782ab332e7bfcd4e6e3f93922961"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/58dfb6fe9dc80270cf7cc014837af4cbf928e3aa"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a58400f58f82f3d8de9c067aa7cda690228c1ecc"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/63xxx/CVE-2026-63965.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-63965"
    },
    {
      "type": "PACKAGE",
      "url": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
    }
  ],
  "schema_version": "1.8.0",
  "summary": "iio: pressure: bmp280: fix stack leak in bmp580 trigger handler"
}