Kernel panic via unchecked shrinker callback
Published Jul 25, 2026 · Updated Jul 25, 2026
NULL pointer dereference in the Linux Kernel shrinker debugfs interface allows local users to panic the kernel through file writes. shrinker_debugfs_add() unconditionally creates count and scan files when the corresponding shrinker callback is NULL, so a write calls a NULL function pointer. The path requires local high privileges and an affected shrinker, such as xen-backend; successful exploitation crashes the running kernel without affecting data confidentiality or integrity.
Summary
What happened
NULL pointer dereference in the Linux Kernel shrinker debugfs interface allows local users to panic the kernel through file writes. shrinker_debugfs_add() unconditionally creates count and scan files when the corresponding shrinker callback is NULL, so a write calls a NULL function pointer. The path requires local high privileges and an affected shrinker, such as xen-backend; successful exploitation crashes the running kernel without affecting data confidentiality or integrity.
The record
- CVE
- CVE-2026-64417
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 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=6.0
- Affected versionversion=bbf535fd6f06b94b9d07ed6f09397a936d4a58d8 <006467ab932698612398f853344a7405164541f4
- Affected versionversion=bbf535fd6f06b94b9d07ed6f09397a936d4a58d8 <09d2407985b8ce3e831f9d4310fe7ac06a6b3ae9
- Affected versionversion=bbf535fd6f06b94b9d07ed6f09397a936d4a58d8 <36f8534f461222291a74156ab91f3ba9f09b6f93
- Affected versionversion=bbf535fd6f06b94b9d07ed6f09397a936d4a58d8 <b9beed2322f3538b0d2d53307062da4102b8d8d8
- Affected versionversion=bbf535fd6f06b94b9d07ed6f09397a936d4a58d8 <e30453c61e185e914fde83c650e268067b140218
- Affected versionversion=bbf535fd6f06b94b9d07ed6f09397a936d4a58d8 <ebb45c2648b1f60715fd283700f651e05e431231
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