Linux Kernel up to a754ab53993b1585132e871c5d811167ad3c52ff net asix_devices initialization

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Linux Kernel up to 6.12.43/6.16.3/6.17-rc1/6.17-rc2/a754ab53993b1585132e871c5d811167ad3c52ff. Impacted is the function asix_devices of the component net. The manipulation leads to initialization.
This vulnerability is uniquely identified as CVE-2025-38736. No exploit exists.
You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.12.43/6.16.3/6.17-rc1/6.17-rc2/a754ab53993b1585132e871c5d811167ad3c52ff. This issue affects the function asix_devices of the component net. The manipulation with an unknown input leads to a initialization vulnerability. Using CWE to declare the problem leads to CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. The impact remains unknown. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization Syzbot reported shift-out-of-bounds exception on MDIO bus initialization. The PHY address should be masked to 5 bits (0-31). Without this mask, invalid PHY addresses could be used, potentially causing issues with MDIO bus operations. Fix this by masking the PHY address with 0x1f (31 decimal) to ensure it stays within the valid range.
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2025-38736 since 04/16/2025. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/09/2026).
The vulnerability scanner Nessus provides a plugin with the ID 261652 (Linux Distros Unpatched Vulnerability : CVE-2025-38736), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 6.12.44, 6.16.4, 6.17-rc2 or 6.17-rc3 eliminates this vulnerability. Applying the patch fcb4ce9f729c1d08e53abf9d449340e24c3edee6/8f141f2a4f2ef8ca865d5921574c3d6535e00a49/748da80831221ae24b4bc8d7ffb22acd5712a341/22042ffedd8c2c6db08ccdd6d4273068eddd3c5c/523eab02fce458fa6d3c51de5bb055800986953e/24ef2f53c07f273bad99173e27ee88d44d135b1c is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (261652) and CERT Bund (WID-SEC-2025-1988). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Debian Linux
- Google Cloud Platform
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- NetApp FAS
- NetApp AFF
- NetApp ActiveIQ Unified Manager
- SUSE openSUSE
- RESF Rocky Linux
- Open Source Linux Kernel
- Microsoft Azure
- Dell Secure Connect Gateway
- IBM QRadar SIEM
- IBM Security Verify Access
- Dell NetWorker
Product
Type
Vendor
Name
Version
- 6.12.0
- 6.12.1
- 6.12.2
- 6.12.3
- 6.12.4
- 6.12.5
- 6.12.6
- 6.12.7
- 6.12.8
- 6.12.9
- 6.12.10
- 6.12.11
- 6.12.12
- 6.12.13
- 6.12.14
- 6.12.15
- 6.12.16
- 6.12.17
- 6.12.18
- 6.12.19
- 6.12.20
- 6.12.21
- 6.12.22
- 6.12.23
- 6.12.24
- 6.12.25
- 6.12.26
- 6.12.27
- 6.12.28
- 6.12.29
- 6.12.30
- 6.12.31
- 6.12.32
- 6.12.33
- 6.12.34
- 6.12.35
- 6.12.36
- 6.12.37
- 6.12.38
- 6.12.39
- 6.12.40
- 6.12.41
- 6.12.42
- 6.12.43
- 6.16.0
- 6.16.1
- 6.16.2
- 6.16.3
- 6.17-rc1
- 6.17-rc2
- a754ab53993b1585132e871c5d811167ad3c52ff
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.1
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: InitializationCWE: CWE-665
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 261652
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-38736
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.12.44/6.16.4/6.17-rc2/6.17-rc3
Patch: fcb4ce9f729c1d08e53abf9d449340e24c3edee6/8f141f2a4f2ef8ca865d5921574c3d6535e00a49/748da80831221ae24b4bc8d7ffb22acd5712a341/22042ffedd8c2c6db08ccdd6d4273068eddd3c5c/523eab02fce458fa6d3c51de5bb055800986953e/24ef2f53c07f273bad99173e27ee88d44d135b1c
Timeline
04/16/2025 CVE reserved09/05/2025 Advisory disclosed
09/05/2025 VulDB entry created
02/09/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2025-38736 (🔒)
GCVE (CVE): GCVE-0-2025-38736
GCVE (VulDB): GCVE-100-322877
CERT Bund: WID-SEC-2025-1988 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 09/05/2025 21:40Updated: 02/09/2026 11:22
Changes: 09/05/2025 21:40 (59), 09/07/2025 00:46 (2), 09/09/2025 06:17 (7), 11/06/2025 14:34 (1), 11/25/2025 15:05 (1), 11/27/2025 13:57 (1), 12/29/2025 11:03 (1), 01/05/2026 10:09 (1), 01/09/2026 06:57 (11), 01/26/2026 11:25 (1), 02/09/2026 11:22 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.