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-21853bpf: avoid holding freeze_mutex during mmap operation

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: avoid holding freeze_mutex during mmap operation We use map->freeze_mutex to prevent races between map_freeze() and memory mapping BPF map contents with writable permissions. The way we naively do this means we'll hold freeze_mutex for entire duration of all the mm and VMA manipulations, which is completely unnecessary. This can potentially also lead to deadlocks, as reported by syzbot in [0]. So, instead, hold freeze_mutex only during writeability checks, bump (proactively) "write active" count for the map, unlock the mutex and proceed with mmap logic. And only if something went wrong during mmap logic, then undo that "write active" counter increment. [0] https://lore.kernel.org/bpf/[email protected]/

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 20 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-21853, 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 84% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 fc9702273e2edb90400a34b3be76f7b08fa3344b – < 2ce31c97c219b4fe797749f950274f246eb88c49
    • affected fc9702273e2edb90400a34b3be76f7b08fa3344b – < 0d90d9e154144a3a80e9fc0eb9b21b7fc990f68f
    • affected fc9702273e2edb90400a34b3be76f7b08fa3344b – < 4759acbd44d24a69b7b14848012ec4201d6c5501
    • affected fc9702273e2edb90400a34b3be76f7b08fa3344b – < 29cfda62ab4d92ab94123813db49ab76c1e61b29
    • affected fc9702273e2edb90400a34b3be76f7b08fa3344b – < d95607a5f2f9bb08194c9deaf4a5f3e8ba59a9d4
    • affected fc9702273e2edb90400a34b3be76f7b08fa3344b – < 271e49f8a58edba65bc2b1250a0abaa98c4bfdbe
    • affected fc9702273e2edb90400a34b3be76f7b08fa3344b – < bc27c52eea189e8f7492d40739b7746d67b65beb
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 5.10.237 – ≤ 5.10.*
    • unaffected 5.15.181 – ≤ 5.15.*
    • unaffected 6.1.135 – ≤ 6.1.*
    • unaffected 6.6.80 – ≤ 6.6.*
    • unaffected 6.12.17 – ≤ 6.12.*
    • unaffected 6.13.5 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .