Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-27047, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4 – < 06dd21045a7e8bc8701b0ebedcd9a30a6325878b
    • affected 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4 – < 0e939a002c8a7d66e60bd0ea6b281fb39d713c1a
    • affected 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4 – < 2a2ff709511617de9c6c072eeee82bcbbdfecaf8
    • affected 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4 – < 589ec16174dd9378953b8232ae76fad0a96e1563
    • affected 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4 – < c0691de7df1d51482a52cac93b7fe82fd9dd296b
    • affected 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4 – < 0307cf443308ecc6be9b2ca312bb31bae5e5a7ad
    • affected 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4 – < 4469c0c5b14a0919f5965c7ceac96b523eb57b79
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 5.10.214 – ≤ 5.10.*
    • unaffected 5.15.153 – ≤ 5.15.*
    • unaffected 6.1.83 – ≤ 6.1.*
    • unaffected 6.6.23 – ≤ 6.6.*
    • unaffected 6.7.11 – ≤ 6.7.*
    • unaffected 6.8.2 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-27047 badge
[![CVE-2024-27047](https://cveledger.app/badge/CVE-2024-27047.svg)](https://cveledger.app/cve/CVE-2024-27047)

Record last updated .