VulnerabilityPublished 19 Jul 2026

CVE-2026-63932: Linux kernel · iio: chemical: mhz19b: reject oversized serial replies

Source GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 15:59 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-vrpq-2gcp-g727

What to do

AI-suggested

A fix has been implemented in the Linux kernel to address this vulnerability by rejecting oversized serial replies and preventing buffer overflow. Users should update their Linux kernel to a version that includes this fix. Patch status is not explicitly confirmed in the provided data; therefore, check the official Linux kernel advisories or vendor updates for the exact fixed versions and apply the update accordingly.

Description

A vulnerability in the Linux kernel's iio chemical mhz19b driver allowed oversized serial replies to overflow a fixed-size buffer. The function mhz19b_receive_buf() did not properly check that incoming serial data chunks fit within the allocated buffer, potentially causing a buffer overflow. This issue has been resolved by resetting the reply state before each command and rejecting oversized replies, returning an error instead of overwriting the buffer.

References

Community reviews

Loading reviews…