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-71295fs/buffer: add alert in try_to_free_buffers() for folios without buffers

Description

In the Linux kernel, the following vulnerability has been resolved: fs/buffer: add alert in try_to_free_buffers() for folios without buffers try_to_free_buffers() can be called on folios with no buffers attached when filemap_release_folio() is invoked on a folio belonging to a mapping with AS_RELEASE_ALWAYS set but no release_folio operation defined. In such cases, folio_needs_release() returns true because of the AS_RELEASE_ALWAYS flag, but the folio has no private buffer data. This causes try_to_free_buffers() to call drop_buffers() on a folio with no buffers, leading to a null pointer dereference. Adding a check in try_to_free_buffers() to return early if the folio has no buffers attached, with WARN_ON_ONCE() to alert about the misconfiguration. This provides defensive hardening.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 6 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-71295, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.12% · top 98% of all CVEs (13 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 d0eafc763135508be118dac208887a26c0adb74d – < 1b111a69a6e33a922622bf9870e4e63fb2b649c8
    • affected b4fa966f03b7401ceacd4ffd7227197afb2b8376 – < c1b6227555c52781178132b7a06466711855795c
    • affected b4fa966f03b7401ceacd4ffd7227197afb2b8376 – < 727e5140e0cf83b4ce6a11b89bb73bff5d96f8f3
    • affected b4fa966f03b7401ceacd4ffd7227197afb2b8376 – < 42c32d7571ccd8ef32351cac506f00b0fae99fd2
    • affected b4fa966f03b7401ceacd4ffd7227197afb2b8376 – < c6246ca15999053d2632fbcc7b86e6eef7f077cb
    • affected b4fa966f03b7401ceacd4ffd7227197afb2b8376 – < b68f91ef3b3fe82ad78c417de71b675699a8467c
    • affected 6.1.72 – < 6.1.165
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .