CVE-2025-21898: ftrace: Avoid potential division by zero in function_stat_show()
In the Linux kernel, the following vulnerability has been resolved:
ftrace: Avoid potential division by zero in function_stat_show()
Check whether denominator expression x * (x - 1) * 1000 mod {2^32, 2^64}
produce zero and skip stddev computation in that case.
For now don't care about rec->counter * rec->counter overflow because
rec->time * rec->time overflow will likely happen earlier.
Security readout for executives and security teams
Plain-English summary
CVE-2025-21898 is a Linux kernel availability issue in ftrace reporting. A local authenticated user may trigger a divide-by-zero condition when function statistics are displayed. The public record rates it medium, with no confidentiality or integrity impact identified.
Executive priority
Treat this as a scheduled but real availability risk. It is not presented as remotely exploitable or actively exploited, but shared Linux infrastructure with local users should be patched promptly through normal kernel maintenance.
Technical view
The flaw is CWE-369 in function_stat_show(). The kernel fix checks whether x * (x - 1) * 1000 becomes zero after 32-bit or 64-bit modulo behavior, and skips standard deviation computation in that case.
Likely exposure
Exposure is most relevant on Linux systems running affected kernel builds where local users can reach ftrace function statistics. The CVE data names Linux kernels and stable commits, but does not identify specific appliance vendors or managed service products.
Exploitation context
The CVSS vector is local, low complexity, low privileges, no user interaction, availability impact high. The source bundle says CISA KEV is false and provides no cited evidence of active exploitation.
Researcher notes
Focus validation on kernel provenance, not application packages. The vulnerable logic is in ftrace statistics display and the fix changes arithmetic handling before standard deviation calculation. Evidence does not support claims of data theft, privilege escalation, or public exploitation.
Mitigation direction
Apply the relevant Linux stable kernel fix or vendor kernel update.
For Debian LTS systems, review the cited Debian LTS advisories.
Prioritize shared servers where untrusted local users have accounts.
Check vendor guidance for distribution-specific fixed package versions.
Plan reboot or live-patching procedures according to existing kernel maintenance policy.
Validation and detection
Inventory kernel versions across Linux hosts.
Compare kernel builds against CVE-2025-21898 vendor guidance and stable commit references.
Confirm patched systems include the relevant ftrace fix.
Identify systems with local shell access by non-administrators.
Track remediation separately for Debian LTS hosts.
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-369: 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-369 · source CWE mapping
Divide By Zero
Divide By Zero represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.