Kernel disclosure and crash via unchecked MDIO address
Published Jul 3, 2025 · Updated Aug 5, 2026
Out-of-bounds access in Linux kernel branches since 5.6 allows local users to read kernel data or interrupt service through an MDIO ioctl. The mdiobus ioctl accepts addresses above PHY_MAX_ADDR, then uses the unchecked address to index its per-address statistics array. The path requires local low-privileged access and an MDIO-capable network interface; reads disclose kernel memory, while writes corrupt memory and can crash the system.
Summary
What happened
Out-of-bounds access in Linux kernel branches since 5.6 allows local users to read kernel data or interrupt service through an MDIO ioctl. The mdiobus ioctl accepts addresses above PHY_MAX_ADDR, then uses the unchecked address to index its per-address statistics array. The path requires local low-privileged access and an MDIO-capable network interface; reads disclose kernel memory, while writes corrupt memory and can crash the system.
The record
- CVE
- CVE-2025-38111
- Published
- Jul 3, 2025
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 3, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=V3.1.5 <*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo