CVE-2022-50285
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-04
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.3.6 (inc) to 4.4 (exc) |
| linux | linux_kernel | From 4.4.1 (inc) to 4.9.332 (exc) |
| linux | linux_kernel | From 4.10 (inc) to 4.14.298 (exc) |
| linux | linux_kernel | From 4.15 (inc) to 4.19.264 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.223 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.153 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.76 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.0.6 (exc) |
| linux | linux_kernel | 4.4 |
| linux | linux_kernel | 4.4 |
| linux | linux_kernel | 4.4 |
| linux | linux_kernel | 4.4 |
| linux | linux_kernel | 4.4 |
| linux | linux_kernel | 6.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves a race condition related to the handling of huge pages. Specifically, the counters for reserved huge pages (h->resv_huge_pages) are supposed to be protected by a lock called hugetlb_lock. However, there is a corner case in the function alloc_huge_page where the counter can be decremented without holding this lock. This can lead to corrupted values in the counter, potentially causing system instability or incorrect behavior related to huge page management.
How can this vulnerability impact me? :
The impact of this vulnerability is that the corrupted counter for reserved huge pages could lead to incorrect memory management in the Linux kernel. This might cause system instability, crashes, or unexpected behavior in applications relying on huge pages, potentially affecting system performance or reliability.
What immediate steps should I take to mitigate this vulnerability?
Apply the patch or update the Linux kernel to a version where the hugetlb_lock is properly taken before decrementing h->resv_huge_pages to avoid the race condition and potential corruption of the h->resv_huge_pages counter.