VulnerabilityPublished 19 Jul 2026

CVE-2026-63877: Linux kernel · serial: dz: Convert to use a platform device

Affects Linux kernelSource GCVE Database

Compare

Not known to be exploited.

Data as of 30 Oct 2026, 15:35 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.

What to do

AI-suggested

A fix has been implemented in the Linux kernel by converting the DZ serial driver to use a platform device and updating resource handling accordingly. Users should update to a kernel version that includes this fix. No additional mitigation steps are indicated.

Description

A vulnerability in the Linux kernel's DZ serial driver caused a crash during initialization of the first serial port due to dereferencing a null-derived pointer. The issue was resolved by converting the driver to use a platform device, improving resource handling and device probing. This change also affects the timing of console handover during system bootstrap.

Impact

The vulnerability caused a kernel crash (Oops) during the initialization of the first serial port, potentially leading to system instability or denial of service. It did not describe remote code execution or privilege escalation. The impact is limited to local system stability during boot or serial port initialization.

Summary

The Linux kernel's DZ serial driver had a flaw where it dereferenced a pointer derived from a null pointer to the port's parent device, leading to a kernel crash during serial port initialization. The fix involved switching the driver to use a platform device as the port's parent device, updating resource management to request only the actual address span used, and employing platform_driver_probe() to handle device binding properly. This approach avoids conflicts with other drivers sharing the same major device number and aligns with modern device discovery methods. The fix also results in the console handover occurring later in the boot process, which is compatible with the firmware console handler and allows improved delay handling.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 30 Oct 2026, 15:35 UTC

Technical details

References

Community reviews

Related threats