CVE-2025-21898

ftrace: Avoid potential division by zero in function_stat_show()

MEDIUM

5.5

CVSS Score

Published: April 1, 2025 at 03:26 PM UTC

Updated: June 17, 2026 at 08:44 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 3.16.83v ≥ 4.14.163v ≥ 4.19.94v ≥ 4.4.209v ≥ 4.9.2093.16.83 ≤ v < 3.174.14.163 ≤ v < 4.154.19.94 ≤ v < 4.204.4.206 ≤ v < 4.54.4.209 ≤ v < 4.54.9.209 ≤ v < 4.105.11 ≤ v < 5.15.1795.16 ≤ v < 6.1.1305.4.9 ≤ v < 5.4.2915.5 ≤ v < 5.10.2355.5 ≤ v < 5.15.1795.5 ≤ v < 6.1.1305.5 ≤ v < 6.12.185.5 ≤ v < 6.13.65.5 ≤ v < 6.145.5 ≤ v < 6.6.816.13 ≤ v < 6.13.66.2 ≤ v < 6.6.816.7 ≤ v < 6.12.1810a7e846d4beaf34384c40ff18d5de10106d9b415f0fd0fcc338513f80044add27fa46cf71d2171a2985af2a20b816a5cc41a2ddc1c4109ef6b9c63.16.83 4.14.163 4.19.94 4.4.209 4.9.209 5.4.9 6.14 rc1 6.14 rc2 6.14 rc3 6.14 rc47650b4b1df091815bbbbb837d308dd4154684f8ac59e74104cfd7df3ca0b5f59f1baee9c8c28b9efe31f7939c1c27faa5d0e3f14519eaf7c89e8a69df0629ee3922f10112584b1898491fecc74d98b3b

Vendor states this is fixed in 3d738b53ed6cddb68e68c9874520a4bf846163b5 (fixed)

Vendor states this is fixed in 5b3d32f607f0478b414b16516cf27f9170cf66c8 (fixed)

Vendor states this is fixed in 746cc474a95473591853927b3a9792a2d671155b (fixed)

Vendor states this is fixed in 992775227843c9376773784b8b362add44592ad7 (fixed)

Vendor states this is fixed in 9cdac46fa7e854e587eb5f393fe491b6d7a9bdf6 (fixed)

Vendor states this is fixed in a1a7eb89ca0b89dc1c326eeee2596f263291aca3 (fixed)

Vendor states this is fixed in ca381f60a3bb7cfaa618d73ca411610bd7fc3149 (fixed)

Vendor states this is fixed in f58a3f8e284d0bdf94164a8e61cd4e70d337a1a3 (fixed)

Affected range stops below 3.17, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 5.10.235 (unaffected)

Vendor states this is fixed in 5.15.179 (unaffected)

Vendor states this is fixed in 5.4.291 (unaffected)

Vendor states this is fixed in 5.5 (unaffected)

Vendor states this is fixed in 6.1.130 (unaffected)

Vendor states this is fixed in 6.12.18 (unaffected)

Vendor states this is fixed in 6.13.6 (unaffected)

Vendor states this is fixed in 6.14 (unaffected)

Vendor states this is fixed in 6.6.81 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references