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

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.1% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-05-06 · updated 2026-10-14
Weakness: CWE-476

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.

Affected products

Linux kernel: from 6.1.72 before 6.1.165; from 6.2 before 6.6.128; from 6.7 before 6.12.75; from 6.13 before 6.18.16; from 6.19 before 6.19.6 — fixed in 6.1.165, 6.12.75, 6.18.16, 6.19.6, 6.6.128

How to fix

Upgrade to a fixed version: Linux kernel 6.1.165, 6.12.75, 6.18.16, 6.19.6. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-71295 or the next vulnerability affects your stack