Description
In the Linux kernel, the following vulnerability has been resolved: filemap: Handle sibling entries in filemap_get_read_batch() If a read races with an invalidation followed by another read, it is possible for a folio to be replaced with a higher-order folio. If that happens, we'll see a sibling entry for the new folio in the next iteration of the loop. This manifests as a NULL pointer dereference while holding the RCU read lock. Handle this by simply returning. The next call will find the new folio and handle it correctly. The other ways of handling this rare race are more complex and it's just not worth it.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
cbd59c48ae2bcadc4a7599c29cf32fd3f9b78251 to < a66f131d30e53000f08301776bf85c912ef47aadaffectedcbd59c48ae2bcadc4a7599c29cf32fd3f9b78251 to < cb995f4eeba9d268fd4b56c2423ad6c1d1ea1b82affected
Linux Linux
Default version status: affected
5.12affected0 to < 5.12unaffected5.18.8 to ≤ 5.18.*unaffected5.19 to ≤ *unaffected