CVE-2025-21988: fs/netfs/read_collect: add to next->prev_donated
In the Linux kernel, the following vulnerability has been resolved:
fs/netfs/read_collect: add to next->prev_donated
If multiple subrequests donate data to the same "next" request
(depending on the subrequest completion order), each of them would
overwrite the `prev_donated` field, causing data corruption and a
BUG() crash ("Can't donate prior to front").
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw can corrupt data and force a kernel crash when several network-filesystem read operations donate data to the same follow-on request in an unlucky completion order. The supplied record rates it 9.8 critical, but the public description specifically demonstrates corruption and denial of service rather than every impact implied by that score.
Executive priority
Treat this as an urgent kernel maintenance issue for systems using the affected netfs path, particularly where crashes or data corruption would disrupt critical services. Validate actual exposure before assuming universal remote compromise, and deploy vendor-supported updates through normal emergency change controls.
Technical view
In fs/netfs/read_collect, multiple completed subrequests can overwrite the same next request’s prev_donated field instead of accumulating donations. This corrupts request bookkeeping and can trigger the kernel BUG message “Can't donate prior to front.” The referenced stable-kernel commits resolve the accounting error.
Likely exposure
Exposure requires an affected Linux kernel and execution of the relevant netfs read path with multiple subrequests completing in the problematic order. The supplied version data identifies Linux 6.12-related releases, but its flattened version entries do not establish precise vulnerable ranges or distribution backport status.
Exploitation context
The supplied record is not in CISA KEV, and no cited source establishes active exploitation or a public exploit. Although the CVSS vector marks network reachability without privileges or interaction, the source bundle does not explain how an external attacker could reliably trigger the required filesystem state.
Researcher notes
The stated failure depends on completion ordering, suggesting a concurrency-sensitive bookkeeping defect. No CWE is supplied. The description substantiates data corruption and a BUG-triggered crash; confidentiality loss and reliable remote code execution are not demonstrated by the provided evidence. Exact affected ranges require vendor or distribution confirmation.
Mitigation direction
Apply a vendor-supported kernel update containing the applicable referenced stable-kernel fix.
Check distribution advisories for backported fixes; package versions may differ from upstream versions.
Prioritize systems actively using Linux network-filesystem functionality.
Use vendor guidance for temporary mitigations if immediate kernel replacement is impractical.
Validation and detection
Inventory running kernel versions across Linux hosts and affected workload images.
Confirm remediation through vendor advisories or inclusion of the referenced upstream fix.
Identify systems exercising netfs-backed read paths and prioritize their testing.
Review kernel logs for BUG crashes containing “Can't donate prior to front.”
Regression-test network-filesystem reads after updating the kernel.
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.
cve · low confidence lookup
CVE-2025-21988 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
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.