VulnerabilityPublished 19 Jul 2026

CVE-2026-63936: Linux kernel · iio: adc: mt6359: fix unchecked return value in mt6358_read_imp

Source GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-856p-gwqh-fxcq

What to do

AI-suggested

A fix has been implemented that initializes the variable val_v to zero in the affected function, preventing uninitialized use and data leakage. Users should apply the official Linux kernel updates that include this fix. Since this is a kernel-level vulnerability, updating to a patched kernel version is the recommended remediation. Patch status is not explicitly stated here; check the Linux kernel vendor advisory for the specific fixed versions and update accordingly.

Description

A vulnerability in the Linux kernel's iio adc mt6359 driver involved an unchecked return value in the mt6358_read_imp() function. If the regmap_read() call failed, an uninitialized variable could lead to random stack data being reported as measurement results. This could potentially leak stack data. The issue has been resolved by initializing the variable to zero to prevent uninitialized use and data leakage.

References

Community reviews

Loading reviews…