LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38111: net/mdiobus: Fix potential out-of-bounds read/write access

In the Linux kernel, the following vulnerability has been resolved: net/mdiobus: Fix potential out-of-bounds read/write access When using publicly available tools like 'mdio-tools' to read/write data from/to network interface and its PHY via mdiobus, there is no verification of parameters passed to the ioctl and it accepts any mdio address. Currently there is support for 32 addresses in kernel via PHY_MAX_ADDR define, but it is possible to pass higher value than that via ioctl. While read/write operation should generally fail in this case, mdiobus provides stats array, where wrong address may allow out-of-bounds read/write. Fix that by adding address verification before read/write operation. While this excludes this access from any statistics, it improves security of read/write operation.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A local user with limited privileges and access to Linux MDIO operations may supply an invalid PHY address, causing kernel memory to be read or modified outside an intended statistics array. This could affect confidentiality, integrity, or availability. It is not described as remotely exploitable.

Executive priority

Treat as a high-priority local kernel issue, especially for shared systems and network or industrial appliances. It does not justify the urgency of a confirmed remote or actively exploited flaw, but patching should follow promptly because successful abuse could affect kernel memory and system stability.

Technical view

The mdiobus ioctl path accepted PHY addresses beyond the kernel’s 32-address limit. Although the underlying MDIO operation would generally fail, the invalid index could access memory outside the mdiobus statistics array. The kernel fix validates the address before read or write processing.

Likely exposure

Exposure is most likely on affected Linux systems where local users or processes can issue mdiobus ioctls against network interfaces and PHY hardware. Internet exposure alone is insufficient. The bundle identifies affected kernel versions and stable fixes, but exact distribution and appliance status requires vendor confirmation.

Exploitation context

The CVSS vector indicates local access, low privileges, low complexity, and no user interaction. The source bundle does not report active exploitation, and the CVE is not listed as KEV. Public tools such as mdio-tools can reach the vulnerable interface, but tool availability alone does not establish exploitability.

Researcher notes

The defect is an unchecked MDIO address used in statistics-array indexing. The documented correction adds address validation before read/write operations, excluding invalid accesses from statistics. Sources do not establish reliable exploitation, resulting primitives, or observed attacks. Researchers should avoid assuming privilege escalation without further evidence.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable stable fix.
  • Check Linux distribution and appliance advisories for backported fixes.
  • Restrict untrusted local access to MDIO-capable interfaces until patched.
  • Prioritize exposed multi-user, embedded, networking, and industrial Linux systems.

Validation and detection

  • Record running kernel versions across potentially affected Linux assets.
  • Confirm fix inclusion using vendor advisories or applicable stable commit history.
  • Identify which users and processes can issue mdiobus ioctls.
  • After updating, verify the fixed kernel is running following reboot.
  • Review local telemetry for unusual MDIO access or kernel faults.
Prepared
Confidence
high
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38111 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
11Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38111Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux080bb352fad00d04995102f681b134e3754bfb6e, 080bb352fad00d04995102f681b134e3754bfb6e, 080bb352fad00d04995102f681b134e3754bfb6e, 080bb352fad00d04995102f681b134e3754bfb6e, 080bb352fad00d04995102f681b134e3754bfb6e, 080bb352fad00d04995102f681b134e3754bfb6e, 080bb352fad00d04995102f681b134e3754bfb6eunaffected
LinuxLinux5.6, 0, 5.10.239, 5.15.186, 6.1.142, 6.6.94, 6.12.34, 6.15.3, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.