CVE-2026-63967 — iio: imu: st_lsm6dsx: fix stack leak in tagged FIFO buffer
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 and < ff8d3c088b77b11782f2c3b97e37425be050e8de≥ c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 and < fe1a7f99e72ebd2880515332b79b8c256be22aca≥ c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 and < babf1943a40bb5669db57d30ca16c22504b18e07≥ c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 and < d42ac0bfb6a16617c62a59d53706579c7fadbfa6≥ c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 and < 3147b303b8c7d9f91da4b849ece33b45048f5eaf≥ c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 and < e6bb3a49c5f9de870ea95e69775df785728e3366≥ c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 and < 890d0312d5f94be43eac21f5a34d3bccc60d051b≥ c14edb4d0bdc53f969ea84c7f384472c28b1a9f8 and < c9d8e9adaa63150ef7e833480b799d0bab83a276 and 3 moreversion a42ca3b182ccb766666a0be1053921cba190e2de≥ 5.9.5 and < 5.10version 5.10 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Awaiting Analysis
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/babf1943a40bb5669db57d30ca16c22504b18e07
- git.kernel.org/stable/c/d42ac0bfb6a16617c62a59d53706579c7fadbfa6
- git.kernel.org/stable/c/3147b303b8c7d9f91da4b849ece33b45048f5eaf
- git.kernel.org/stable/c/890d0312d5f94be43eac21f5a34d3bccc60d051b
- git.kernel.org/stable/c/fe1a7f99e72ebd2880515332b79b8c256be22aca
- git.kernel.org/stable/c/c9d8e9adaa63150ef7e833480b799d0bab83a276
- git.kernel.org/stable/c/e6bb3a49c5f9de870ea95e69775df785728e3366
- git.kernel.org/stable/c/ff8d3c088b77b11782f2c3b97e37425be050e8de
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 22h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 22h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-63967 is "iio: imu: st_lsm6dsx: fix stack leak in tagged FIFO buffer", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.