CVE-2023-53238: phy: hisilicon: Fix an out of bounds check in hisi_inno_phy_probe()
In the Linux kernel, the following vulnerability has been resolved:
phy: hisilicon: Fix an out of bounds check in hisi_inno_phy_probe()
The size of array 'priv->ports[]' is INNO_PHY_PORT_NUM.
In the for loop, 'i' is used as the index for array 'priv->ports[]'
with a check (i > INNO_PHY_PORT_NUM) which indicates that
INNO_PHY_PORT_NUM is allowed value for 'i' in the same loop.
This > comparison needs to be changed to >=, otherwise it potentially leads
to an out of bounds write on the next iteration through the loop
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel bug in a Hisilicon PHY driver. A boundary check can allow memory access past a fixed ports array. On affected systems, a local low-privileged user could potentially cause serious confidentiality impact or system availability loss. Exposure is likely limited to systems using the relevant driver and hardware.
Executive priority
Treat as high priority for Linux fleets with Hisilicon-based platforms or custom kernels. For general server fleets without this hardware or driver, validate exposure first, then patch through normal kernel maintenance. No active exploitation evidence is provided.
Technical view
In hisi_inno_phy_probe(), the code checked whether an index was greater than INNO_PHY_PORT_NUM instead of greater than or equal to it. That permits INNO_PHY_PORT_NUM as an array index for priv->ports[], creating an out-of-bounds condition. Kernel stable commits correct the bounds check.
Likely exposure
The CVSS vector is local, low complexity, low privileges, and no user interaction. Internet-facing exposure is not indicated. Risk is concentrated on affected Linux kernels where the Hisilicon Inno PHY driver is present, built, and reachable on relevant hardware.
Exploitation context
The provided sources do not show CISA KEV listing or other evidence of active exploitation. The impact is still meaningful because successful misuse occurs in kernel context, but exploitation details and real-world abuse are not established in the bundle.
Researcher notes
The source description says out-of-bounds write, while the supplied CWE is CWE-125, which usually denotes out-of-bounds read. Analysts should preserve that discrepancy and rely on the kernel commit context when classifying internal findings.
Mitigation direction
Update affected Linux kernels using vendor or distribution-supported packages.
Track the listed upstream stable commits in kernel maintenance planning.
Prioritize systems using Hisilicon PHY hardware or the affected driver.
Check distribution advisories before relying on upstream version assumptions.
Limit local untrusted access on exposed affected systems until patched.
Validation and detection
Inventory Linux kernel versions against the affected version list.
Confirm whether the Hisilicon Inno PHY driver is built or loaded.
Map affected assets to hardware platforms using this PHY driver.
Verify installed kernel packages include the relevant stable fix.
Document distro advisory status where upstream and vendor versions differ.
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.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.