mm/hugetlb: do not dissolve gigantic pages without runtime support
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/hugetlb: do not dissolve gigantic pages without runtime support
dissolve_free_hugetlb_folio() doesn't check hstate_is_gigantic_no_runtime(h) though remove_hugetlb_folio()/ update_and_free_hugetlb_folio() silently bail for such folios, so it frees a still-listed folio and, on vmemmap restore failure, the add_hugetlb_folio() rollback corrupts the free list.
From the CVE record · Linux
The Linux kernel's hugetlb code can free a gigantic page that is still on a list when runtime support for dissolving it is unavailable. If restoring its vmemmap then fails, the rollback corrupts the free list. The input does not specify an attack path, authentication requirements, or user interaction.
Teams running the Linux kernel should check their deployments; affected versions were not provided.