Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-63967iio: imu: st_lsm6dsx: fix stack leak in tagged FIFO buffer

Description

In the Linux kernel, the following vulnerability has been resolved: iio: imu: st_lsm6dsx: fix stack leak in tagged FIFO buffer The tagged FIFO path declares iio_buff on the stack with __aligned(8) but no initializer, but there is a hole in the structure, which will then leak to userspace as ST_LSM6DSX_SAMPLE_SIZE bytes (6) will be copied, but the space between that and the timestamp are not initialized. Commit c14edb4d0bdc ("iio:imu:st_lsm6dsx Fix alignment and data leak issues") moved the untagged FIFO path to a kzalloc'd buffer in hw->scan, but for the tagged path it only added the alignment qualifier and not the initializer :( Fix this by just zero-initializing the structure on the stack.

Timeline

  1. ID reserved

    By Linux

  2. Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63967, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (22 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 – < ff8d3c088b77b11782f2c3b97e37425be050e8de
    • affected c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 – < fe1a7f99e72ebd2880515332b79b8c256be22aca
    • affected c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 – < babf1943a40bb5669db57d30ca16c22504b18e07
    • affected c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 – < d42ac0bfb6a16617c62a59d53706579c7fadbfa6
    • affected c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 – < 3147b303b8c7d9f91da4b849ece33b45048f5eaf
    • affected c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 – < e6bb3a49c5f9de870ea95e69775df785728e3366
    • affected c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 – < 890d0312d5f94be43eac21f5a34d3bccc60d051b
    • affected c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 – < c9d8e9adaa63150ef7e833480b799d0bab83a276
    • affected a42ca3b182ccb766666a0be1053921cba190e2de
    • affected 5.9.5 – < 5.10
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.93 – ≤ 6.12.*
    • unaffected 6.18.35 – ≤ 6.18.*
    • unaffected 7.0.12 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63967 badge
[![CVE-2026-63967](https://cveledger.app/badge/CVE-2026-63967.svg)](https://cveledger.app/cve/CVE-2026-63967)

Record last updated .