mm/gup: fix memfd_pin_folios alloc race panic
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:
mm/gup: fix memfd_pin_folios alloc race panic
If memfd_pin_folios tries to create a hugetlb page, but someone else already did, then folio gets the value -EEXIST here:
folio = memfd_alloc_folio(memfd, start_idx); if (IS_ERR(folio)) { ret = PTR_ERR(folio); if (ret != -EEXIST) goto err;
then on the next trip through the "while start_idx" loop we panic here:
if (folio) { folio_put(folio);
To fix, set the folio to NULL on error.
From the CVE record · Linux
A race in the Linux kernel's memfd_pin_folios handling can cause a kernel panic when another operation has already created the hugetlb page it tries to create. The input does not specify whether an attacker needs network access, local access, authentication, or user interaction to trigger it.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.