mm: avoid leaving partial pfn mappings around in error case
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 74ffa5a3e68504dd289135b1cf0422c19ffb3f2e · < 954fd4c81f22c4b6ba65379a81fd252971bf4ef3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mm: avoid leaving partial pfn mappings around in error case
As Jann points out, PFN mappings are special, because unlike normal memory mappings, there is no lifetime information associated with the mapping - it is just a raw mapping of PFNs with no reference counting of a 'struct page'.
That's all very much intentional, but it does mean that it's easy to mess up the cleanup in case of errors. Yes, a failed mmap() will always eventually clean up any partial mappings, but without any explicit lifetime in the page table mapping itself, it's very easy to do the error handling in the wrong order.
In particular, it's easy to mistakenly free the physical backing store before the page tables are actually cleaned up and (temporarily) have stale dangling PTE entries.
To make this situation less error-prone, just make sure that any partial pfn mapping is torn down early, before any other error handling.
From the CVE record · Linux
The Linux kernel can leave a partial PFN mapping in place during error handling for a failed mmap(). If the physical backing store is freed before the mapping is removed, stale page-table entries can temporarily remain. This requires a failed PFN-mapping operation; the input does not specify an authentication requirement or user interaction.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.