CVE-2025-21846: acct: perform last write from workqueue
In the Linux kernel, the following vulnerability has been resolved:
acct: perform last write from workqueue
In [1] it was reported that the acct(2) system call can be used to
trigger NULL deref in cases where it is set to write to a file that
triggers an internal lookup. This can e.g., happen when pointing acc(2)
to /sys/power/resume. At the point the where the write to this file
happens the calling task has already exited and called exit_fs(). A
lookup will thus trigger a NULL-deref when accessing current->fs.
Reorganize the code so that the the final write happens from the
workqueue but with the caller's credentials. This preserves the
(strange) permission model and has almost no regression risk.
This api should stop to exist though.
Security readout for executives and security teams
Plain-English summary
CVE-2025-21846 is a Linux kernel NULL pointer dereference reachable through acct(2). A local user with the needed privilege can cause a kernel crash by directing accounting output at certain internal files. The impact is availability, not data theft or code execution based on the supplied sources.
Executive priority
Treat this as a routine but real availability risk. Prioritize shared Linux hosts, multi-user systems, critical appliances, and environments where an unexpected kernel crash would affect business operations. It is not currently supported as an emergency remote-exploitation issue by the supplied evidence.
Technical view
The bug occurs when acct(2) writes a final accounting record after the calling task has exited and exit_fs() cleared current->fs. If the target file triggers an internal lookup, such as the reported /sys/power/resume case, the lookup can dereference NULL. Stable kernel fixes move the final write to a workqueue using the caller credentials.
Likely exposure
Linux systems running affected kernel lines are relevant, especially hosts where local users or services can invoke process accounting behavior. Exposure is local-only per CVSS AV:L and requires privileges per PR:L. Appliances embedding Linux should be checked through their vendor advisories.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. The public description includes a crash condition, but the known impact is denial of service through kernel NULL dereference, not remote compromise.
Researcher notes
The key condition is acct(2) final write after task exit combined with a destination that causes internal lookup using current->fs. The fix preserves the permission model by performing the final write from a workqueue with the caller credentials. Evidence is strong for crash impact, limited for exploitation in the wild.
Mitigation direction
Apply kernel updates containing the referenced stable fixes.
Use distribution security updates where available, including Debian LTS advisories if applicable.
Check appliance and embedded Linux vendor advisories for backported fixes.
Do not assume a workaround; follow vendor guidance if patching is delayed.
Reduce local account exposure on systems awaiting kernel updates.
Validation and detection
Inventory Linux kernel versions across servers, endpoints, containers hosts, and appliances.
Compare installed kernels with vendor fixed-package advisories or stable kernel fixes.
Confirm whether process accounting is enabled or exposed to local privileged users.
Review crash logs for NULL dereference symptoms around acct or accounting writes.
Verify updated kernels are booted, not merely installed.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.