Answer in brief
CVE-2024-47676 records a Unknown severity vulnerability in mm/hugetlb.c: fix UAF of vma in hugetlb fault pathway. 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 | >=9acad7ba3e25d11f4c96df1b7312ae89e6faca5c <e897d184a8dd4a4e1f39c8c495598e4d9472776c || >=9acad7ba3e25d11f4c96df1b7312ae89e6faca5c <d59ebc99dee0a2687a26df94b901eb8216dbf876 || >=9acad7ba3e25d11f4c96df1b7312ae89e6faca5c <98b74bb4d7e96b4da5ef3126511febe55b76b807 | e897d184a8dd4a4e1f39c8c495598e4d9472776c, d59ebc99dee0a2687a26df94b901eb8216dbf876, 98b74bb4d7e96b4da5ef3126511febe55b76b807 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Oct 21, 2024
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/hugetlb.c: fix UAF of vma in hugetlb fault pathway Syzbot reports a UAF in hugetlb_fault(). This happens because vmf_anon_prepare() could drop the per-VMA lock and allow the current VMA to be freed before hugetlb_vma_unlock_read() is called. We can fix this by using a modified version of vmf_anon_prepare() that doesn't release the VMA lock on failure, and then release it ourselves after hugetlb_vma_unlock_read().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-47676 records a Unknown severity vulnerability in mm/hugetlb.c: fix UAF of vma in hugetlb fault pathway. 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 | >=9acad7ba3e25d11f4c96df1b7312ae89e6faca5c <e897d184a8dd4a4e1f39c8c495598e4d9472776c || >=9acad7ba3e25d11f4c96df1b7312ae89e6faca5c <d59ebc99dee0a2687a26df94b901eb8216dbf876 || >=9acad7ba3e25d11f4c96df1b7312ae89e6faca5c <98b74bb4d7e96b4da5ef3126511febe55b76b807 | e897d184a8dd4a4e1f39c8c495598e4d9472776c, d59ebc99dee0a2687a26df94b901eb8216dbf876, 98b74bb4d7e96b4da5ef3126511febe55b76b807 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Oct 21, 2024
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/hugetlb.c: fix UAF of vma in hugetlb fault pathway Syzbot reports a UAF in hugetlb_fault(). This happens because vmf_anon_prepare() could drop the per-VMA lock and allow the current VMA to be freed before hugetlb_vma_unlock_read() is called. We can fix this by using a modified version of vmf_anon_prepare() that doesn't release the VMA lock on failure, and then release it ourselves after hugetlb_vma_unlock_read().
Quoted source text, attributed separately from HOL analysis.