CVE-2026-31589

critical

Description

In the Linux kernel, the following vulnerability has been resolved: mm: call ->free_folio() directly in folio_unmap_invalidate() We can only call filemap_free_folio() if we have a reference to (or hold a lock on) the mapping. Otherwise, we've already removed the folio from the mapping so it no longer pins the mapping and the mapping can be removed, causing a use-after-free when accessing mapping->a_ops. Follow the same pattern as __remove_mapping() and load the free_folio function pointer before dropping the lock on the mapping. That lets us make filemap_free_folio() static as this was the only caller outside filemap.c.

References

https://git.kernel.org/stable/c/efc52947247a21bbf79059539bbbd40f4ea76f00

https://git.kernel.org/stable/c/c330e65ea59c4805d6ab6757c4ddfe8c63acef31

https://git.kernel.org/stable/c/b667df39d98a7a24be7c2a40ff0863dac1ad2cd7

https://git.kernel.org/stable/c/615d9bb2ccad42f9e21d837431e401db2e471195

Details

Source: Mitre, NVD

Published: 2026-04-24

Updated: 2026-05-07

Risk Information

CVSS v2

Base Score: 10

Vector: CVSS2#AV:N/AC:L/Au:N/C:C/I:C/A:C

Severity: Critical

CVSS v3

Base Score: 9.8

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Severity: Critical

EPSS

EPSS: 0.00018