0.0
NA
CVE-2026-63967
iio: 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.

INFO

Published Date :

July 19, 2026, 4:17 p.m.

Last Modified :

July 30, 2026, 2:51 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-63967 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
Solution
Initialize stack-allocated buffer to prevent data leaks.
  • Zero-initialize the stack structure.
  • Ensure alignment qualifiers include initializers.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-63967 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-63967 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-63967 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-63967 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jul. 19, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'c14edb4d0bdc53f969ea84c7f384472c28b1a9f8', 'lessThan': 'ff8d3c088b77b11782f2c3b97e37425be050e8de', 'versionType': 'git'}, {'status': 'affected', 'version': 'c14edb4d0bdc53f969ea84c7f384472c28b1a9f8', 'lessThan': 'fe1a7f99e72ebd2880515332b79b8c256be22aca', 'versionType': 'git'}, {'status': 'affected', 'version': 'c14edb4d0bdc53f969ea84c7f384472c28b1a9f8', 'lessThan': 'babf1943a40bb5669db57d30ca16c22504b18e07', 'versionType': 'git'}, {'status': 'affected', 'version': 'c14edb4d0bdc53f969ea84c7f384472c28b1a9f8', 'lessThan': 'd42ac0bfb6a16617c62a59d53706579c7fadbfa6', 'versionType': 'git'}, {'status': 'affected', 'version': 'c14edb4d0bdc53f969ea84c7f384472c28b1a9f8', 'lessThan': '3147b303b8c7d9f91da4b849ece33b45048f5eaf', 'versionType': 'git'}, {'status': 'affected', 'version': 'c14edb4d0bdc53f969ea84c7f384472c28b1a9f8', 'lessThan': 'e6bb3a49c5f9de870ea95e69775df785728e3366', 'versionType': 'git'}, {'status': 'affected', 'version': 'c14edb4d0bdc53f969ea84c7f384472c28b1a9f8', 'lessThan': '890d0312d5f94be43eac21f5a34d3bccc60d051b', 'versionType': 'git'}, {'status': 'affected', 'version': 'c14edb4d0bdc53f969ea84c7f384472c28b1a9f8', 'lessThan': 'c9d8e9adaa63150ef7e833480b799d0bab83a276', 'versionType': 'git'}, {'status': 'affected', 'version': 'a42ca3b182ccb766666a0be1053921cba190e2de', 'versionType': 'git'}, {'status': 'affected', 'version': '5.9.5', 'lessThan': '5.10', 'versionType': 'semver'}], 'programFiles': ['drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.10'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.10', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.259', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.210', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.176', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.143', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.93', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.35', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.12', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c'], 'defaultStatus': 'affected'}]
    Added 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.
    Added Reference https://git.kernel.org/stable/c/3147b303b8c7d9f91da4b849ece33b45048f5eaf
    Added Reference https://git.kernel.org/stable/c/890d0312d5f94be43eac21f5a34d3bccc60d051b
    Added Reference https://git.kernel.org/stable/c/babf1943a40bb5669db57d30ca16c22504b18e07
    Added Reference https://git.kernel.org/stable/c/c9d8e9adaa63150ef7e833480b799d0bab83a276
    Added Reference https://git.kernel.org/stable/c/d42ac0bfb6a16617c62a59d53706579c7fadbfa6
    Added Reference https://git.kernel.org/stable/c/e6bb3a49c5f9de870ea95e69775df785728e3366
    Added Reference https://git.kernel.org/stable/c/fe1a7f99e72ebd2880515332b79b8c256be22aca
    Added Reference https://git.kernel.org/stable/c/ff8d3c088b77b11782f2c3b97e37425be050e8de
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.