Skip to main content
VulnerabilityPublished Updated

CVE-2025-38086: Linux kernel · net: ch9200: fix uninitialised access during mii_nway_restart

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in cdaa6d1cb2ff1219c6c822b27655dd170ffb0f72 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:04 UTC

Severity
Unrated

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

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in cdaa6d1cb2ff1219c6c822b27655dd170ffb0f72, 119766de4930ff40db9f36b960cb53b0c400e81b, 33163c68d2e3061fa3935b5f0a1867958b1cdbd2 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 4a476bd6d1d923922ec950ddc4c27b279f6901eb, < cdaa6d1cb2ff1219c6c822b27655dd170ffb0f72
Fixed in
  • cdaa6d1cb2ff1219c6c822b27655dd170ffb0f72
LinuxLinuxAffected
  • ≥ 4a476bd6d1d923922ec950ddc4c27b279f6901eb, < 119766de4930ff40db9f36b960cb53b0c400e81b
Fixed in
  • 119766de4930ff40db9f36b960cb53b0c400e81b
LinuxLinuxAffected
  • ≥ 4a476bd6d1d923922ec950ddc4c27b279f6901eb, < 33163c68d2e3061fa3935b5f0a1867958b1cdbd2
Fixed in
  • 33163c68d2e3061fa3935b5f0a1867958b1cdbd2
LinuxLinuxAffected
  • ≥ 4a476bd6d1d923922ec950ddc4c27b279f6901eb, < 9da3e442714f7f4393ff01c265c4959c03e88c2f
Fixed in
  • 9da3e442714f7f4393ff01c265c4959c03e88c2f
LinuxLinuxAffected
  • ≥ 4a476bd6d1d923922ec950ddc4c27b279f6901eb, < 9ad0452c0277b816a435433cca601304cfac7c21
Fixed in
  • 9ad0452c0277b816a435433cca601304cfac7c21
LinuxLinuxAffected
  • ≥ 4a476bd6d1d923922ec950ddc4c27b279f6901eb, < 9a350f30d65197354706b7759b5c89d6c267b1a9
Fixed in
  • 9a350f30d65197354706b7759b5c89d6c267b1a9

Description

In the Linux kernel, the following vulnerability has been resolved: net: ch9200: fix uninitialised access during mii_nway_restart In mii_nway_restart() the code attempts to call mii->mdio_read which is ch9200_mdio_read(). ch9200_mdio_read() utilises a local buffer called "buff", which is initialised with control_read(). However "buff" is conditionally initialised inside control_read(): if (err == size) { memcpy(data, buf, size); } If the condition of "err == size" is not met, then "buff" remains uninitialised. Once this happens the uninitialised "buff" is accessed and returned during ch9200_mdio_read(): return (buff[0] | buff[1] << 8); The problem stems from the fact that ch9200_mdio_read() ignores the return value of control_read(), leading to uinit-access of "buff". To fix this we should check the return value of control_read() and return early on error.

References

Community reviews

Loading reviews…