CVE-2025-21736
MediumIn the Linux kernel, the following vulnerability has been resolved: nilfs2: fix possible int overflows in nilfs_fiemap() Since nilfs_bmap_lookup_contig() in nilfs_fiemap() calculates its result by being prepared to go through potentially maxblocks == INT_MAX blocks, the value in n may experience an overflow caused by left shift of blkbits. While it is extremely unlikely to occur, play it safe and cast right hand expression to wider type to mitigate the issue. Found by Linux Verification Center (linuxtesting.org) with static analysis tool SVACE.
CVSS 3.1 score
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness type
CWE-190CVE-2025-21736 is a Integer Overflow vulnerability
What is Integer Overflow?
The product performs a calculation that can produce an integer overflow, leading to unexpected values. Learn more on MITRE CWE
Affected versions
Linux kernel versions
2.6.38
and later are affected. Fixed in
5.4.291,
5.10.235,
5.15.179,
6.1.129,
6.6.78,
6.12.14,
6.13.3,
6.14
and their respective stable series.
References
10 total-
Patch
-
Patch
-
Patch
-
Patch
-
Patch
Frequently asked questions
-
What is CVE-2025-21736?
CVE-2025-21736 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as an Integer Overflow flaw (CWE-190) . It affects Linux kernel versions from 2.6.38 onward and has been patched in 5.4.291, 5.10.235, 5.15.179 and others. CVE-2025-21736 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2025-21736?
CVE-2025-21736 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. -
Is there a patch available for CVE-2025-21736?
Yes. CVE-2025-21736 has been patched. Fixed versions include 5.4.291, 5.10.235, 5.15.179 and others. If you are running Linux kernel 2.6.38 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-21736 actively exploited?
No. CVE-2025-21736 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.