Kernel crash via unchecked memory-mapping failure
Published May 1, 2025 · Updated May 11, 2026
NULL pointer dereference in the Linux pata_pxa ATA driver from 2.6.36 allows local users to crash the kernel during device probing. The pxa_ata_probe() path accepts a NULL return from devm_ioremap() and later dereferences it instead of aborting initialization. Reachability requires the PXA ATA driver to probe matching platform hardware while an I/O-memory mapping fails; the reported consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in the Linux pata_pxa ATA driver from 2.6.36 allows local users to crash the kernel during device probing. The pxa_ata_probe() path accepts a NULL return from devm_ioremap() and later dereferences it instead of aborting initialization. Reachability requires the PXA ATA driver to probe matching platform hardware while an I/O-memory mapping fails; the reported consequence is a kernel crash.
The record
- CVE
- CVE-2025-37758
- Published
- May 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2025CVE 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=2.6.36
- Affected versionversion=2dc6c6f15da97cb3e810963c80e981f19d42cd7d <17d5e6e915fad5a261db3698c9c5bbe702102d7c
- Affected versionversion=2dc6c6f15da97cb3e810963c80e981f19d42cd7d <2ba9e4c69207777bb0775c7c091800ecd69de144
- Affected versionversion=2dc6c6f15da97cb3e810963c80e981f19d42cd7d <2dc53c7a0c1f57b082931facafa804a7ca32a9a6
- Affected versionversion=2dc6c6f15da97cb3e810963c80e981f19d42cd7d <5b09bf6243b0bc0ae58bd9efdf6f0de5546f8d06
- Affected versionversion=2dc6c6f15da97cb3e810963c80e981f19d42cd7d <a551f75401793ba8075d7f46ffc931ce5151f03f
- Affected versionversion=2dc6c6f15da97cb3e810963c80e981f19d42cd7d <ad320e408a8c95a282ab9c05cdf0c9b95e317985
- Affected versionversion=2dc6c6f15da97cb3e810963c80e981f19d42cd7d <c022287f6e599422511aa227dc6da37b58d9ceac
- Affected versionversion=2dc6c6f15da97cb3e810963c80e981f19d42cd7d <d0d720f9282839b9db625a376c02a1426a16b0ae
- Affected versionversion=2dc6c6f15da97cb3e810963c80e981f19d42cd7d <ee2b0301d6bfe16b35d57947687c664ecb815775
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