BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-38736High confidence

net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization

Linux · Linux

Official source article: Siemens SSA-019113 ↗. Check the applicable product and release in the original source.

7.1HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 15 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.17% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 15 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

13 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 9 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.48-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.153-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
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.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-032379 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-032379: Multiple Vulnerabilities in SIMATIC CN 4100 Before V5.0
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC CN 4100
Summary
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.
Remediation
Update to V5.0 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-31553

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 15 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Out-of-bounds Read → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-125
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2025-31553Official EUVD mapping

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.

Official EUVD record ↗
BSI · German · WID-SEC-2025-1988Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250910Security Bulletin 10 SEP 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 10 SEP 2025, published on 10 September 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0880Multiples vulnérabilités dans les produits Siemens

25-21919, CVE-2025-21925, CVE-2025-21926, CVE-2025-21938, CVE-2025-21959, CVE-2025-21999, CVE-2025-22005, CVE-2025-22015, CVE-2025-22055, CVE-2025-22056, CVE-2025-22060, CVE-2025-22083, CVE-2025-22090, CVE-2025-22095, CVE-2025-22107, CVE-2025-22111, CVE-2025-22121, CVE-2025-23136, CVE-2025-23143, CVE-2025-37785, CVE-2025-37909, CVE-2025-37917, CVE-2025-37945, CVE-2025-37959, CVE-2025-37964, CVE-2025-37972, CVE-2025-37980, CVE-2025-38125, CVE-2025-38162, CVE-2025-38192, CVE-2025-38201, CVE-2025-38232, CVE-2025-38322, CVE-2025-38591, CVE-2025-38614, CVE-2025-38681, CVE-2025-38704, CVE-2025-38721, CVE-2025-38725, CVE-2025-38727, CVE-2025-38732, CVE-2025-38736, CVE-2025-39681, CVE-2025-39691, CVE-2025-39721, CVE-2025-39748, CVE-2025-39756, CVE-2025-39764, CVE-2025-39770, CVE-2025-39773, CVE-2025-39782, CVE-2025-39795, CVE-2025-39826, CVE-2025-39827, CVE-2025-39845, CVE-2025-39866, CVE-2025-39871, CVE-2025-39931, CVE-2025-39953, CVE-2025-39955, CVE-2025-39964, CVE-2025-39977, CVE-2025-39978, CVE-2025-39980, CVE-2025-40022, CVE-2025-40070, CVE-2025-40078, CVE-2025-40080, CVE-2025-40105, CVE-2025-40135, CVE-2025-40149, CVE-2025-40219, CVE-2025-40261, CVE-2025-40300, CVE-2025-61984, CVE-2025-61985, CVE-2025-68206, CVE-2025-68261, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291, CVE-2025

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0565Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2025-38721 Référence CVE CVE-2025-38723 https://www.cve.org/CVERecord?id=CVE-2025-38723 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38735 https://www.cve.org/CVERecord?id=CVE-2025-38735 Référence CVE CVE-2025-38736 https://www.cve.org/CVERecord?id=CVE-2025-38736 Référence CVE CVE-2025-39673 https://www.cve.org/CVERecord?id=CVE-2025-39673 Référence CVE CVE-2025-39675 https://www.cve.org/CVERecord?id=CVE-2025-39675 Référence CVE CVE-2025-39676 https://www.cve.org/CVERecord?id=CVE-2025-39676 Référence CVE CVE-2025-39681 https://www.cve.org/CVERecord?id=CVE-2025-39681 Référence CVE CVE-2025-39682 https://www.cve.org/CVERecord?id=CVE-2025-39682 Référence CVE CVE-2025-39683 https://www.cve.org/CVERecord?id=CVE-2025-39683 Référence CVE CVE-2025-39684 https://www.cve.org/CVERecord?id=CVE-2025-39684 Référence CVE CVE-2025-39685 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1073Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38733 https://www.cve.org/CVERecord?id=CVE-2025-38733 Référence CVE CVE-2025-38734 https://www.cve.org/CVERecord?id=CVE-2025-38734 Référence CVE CVE-2025-38735 https://www.cve.org/CVERecord?id=CVE-2025-38735 Référence CVE CVE-2025-38736 https://www.cve.org/CVERecord?id=CVE-2025-38736 Référence CVE CVE-2025-39673 https://www.cve.org/CVERecord?id=CVE-2025-39673 Référence CVE CVE-2025-39675 https://www.cve.org/CVERecord?id=CVE-2025-39675 Référence CVE CVE-2025-39676 https://www.cve.org/CVERecord?id=CVE-2025-39676 Référence CVE CVE-2025-39677 https://www.cve.org/CVERecord?id=CVE-2025-39677 Référence CVE CVE-2025-39678 https://www.cve.org/CVERecord?id=CVE-2025-39678 Référence CVE CVE-2025-39679 https://www.cve.org/CVERecord?id=CVE-2025-39679 Référence CVE CVE-2025-39681 https://www.cve.org/CVERecord?id=CVE-2025-39681 Référence CVE CVE-2025-39682 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1032Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38734 https://www.cve.org/CVERecord?id=CVE-2025-38734 Référence CVE CVE-2025-38735 https://www.cve.org/CVERecord?id=CVE-2025-38735 Référence CVE CVE-2025-38736 https://www.cve.org/CVERecord?id=CVE-2025-38736 Référence CVE CVE-2025-39673 https://www.cve.org/CVERecord?id=CVE-2025-39673 Référence CVE CVE-2025-39675 https://www.cve.org/CVERecord?id=CVE-2025-39675 Référence CVE CVE-2025-39676 https://www.cve.org/CVERecord?id=CVE-2025-39676 Référence CVE CVE-2025-39679 https://www.cve.org/CVERecord?id=CVE-2025-39679 Référence CVE CVE-2025-39683 https://www.cve.org/CVERecord?id=CVE-2025-39683 Référence CVE CVE-2025-39684 https://www.cve.org/CVERecord?id=CVE-2025-39684 Référence CVE CVE-2025-39685 https://www.cve.org/CVERecord?id=CVE-2025-39685 Référence CVE CVE-2025-39686 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1009Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38734 https://www.cve.org/CVERecord?id=CVE-2025-38734 Référence CVE CVE-2025-38735 https://www.cve.org/CVERecord?id=CVE-2025-38735 Référence CVE CVE-2025-38736 https://www.cve.org/CVERecord?id=CVE-2025-38736 Référence CVE CVE-2025-39673 https://www.cve.org/CVERecord?id=CVE-2025-39673 Référence CVE CVE-2025-39675 https://www.cve.org/CVERecord?id=CVE-2025-39675 Référence CVE CVE-2025-39676 https://www.cve.org/CVERecord?id=CVE-2025-39676 Référence CVE CVE-2025-39679 https://www.cve.org/CVERecord?id=CVE-2025-39679 Référence CVE CVE-2025-39683 https://www.cve.org/CVERecord?id=CVE-2025-39683 Référence CVE CVE-2025-39684 https://www.cve.org/CVERecord?id=CVE-2025-39684 Référence CVE CVE-2025-39685 https://www.cve.org/CVERecord?id=CVE-2025-39685 Référence CVE CVE-2025-39686 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0921Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-38722 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38734 https://www.cve.org/CVERecord?id=CVE-2025-38734 Référence CVE CVE-2025-38735 https://www.cve.org/CVERecord?id=CVE-2025-38735 Référence CVE CVE-2025-38736 https://www.cve.org/CVERecord?id=CVE-2025-38736 Référence CVE CVE-2025-39675 https://www.cve.org/CVERecord?id=CVE-2025-39675 Référence CVE CVE-2025-39677 https://www.cve.org/CVERecord?id=CVE-2025-39677 Référence CVE CVE-2025-39678 https://www.cve.org/CVERecord?id=CVE-2025-39678 Référence CVE CVE-2025-39679 https://www.cve.org/CVERecord?id=CVE-2025-39679 Référence CVE CVE-2025-39681 https://www.cve.org/CVERecord?id=CVE-2025-39681 Référence CVE CVE-2025-39682 https://www.cve.org/CVERecord?id=CVE-2025-39682 Référence CVE CVE-2025-39684 https://www.cve.org/CVERecord?id=CVE-2025-39684 Référence CVE CVE-2025-39685 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0895Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-38722 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38734 https://www.cve.org/CVERecord?id=CVE-2025-38734 Référence CVE CVE-2025-38735 https://www.cve.org/CVERecord?id=CVE-2025-38735 Référence CVE CVE-2025-38736 https://www.cve.org/CVERecord?id=CVE-2025-38736 Référence CVE CVE-2025-39675 https://www.cve.org/CVERecord?id=CVE-2025-39675 Référence CVE CVE-2025-39677 https://www.cve.org/CVERecord?id=CVE-2025-39677 Référence CVE CVE-2025-39678 https://www.cve.org/CVERecord?id=CVE-2025-39678 Référence CVE CVE-2025-39679 https://www.cve.org/CVERecord?id=CVE-2025-39679 Référence CVE CVE-2025-39681 https://www.cve.org/CVERecord?id=CVE-2025-39681 Référence CVE CVE-2025-39682 https://www.cve.org/CVERecord?id=CVE-2025-39682 Référence CVE CVE-2025-39684 https://www.cve.org/CVERecord?id=CVE-2025-39684 Référence CVE CVE-2025-39685 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0894Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2025-38721 Référence CVE CVE-2025-38723 https://www.cve.org/CVERecord?id=CVE-2025-38723 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38735 https://www.cve.org/CVERecord?id=CVE-2025-38735 Référence CVE CVE-2025-38736 https://www.cve.org/CVERecord?id=CVE-2025-38736 Référence CVE CVE-2025-39673 https://www.cve.org/CVERecord?id=CVE-2025-39673 Référence CVE CVE-2025-39675 https://www.cve.org/CVERecord?id=CVE-2025-39675 Référence CVE CVE-2025-39676 https://www.cve.org/CVERecord?id=CVE-2025-39676 Référence CVE CVE-2025-39681 https://www.cve.org/CVERecord?id=CVE-2025-39681 Référence CVE CVE-2025-39682 https://www.cve.org/CVERecord?id=CVE-2025-39682 Référence CVE CVE-2025-39683 https://www.cve.org/CVERecord?id=CVE-2025-39683 Référence CVE CVE-2025-39684 https://www.cve.org/CVERecord?id=CVE-2025-39684 Référence CVE CVE-2025-39685 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0825Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38733 https://www.cve.org/CVERecord?id=CVE-2025-38733 Référence CVE CVE-2025-38734 https://www.cve.org/CVERecord?id=CVE-2025-38734 Référence CVE CVE-2025-38735 https://www.cve.org/CVERecord?id=CVE-2025-38735 Référence CVE CVE-2025-38736 https://www.cve.org/CVERecord?id=CVE-2025-38736 Référence CVE CVE-2025-38737 https://www.cve.org/CVERecord?id=CVE-2025-38737 Référence CVE CVE-2025-39673 https://www.cve.org/CVERecord?id=CVE-2025-39673 Référence CVE CVE-2025-39675 https://www.cve.org/CVERecord?id=CVE-2025-39675 Référence CVE CVE-2025-39676 https://www.cve.org/CVERecord?id=CVE-2025-39676 Référence CVE CVE-2025-39679 https://www.cve.org/CVERecord?id=CVE-2025-39679 Référence CVE CVE-2025-39681 https://www.cve.org/CVERecord?id=CVE-2025-39681 Référence CVE CVE-2025-39682 https://www.cve.org/CVERecord?id=CVE-2025-39682 Référence CVE CVE-2025-39683 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-024405Debian等の複数ベンダの製品における境界外読み取りに関する脆弱性

