Local system crash via recursive shrinker locking
Published Jan 31, 2026 · Updated Jan 31, 2026
Deadlock in the Rust Binder driver in Linux Kernel 6.18 allows local users to crash the system through memory-reclaim activity. The rust_shrink_free_page function takes a spin lock that the per-cgroup list_lru path attempts to acquire again, causing recursive locking and deadlock in the shrinker callback. Exploitation requires local access and the Rust Binder path to be present; the bounded consequence is a kernel hang or crash rather than data disclosure or modification.
Summary
What happened
Deadlock in the Rust Binder driver in Linux Kernel 6.18 allows local users to crash the system through memory-reclaim activity. The rust_shrink_free_page function takes a spin lock that the per-cgroup list_lru path attempts to acquire again, causing recursive locking and deadlock in the shrinker callback. Exploitation requires local access and the Rust Binder path to be present; the bounded consequence is a kernel hang or crash rather than data disclosure or modification.
The record
- CVE
- CVE-2025-71181
- Published
- Jan 31, 2026
- Updated
- Jan 31, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-667, T1499
- 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=6.18
- Affected versionversion=eafedbc7c050c44744fbdf80bdf3315e860b7513 <30a98c97f7874031f2e1de19c777ce011143cba4
- Affected versionversion=eafedbc7c050c44744fbdf80bdf3315e860b7513 <361e0ff456a8daf9753c18030533256e4133ce7a
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.
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