CVE-2026-64417
Last modified
CVE-2026-64417 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: mm: shrinker: fix NULL pointer dereference in debugfs shrinker_debugfs_add() creates both "count" and "scan" debugfs files unconditionally. That assumes every shrinker implements both count_objects() and scan_objects(), which is not guaranteed. For example, the xen-backend shrinker sets count_objects() but leaves scan_objects() NULL, so writing to its scan file calls through a NULL function pointer and panics the kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:0x0 Code: Unable to access opcode bytes at 0xffffffffffffffd6. Call Trace: <TASK> shrinker_debugfs_scan_write+0x12e/0x270 full_proxy_write+0x5f/0x90 vfs_write+0xde/0x420 ? filp_flush+0x75/0x90 ? filp_close+0x1d/0x30 ? do_dup2+0xb8/0x120 ksys_write+0x68/0xf0 ? filp_flush+0x75/0x90 do_syscall_64+0xb3/0x5b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e The count path has the same issue in principle if a shrinker omits count_objects(). To fix it, only create "count" and "scan" debugfs files when the corresponding callbacks are present.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: mm: shrinker: fix NULL pointer dereference in debugfs shrinker_debugfs_add() creates both "count" and "scan" debugfs files unconditionally. That assumes every shrinker implements both count_objects() and scan_objects(), which is not guaranteed. For example, the xen-backend shrinker sets count_objects() but leaves scan_objects() NULL, so writing to its scan file calls through a NULL function pointer and panics the kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:0x0 Code: Unable to access opcode bytes at 0xffffffffffffffd6. Call Trace: <TASK> shrinker_debugfs_scan_write+0x12e/0x270 full_proxy_write+0x5f/0x90 vfs_write+0xde/0x420 ? filp_flush+0x75/0x90 ? filp_close+0x1d/0x30 ? do_dup2+0xb8/0x120 ksys_write+0x68/0xf0 ? filp_flush+0x75/0x90 do_syscall_64+0xb3/0x5b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e The count path has the same issue in principle if a shrinker omits count_objects(). To fix it, only create "count" and "scan" debugfs files when the corresponding callbacks are present.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.0, < 6.1.178 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.145 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.96 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.39 | — |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 | — |
| Linux | Linux Kernel | 7.2 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64417?
How severe is CVE-2026-64417?
How do I fix CVE-2026-64417?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64411In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64412In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64413In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-64414In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64415In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64416In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64418In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64419In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-6442Improper validation of bash commands in Snowflake Cortex Cod…8.3
- CVE-2026-64420In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-64421In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64422In the Linux kernel, the following vulnerability has been re…7.1
Are you affected by CVE-2026-64417?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
