CVE-2025-38110: net/mdiobus: Fix potential out-of-bounds clause 45 read/write access
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 260388f79e94fb3026c419a208ece8358bb7b555, 31bf7b2b92563a352788cf9df3698682f659bacc, 4ded22f7f3ce9714ed72c3e9c68fea1cb9388ae7; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1; azl3 kernel 6.6.96.1-1 on Azure Linux 3.0 6.6.96.1-1.
Low priority for now. Upgrade to Linux Linux 260388f79e94fb3026c419a208ece8358bb7b555, 31bf7b2b92563a352788cf9df3698682f659bacc, 4ded22f7f3ce9714ed72c3e9c68fea1cb9388ae7; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1; azl3 kernel 6.6.96.1-1 on Azure Linux 3.0 6.6.96.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: net/mdiobus: Fix potential out-of-bounds clause 45 read/write access When using publicly available tools like 'mdio-tools' to read/write data from/to network interface and its PHY via C45 (clause 45) 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 C45 read/write operation. While this excludes this access from any statistics, it improves security of read/write operation.
- BDU:2025-09684
- ALSA-2025:11855
- ALSA-2025:11861
- RHSA-2025:11245
- RHSA-2025:11855
- RHSA-2025:11861
- RLSA-2025:11855
- RLSA-2025:11861
- SUSE-SU-2025:03636-1
- SUSE-SU-2025:03638-1
- SUSE-SU-2025:03650-1
- SUSE-SU-2025:20873-1
- SUSE-SU-2025:20874-1
- SUSE-SU-2025:20875-1
- SUSE-SU-2025:20876-1
- SUSE-SU-2025:20877-1
- SUSE-SU-2025:20878-1
- SUSE-SU-2025:20881-1
- SUSE-SU-2025:20882-1
- SUSE-SU-2025:20883-1
- Published
- Jul 3, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- CWE-125
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.1
- CNA · Linux
- 7.8
- 0.7 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.3 and later · before 6.6.94
- linux linux kernel6.7 and later · before 6.12.34
- linux linux kernel6.13 and later · before 6.15.3
- linux linux kernel6.16
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.3affected
- 4e4aafcddbbfcdd6eed5780e190fcbfac8b4685a and later · before abb0605ca00979a49572a6516f6db22c3dc57223affected · git
- 4e4aafcddbbfcdd6eed5780e190fcbfac8b4685a and later · before 31bf7b2b92563a352788cf9df3698682f659baccaffected · git
- 4e4aafcddbbfcdd6eed5780e190fcbfac8b4685a and later · before 4ded22f7f3ce9714ed72c3e9c68fea1cb9388ae7affected · git
- 4e4aafcddbbfcdd6eed5780e190fcbfac8b4685a and later · before 260388f79e94fb3026c419a208ece8358bb7b555affected · git
- before 6.3not affected · semver
- 6.6.94 and later · up to and including 6.6.*not affected · semver
- 6.12.34 and later · up to and including 6.12.*not affected · semver
- 6.15.3 and later · up to and including 6.15.*not affected · semver
- 6.16 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-55.24.1.el10_0 | 6.12.0-55.24.1.el10_0 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-55.24.1.el10_0 | 6.12.0-55.24.1.el10_0 |
| AlmaLinux:9 | kernel | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-core | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38107Jul 3, 2025 · net_sched: ets: fix a race in ets_qdisc_change()28Monitor
- ← EarlierCVE-2025-38108Jul 3, 2025 · net_sched: red: fix a race in __red_change()28Monitor
- Later →CVE-2025-38111Jul 3, 2025 · net/mdiobus: Fix potential out-of-bounds read/write access28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 260388f79e94fb3026c419a208ece8358bb7b555 | Vendor (CNA) |
| Linux Linux | 31bf7b2b92563a352788cf9df3698682f659bacc | Vendor (CNA) |
| Linux Linux | 4ded22f7f3ce9714ed72c3e9c68fea1cb9388ae7 | Vendor (CNA) |
| Linux Linux | abb0605ca00979a49572a6516f6db22c3dc57223 | Vendor (CNA) |
| azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 | 6.6.96.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.96.1-1 on Azure Linux 3.0 | 6.6.96.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 6.12.0-55.24.1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-doc | 6.12.0-55.24.1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.12.35-1 · Debian:13 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.77.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.77.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.77.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.77.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.77.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.77.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.77.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.77.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.77.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.77.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-427.77.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
+14
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.