LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27047: net: phy: fix phy_get_internal_delay accessing an empty array

In the Linux kernel, the following vulnerability has been resolved: net: phy: fix phy_get_internal_delay accessing an empty array The phy_get_internal_delay function could try to access to an empty array in the case that the driver is calling phy_get_internal_delay without defining delay_values and rx-internal-delay-ps or tx-internal-delay-ps is defined to 0 in the device-tree. This will lead to "unable to handle kernel NULL pointer dereference at virtual address 0". To avoid this kernel oops, the test should be delay >= 0. As there is already delay < 0 test just before, the test could only be size == 0.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash affected systems when certain Ethernet PHY configuration data is present but the driver lacks matching delay values. The source describes a kernel NULL pointer dereference, not data theft or remote code execution. Business urgency is mainly availability risk on systems using impacted kernels and relevant network hardware/device-tree settings.

Executive priority

Treat as a targeted availability and reliability issue, not an internet-wide emergency based on current evidence. Prioritize embedded, operational, and vendor-managed systems where a kernel crash could disrupt service or physical operations.

Technical view

phy_get_internal_delay could access an empty delay_values array when rx-internal-delay-ps or tx-internal-delay-ps is set to 0 in device tree and the driver did not define delay_values. The failure results in a kernel oops. Upstream stable commits correct the size check logic.

Likely exposure

Exposure is most likely on Linux systems, especially embedded or appliance-style deployments, using affected kernel ranges and Ethernet PHY drivers with the described device-tree delay properties. Generic Linux presence alone is not enough to prove exposure.

Exploitation context

The provided sources do not show active exploitation, and CISA KEV status is false. The described impact is a kernel crash condition triggered by specific configuration and driver behavior. No public source in the bundle supports remote exploitation or privilege escalation.

Researcher notes

Severity metadata, CVSS, and CWE are absent from the bundle. The root condition is narrow: driver calls phy_get_internal_delay without delay_values while the device tree supplies zero internal delay. Analysis should focus on kernel branch, backport status, hardware PHY driver, and device-tree configuration.

Mitigation direction

  • Apply a vendor kernel update that includes the referenced upstream stable fixes.
  • For Debian systems, review the Debian LTS advisory and install applicable kernel packages.
  • For Siemens products, follow Siemens SSA-265688 product-specific guidance.
  • If no vendor package is available, confirm whether the relevant stable commit is backported.
  • Avoid changing device-tree PHY delay settings without vendor validation.

Validation and detection

  • Inventory Linux kernel versions across affected servers, appliances, and embedded systems.
  • Check whether deployed device trees define rx-internal-delay-ps or tx-internal-delay-ps as 0.
  • Confirm whether the running kernel contains one of the referenced stable fixes.
  • Review boot and kernel logs for NULL pointer dereference or PHY initialization oops messages.
  • Test network initialization after patching on representative hardware.
Prepared
Confidence
medium
Sources
11

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-2024-27047 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
3ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux92252eec913b2dd5e7b5de11ea3efa2e64d65cf4, 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4, 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4, 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4, 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4, 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4, 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4unaffected
LinuxLinux5.9, 0, 5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

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