Skip to main content
VulnerabilityPublished Updated

CVE-2025-71295: Linux kernel · fs/buffer: add alert in try_to_free_buffers() for folios without buffers

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in c6246ca15999053d2632fbcc7b86e6eef7f077cb : update Linux kernel when convenient.

Data as of 5 Nov 2026, 23:24 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in c6246ca15999053d2632fbcc7b86e6eef7f077cb, c1b6227555c52781178132b7a06466711855795c, b68f91ef3b3fe82ad78c417de71b675699a8467c +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=6.1.72 <6.1.165
Fixed in
  • c6246ca15999053d2632fbcc7b86e6eef7f077cb
  • c1b6227555c52781178132b7a06466711855795c
  • b68f91ef3b3fe82ad78c417de71b675699a8467c
  • 727e5140e0cf83b4ce6a11b89bb73bff5d96f8f3
  • 42c32d7571ccd8ef32351cac506f00b0fae99fd2
  • 6.1.165
  • 1b111a69a6e33a922622bf9870e4e63fb2b649c8
LinuxLinuxAffected
  • =6.6
Fixed in–

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.

References

Community reviews

Loading reviews…