Answer in brief
CVE-2024-52319 records a Unknown severity vulnerability in mm: use aligned address in clear_gigantic_page(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=78fefd04c123493bbf28434768fa577b2153c79b <b79b6fe0737f233f0be1465052b7f0e75f324735 || >=78fefd04c123493bbf28434768fa577b2153c79b <8aca2bc96c833ba695ede7a45ad7784c836a262e | b79b6fe0737f233f0be1465052b7f0e75f324735, 8aca2bc96c833ba695ede7a45ad7784c836a262e |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Jan 11, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: mm: use aligned address in clear_gigantic_page() In current kernel, hugetlb_no_page() calls folio_zero_user() with the fault address. Where the fault address may be not aligned with the huge page size. Then, folio_zero_user() may call clear_gigantic_page() with the address, while clear_gigantic_page() requires the address to be huge page size aligned. So, this may cause memory corruption or information leak, addtional, use more obvious naming 'addr_hint' instead of 'addr' for clear_gigantic_page().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-52319 records a Unknown severity vulnerability in mm: use aligned address in clear_gigantic_page(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=78fefd04c123493bbf28434768fa577b2153c79b <b79b6fe0737f233f0be1465052b7f0e75f324735 || >=78fefd04c123493bbf28434768fa577b2153c79b <8aca2bc96c833ba695ede7a45ad7784c836a262e | b79b6fe0737f233f0be1465052b7f0e75f324735, 8aca2bc96c833ba695ede7a45ad7784c836a262e |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Jan 11, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: mm: use aligned address in clear_gigantic_page() In current kernel, hugetlb_no_page() calls folio_zero_user() with the fault address. Where the fault address may be not aligned with the huge page size. Then, folio_zero_user() may call clear_gigantic_page() with the address, while clear_gigantic_page() requires the address to be huge page size aligned. So, this may cause memory corruption or information leak, addtional, use more obvious naming 'addr_hint' instead of 'addr' for clear_gigantic_page().
Quoted source text, attributed separately from HOL analysis.