fs/buffer: add alert in try_to_free_buffers() for folios without buffers
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b4fa966f03b7401ceacd4ffd7227197afb2b8376 · < b68f91ef3b3fe82ad78c417de71b675699a8467c| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's try_to_free_buffers() can dereference a null pointer when called on a folio without buffers attached. This can occur when filemap_release_folio() handles a folio whose mapping has AS_RELEASE_ALWAYS set but no release_folio operation. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with this fs/buffer behavior should check their deployments; affected versions are not specified.