Vulnerability · Published Mar 27, 2025 · Assigned by Linux
CVE-2023-52984net: phy: dp83822: Fix null pointer access on DP83825/DP83826 devices
Medium 5.5
In plain English
A medium-severity null pointer dereference in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 19% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: net: phy: dp83822: Fix null pointer access on DP83825/DP83826 devices The probe() function is only used for the DP83822 PHY, leaving the private data pointer uninitialized for the smaller DP83825/26 models. While all uses of the private data structure are hidden in 82822 specific callbacks, configuring the interrupt is shared across all models. This causes a NULL pointer dereference on the smaller PHYs as it accesses the private data unchecked. Verifying the pointer avoids that.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.11-1 | DEBIAN-CVE-2023-52984 |
| Debian:13 | linux | 6.1.11-1 | DEBIAN-CVE-2023-52984 |
| Debian:14 | linux | 6.1.11-1 | DEBIAN-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux | 5.15.0-72.79 | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1036.40 | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1038.45 | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1038.45.1 | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1034.42 | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1033.38 | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1020.25 | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1030.33 | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1030.35 | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1033.38 | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-72.79 | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1025.25 | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1035.41 | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1029.31 | UBUNTU-CVE-2023-52984 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-52984 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-52984 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 5dc39fd5ef35bc6919759fa99246581b1adc6b82 – before 362a2f5531dc0e5b0b5b3e3a541000dbffa754615dc39fd5ef35bc6919759fa99246581b1adc6b82 – before 2cd1e9c013ec56421c58921b1ddf1d2d53bd47fa5dc39fd5ef35bc6919759fa99246581b1adc6b82 – before 78901b10522cdf6badf24acf65a892637596bccc5dc39fd5ef35bc6919759fa99246581b1adc6b82 – before 422ae7d9c7221e8d4c8526d0f54106307d69d2dc |
| Linux | Linux | 5.10 |
Weakness: CWE-476 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H