Linuxカーネルのnet usb asix_devicesに、MDIOバス初期化時のPHYアドレスマスク処理に関する脆弱性が存在しました。PHYアドレスを正しく5ビット(0〜31)でマスクせずに処理した場合、無効なPHYアドレスが使用され、予期しない動作や例外が発生する可能性がありました。この問題は、PHYアドレスに0x1fのマスクを適用することで修正されています。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0147Kwetsbaarheden verholpen in Siemens-producten

Multiple security fixes were applied across various SUSE Linux Enterprise and Micro kernel versions, addressing vulnerabilities such as race conditions, use-after-free bugs, memory leaks, null pointer dereferences, and a specific fix in the Linux kernel asix_devices USB network driver for PHY address masking.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 5 Sept 2025 · Last source change 8 Sept 2026, 08:42 UTC · CWE-125 · Out-of-bounds Read

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-31553
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    75947d3200de98a9ded9ad8972e02f1a177097fe < fcb4ce9f729c1d08e53abf9d449340e24c3edee6; 59ed6fbdb1bc03316e09493ffde7066f031c7524 < 8f141f2a4f2ef8ca865d5921574c3d6535e00a49; ccef5ee4adf56472aa26bdd1f821a6d0cd06089a < 748da80831221ae24b4bc8d7ffb22acd5712a341; ee2cd40b0bb46056949a2319084a729d95389386 < 22042ffedd8c2c6db08ccdd6d4273068eddd3c5c; ad1f8313aeec0115f9978bd2d002ef4a8d96c773 < 523eab02fce458fa6d3c51de5bb055800986953e; 4faff70959d51078f9ee8372f8cff0d7045e4114 < 24ef2f53c07f273bad99173e27ee88d44d135b1c; a754ab53993b1585132e871c5d811167ad3c52ff; 6.15.11 < 6.16 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    Linux: 75947d3200de98a9ded9ad8972e02f1a177097fe < fcb4ce9f729c1d08e53abf9d449340e24c3edee6, 59ed6fbdb1bc03316e09493ffde7066f031c7524 < 8f141f2a4f2ef8ca865d5921574c3d6535e00a49, ccef5ee4adf56472aa26bdd1f821a6d0cd06089a < 748da80831221ae24b4bc8d7ffb22acd5712a341, ee2cd40b0bb46056949a2319084a729d95389386 < 22042ffedd8c2c6db08ccdd6d4273068eddd3c5c, ad1f8313aeec0115f9978bd2d002ef4a8d96c773 < 523eab02fce458fa6d3c51de5bb055800986953e, 4faff70959d51078f9ee8372f8cff0d7045e4114 < 24ef2f53c07f273bad99173e27ee88d44d135b1c, a754ab53993b1585132e871c5d811167ad3c52ff, 6.15.11 < 6.16, 6.12.43 < 6.12.44, 6.16.2 < 6.16.4 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-38736 · cve.blacktree.nl