Answer in brief
CVE-2025-37996 records a Unknown severity vulnerability in KVM: arm64: Fix uninitialized memcache pointer in user_mem_abort(). 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 | >=fce886a6020734d6253c2c5a3bc285e385cc5496 <a26d50f8a4a5049e956984797b5d0dedea4bbb18 || >=fce886a6020734d6253c2c5a3bc285e385cc5496 <157dbc4a321f5bb6f8b6c724d12ba720a90f1a7c | a26d50f8a4a5049e956984797b5d0dedea4bbb18, 157dbc4a321f5bb6f8b6c724d12ba720a90f1a7c |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
May 29, 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: KVM: arm64: Fix uninitialized memcache pointer in user_mem_abort() Commit fce886a60207 ("KVM: arm64: Plumb the pKVM MMU in KVM") made the initialization of the local memcache variable in user_mem_abort() conditional, leaving a codepath where it is used uninitialized via kvm_pgtable_stage2_map(). This can fail on any path that requires a stage-2 allocation without transition via a permission fault or dirty logging. Fix this by making sure that memcache is always valid.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-37996 records a Unknown severity vulnerability in KVM: arm64: Fix uninitialized memcache pointer in user_mem_abort(). 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 | >=fce886a6020734d6253c2c5a3bc285e385cc5496 <a26d50f8a4a5049e956984797b5d0dedea4bbb18 || >=fce886a6020734d6253c2c5a3bc285e385cc5496 <157dbc4a321f5bb6f8b6c724d12ba720a90f1a7c | a26d50f8a4a5049e956984797b5d0dedea4bbb18, 157dbc4a321f5bb6f8b6c724d12ba720a90f1a7c |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
May 29, 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: KVM: arm64: Fix uninitialized memcache pointer in user_mem_abort() Commit fce886a60207 ("KVM: arm64: Plumb the pKVM MMU in KVM") made the initialization of the local memcache variable in user_mem_abort() conditional, leaving a codepath where it is used uninitialized via kvm_pgtable_stage2_map(). This can fail on any path that requires a stage-2 allocation without transition via a permission fault or dirty logging. Fix this by making sure that memcache is always valid.
Quoted source text, attributed separately from HOL analysis.