Kernel crash via uncleared fscache timer
Published Sep 18, 2024 · Updated Sep 8, 2026
Use-after-free in the Linux kernel fscache component allows local users to crash an affected system during module removal. The fscache_cookie_lru_timer remains queued on a CPU timer list when the fscache module exits, so a later softIRQ dereferences freed module state. Triggering requires privileged module removal after timer_reduce(), though filesystem unmount or shutdown can also reach the crash.
Summary
What happened
Use-after-free in the Linux kernel fscache component allows local users to crash an affected system during module removal. The fscache_cookie_lru_timer remains queued on a CPU timer list when the fscache module exits, so a later softIRQ dereferences freed module state. Triggering requires privileged module removal after timer_reduce(), though filesystem unmount or shutdown can also reach the crash.
The record
- CVE
- CVE-2024-46786
- Published
- Sep 18, 2024
- Updated
- Sep 8, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-416, T1529
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 18, 2024CVE publishedPublication date reported by the CVE source.
- Sep 8, 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=V3.1.6 <*
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