Local kernel panic via uninitialized AT8031 private data
Published May 1, 2024 · Updated May 11, 2026
NULL pointer dereference in the Linux kernel 6.8 allows local users to trigger a kernel panic through the AT8031 PHY probe path. The at8031_probe path writes is_1000basex and is_fiber through priv before at803x_probe allocates that structure in phydev. Reachability requires local low-privileged access and an AT8031 PHY, and successful triggering interrupts the affected system by panicking its kernel.
Summary
What happened
NULL pointer dereference in the Linux kernel 6.8 allows local users to trigger a kernel panic through the AT8031 PHY probe path. The at8031_probe path writes is_1000basex and is_fiber through priv before at803x_probe allocates that structure in phydev. Reachability requires local low-privileged access and an AT8031 PHY, and successful triggering interrupts the affected system by panicking its kernel.
The record
- CVE
- CVE-2024-26942
- Published
- May 1, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362, CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=25d2ba94005fac18fe68878cddff59a67e115554 <6a4aee277740d04ac0fd54cfa17cc28261932ddc
- Affected versionversion=25d2ba94005fac18fe68878cddff59a67e115554 <a8a296ad9957b845b89bcf48be1cf8c74875ecc3
- Affected versionversion=6.8
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo