Answer in brief
CVE-2022-49554 records a High severity (CVSS 7.8) vulnerability in zsmalloc: fix races between asynchronous zspage free and page migration. 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.
Answer in brief
CVE-2022-49554 records a High severity (CVSS 7.8) vulnerability in zsmalloc: fix races between asynchronous zspage free and page migration. 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.
CVSS is 7.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=77ff465799c60294e248000cd22ae8171da3304c <3674d8a8dadd03a447dd21069d4dacfc3399b63b || >=77ff465799c60294e248000cd22ae8171da3304c <645996efc2ae391246d595832aaa6f9d3cc338c7 || >=77ff465799c60294e248000cd22ae8171da3304c <fc658c083904427abbf8f18280d517ee2668677c || >=77ff465799c60294e248000cd22ae8171da3304c <fae05b2314b147a78fbed1dc4c645d9a66313758 || >=77ff465799c60294e248000cd22ae8171da3304c <3ec459c8810e658401be428d3168eacfc380bdd0 || >=77ff465799c60294e248000cd22ae8171da3304c <8ba7b7c1dad1f6503c541778f31b33f7f62eb966 || >=77ff465799c60294e248000cd22ae8171da3304c <c5402fb5f71f1a725f1e55d9c6799c0c7bec308f || >=77ff465799c60294e248000cd22ae8171da3304c <2505a981114dcb715f8977b8433f7540854851d8 | 3674d8a8dadd03a447dd21069d4dacfc3399b63b, 645996efc2ae391246d595832aaa6f9d3cc338c7, fc658c083904427abbf8f18280d517ee2668677c, fae05b2314b147a78fbed1dc4c645d9a66313758, 3ec459c8810e658401be428d3168eacfc380bdd0, 8ba7b7c1dad1f6503c541778f31b33f7f62eb966, c5402fb5f71f1a725f1e55d9c6799c0c7bec308f, 2505a981114dcb715f8977b8433f7540854851d8 |
| Linux/Linuxgeneric | 4.14 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: zsmalloc: fix races between asynchronous zspage free and page migration The asynchronous zspage free worker tries to lock a zspage's entire page list without defending against page migration. Since pages which haven't yet been locked can concurrently migrate off the zspage page list while lock_zspage() churns away, lock_zspage() can suffer from a few different lethal races. It can lock a page which no longer belongs to the zspage and unsafely dereference page_private(), it can unsafely dereference a torn pointer to the next page (since there's a data race), and it can observe a spurious NULL pointer to the next page and thus not lock all of the zspage's pages (since a single page migration will reconstruct the entire page list, and create_page_chain() unconditionally zeroes out each list pointer in the process). Fix the races by using migrate_read_lock() in lock_zspage() to synchronize with page migration.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=77ff465799c60294e248000cd22ae8171da3304c <3674d8a8dadd03a447dd21069d4dacfc3399b63b || >=77ff465799c60294e248000cd22ae8171da3304c <645996efc2ae391246d595832aaa6f9d3cc338c7 || >=77ff465799c60294e248000cd22ae8171da3304c <fc658c083904427abbf8f18280d517ee2668677c || >=77ff465799c60294e248000cd22ae8171da3304c <fae05b2314b147a78fbed1dc4c645d9a66313758 || >=77ff465799c60294e248000cd22ae8171da3304c <3ec459c8810e658401be428d3168eacfc380bdd0 || >=77ff465799c60294e248000cd22ae8171da3304c <8ba7b7c1dad1f6503c541778f31b33f7f62eb966 || >=77ff465799c60294e248000cd22ae8171da3304c <c5402fb5f71f1a725f1e55d9c6799c0c7bec308f || >=77ff465799c60294e248000cd22ae8171da3304c <2505a981114dcb715f8977b8433f7540854851d8 | 3674d8a8dadd03a447dd21069d4dacfc3399b63b, 645996efc2ae391246d595832aaa6f9d3cc338c7, fc658c083904427abbf8f18280d517ee2668677c, fae05b2314b147a78fbed1dc4c645d9a66313758, 3ec459c8810e658401be428d3168eacfc380bdd0, 8ba7b7c1dad1f6503c541778f31b33f7f62eb966, c5402fb5f71f1a725f1e55d9c6799c0c7bec308f, 2505a981114dcb715f8977b8433f7540854851d8 |
| Linux/Linuxgeneric | 4.14 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: zsmalloc: fix races between asynchronous zspage free and page migration The asynchronous zspage free worker tries to lock a zspage's entire page list without defending against page migration. Since pages which haven't yet been locked can concurrently migrate off the zspage page list while lock_zspage() churns away, lock_zspage() can suffer from a few different lethal races. It can lock a page which no longer belongs to the zspage and unsafely dereference page_private(), it can unsafely dereference a torn pointer to the next page (since there's a data race), and it can observe a spurious NULL pointer to the next page and thus not lock all of the zspage's pages (since a single page migration will reconstruct the entire page list, and create_page_chain() unconditionally zeroes out each list pointer in the process). Fix the races by using migrate_read_lock() in lock_zspage() to synchronize with page migration.
Quoted source text, attributed separately from HOL analysis.