mm: filemap: retain mapped dropbehind folios
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.547.2.87.3In the Linux kernel, the following vulnerability has been resolved:
mm: filemap: retain mapped dropbehind folios
Fault-around can map ready dropbehind folios without going through the normal page-cache lookup that clears dropbehind. A mapping represents a competing cached user, so retain the folio instead of forcibly unmapping it when writeback completes.
For a mapped folio, folio_unmap_invalidate() can call unmap_mapping_folio(), which takes i_mmap_rwsem and may sleep. Retaining mapped folios avoids this path when folio_end_dropbehind() runs in non-preemptible task context.
Tal was able to trigger a sleeping-in-atomic warning due to this [1].
Unmapped dropbehind folios continue through the existing invalidation path.
From the CVE record · Linux
Linux kernel filemap handling can invalidate mapped dropbehind folios when writeback completes, reaching an operation that may sleep in non-preemptible task context. This can trigger a sleeping-in-atomic warning; the input does not specify how an attacker could trigger it or whether authentication or user interaction is required.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.