Kernel crash via unchecked NULL cache entry
Published Jul 9, 2025 · Updated May 11, 2026
NULL pointer dereference in Linux bcache allows local users to crash the kernel when cache-set allocation fails during registration. The error path calls bch_cache_set_unregister before register_cache_set populates c->cache, and cache_set_flush dereferences the resulting NULL cache entry. Low-privileged local access and a bcache registration path encountering allocation failure are required; the bounded result is service interruption through a kernel crash.
Summary
What happened
NULL pointer dereference in Linux bcache allows local users to crash the kernel when cache-set allocation fails during registration. The error path calls bch_cache_set_unregister before register_cache_set populates c->cache, and cache_set_flush dereferences the resulting NULL cache entry. Low-privileged local access and a bcache registration path encountering allocation failure are required; the bounded result is service interruption through a kernel crash.
The record
- CVE
- CVE-2025-38263
- Published
- Jul 9, 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
- Jul 9, 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=3.10
- Affected versionversion=cafe563591446cf80bfbc2fe3bc72a2e36cf1060 <1e46ed947ec658f89f1a910d880cd05e42d3763e
- Affected versionversion=cafe563591446cf80bfbc2fe3bc72a2e36cf1060 <1f25f2d3fa29325320c19a30abf787e0bd5fc91b
- Affected versionversion=cafe563591446cf80bfbc2fe3bc72a2e36cf1060 <3f9e128186c99a117e304f1dce6d0b9e50c63cd8
- Affected versionversion=cafe563591446cf80bfbc2fe3bc72a2e36cf1060 <553f560e0a74a7008ad9dba05c3fd05da296befb
- Affected versionversion=cafe563591446cf80bfbc2fe3bc72a2e36cf1060 <667c3f52373ff5354cb3543e27237eb7df7b2333
- Affected versionversion=cafe563591446cf80bfbc2fe3bc72a2e36cf1060 <c4f5e7e417034b05f5d2f5fa9a872db897da69bd
- Affected versionversion=cafe563591446cf80bfbc2fe3bc72a2e36cf1060 <d54681938b777488e5dfb781b566d16adad991de
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