s390/uv: Don't call folio_wait_writeback() without a folio reference
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/uv: Don't call folio_wait_writeback() without a folio reference
folio_wait_writeback() requires that no spinlocks are held and that a folio reference is held, as documented. After we dropped the PTL, the folio could get freed concurrently. So grab a temporary reference.
From the CVE record · Linux
The Linux kernel's s390/uv code called folio_wait_writeback() without holding a required folio reference. After the page table lock was dropped, the folio could be freed concurrently. The input does not specify attacker capabilities, authentication requirements, or user interaction.
Engineers running the Linux kernel should check whether their kernel includes the affected s390/uv code; affected versions are not specified.