Kernel crash via post-exit accounting write
Published Mar 12, 2025 · Updated Sep 8, 2026
NULL pointer dereference in Linux kernel process accounting allows local users to crash the system through a lookup-triggering acct(2) target. The final accounting write runs after the exiting task has called exit_fs(), so an internal lookup such as one for /sys/power/resume dereferences the absent current->fs pointer. Triggering the crash requires local access and CAP_SYS_PACCT; the reported consequence is a kernel service interruption, not data disclosure or modification.
Summary
What happened
NULL pointer dereference in Linux kernel process accounting allows local users to crash the system through a lookup-triggering acct(2) target. The final accounting write runs after the exiting task has called exit_fs(), so an internal lookup such as one for /sys/power/resume dereferences the absent current->fs pointer. Triggering the crash requires local access and CAP_SYS_PACCT; the reported consequence is a kernel service interruption, not data disclosure or modification.
The record
- CVE
- CVE-2025-21846
- Published
- Mar 12, 2025
- Updated
- Sep 8, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 2025CVE 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.
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