Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-21736nilfs2: fix possible int overflows in nilfs_fiemap()

Description

In 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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 15 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-21736, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.25% · top 83% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 622daaff0a8975fb5c5b95f24f3234550ba32e92 – < 7649937987fed51ed09985da4019d50189fc534e
    • affected 622daaff0a8975fb5c5b95f24f3234550ba32e92 – < 58b1c6881081f5ddfb9a14dc241a74732c0f855c
    • affected 622daaff0a8975fb5c5b95f24f3234550ba32e92 – < 8f41df5fd4c11d26e929a85f7239799641f92da7
    • affected 622daaff0a8975fb5c5b95f24f3234550ba32e92 – < f3d80f34f58445355fa27b9579a449fb186aa64e
    • affected 622daaff0a8975fb5c5b95f24f3234550ba32e92 – < f2bd0f1ab47822fe5bd699c8458b896c4b2edea1
    • affected 622daaff0a8975fb5c5b95f24f3234550ba32e92 – < b9495a9109abc31d3170f7aad7d48aa64610a1a2
    • affected 622daaff0a8975fb5c5b95f24f3234550ba32e92 – < 250423300b4b0335918be187ef3cade248c06e6a
    • affected 622daaff0a8975fb5c5b95f24f3234550ba32e92 – < 6438ef381c183444f7f9d1de18f22661cba1e946
  • Linux · Linux

    • affected 2.6.38
    • unaffected < 2.6.38
    • unaffected 5.4.291 – ≤ 5.4.*
    • unaffected 5.10.235 – ≤ 5.10.*
    • unaffected 5.15.179 – ≤ 5.15.*
    • unaffected 6.1.129 – ≤ 6.1.*
    • unaffected 6.6.78 – ≤ 6.6.*
    • unaffected 6.12.14 – ≤ 6.12.*
    • unaffected 6.13.3 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-21736 badge
[![CVE-2025-21736](https://cveledger.app/badge/CVE-2025-21736.svg)](https://cveledger.app/cve/CVE-2025-21736)

Record last updated .