Local kernel crash via null PCI pointer
Published Jan 31, 2026 · Updated Jan 31, 2026
A null pointer dereference in the Linux Kernel 3c59x driver allows local users to crash the kernel during device probing. In vortex_probe1(), the free_ring error path passes &pdev->dev to dma_free_coherent even though pdev can be NULL, rather than using the available generic device pointer. The path requires local access capable of provoking probe cleanup on a system using the 3Com 3c59x driver; the documented consequence is loss of availability, not data access or modification.
Summary
What happened
A null pointer dereference in the Linux Kernel 3c59x driver allows local users to crash the kernel during device probing. In vortex_probe1(), the free_ring error path passes &pdev->dev to dma_free_coherent even though pdev can be NULL, rather than using the available generic device pointer. The path requires local access capable of provoking probe cleanup on a system using the 3Com 3c59x driver; the documented consequence is loss of availability, not data access or modification.
The record
- CVE
- CVE-2026-23020
- Published
- Jan 31, 2026
- Updated
- Jan 31, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 31, 2026CVE publishedPublication date reported by the CVE source.
- Jan 31, 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=4.17
- Affected versionversion=55c82617c3e82210b7471e9334e8fc5df6a9961f <053ac9e37eee435e999277c0f1ef890dad6064bf
- Affected versionversion=55c82617c3e82210b7471e9334e8fc5df6a9961f <28b2a805609699be7b90020ae7dccfb234be1ceb
- Affected versionversion=55c82617c3e82210b7471e9334e8fc5df6a9961f <2f05f7737e16d9a40038cc1c38a96a3f7964898b
- Affected versionversion=55c82617c3e82210b7471e9334e8fc5df6a9961f <606872c8e8bf96066730f6a2317502c5633c37f1
- Affected versionversion=55c82617c3e82210b7471e9334e8fc5df6a9961f <6cff14b831dbdb32675b4c7904dcc3eeeaf47e9d
- Affected versionversion=55c82617c3e82210b7471e9334e8fc5df6a9961f <a4e305ed60f7c41bbf9aabc16dd75267194e0de3
- Affected versionversion=55c82617c3e82210b7471e9334e8fc5df6a9961f <d82796a57cc0dac1dbef19d913c8f02a8cc7b1a7
- Affected versionversion=d30fdc02c49ad9965bba25015ae66c22dae967d1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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