Answer in brief
CVE-2022-49286 records a Unknown severity vulnerability in tpm: use try_get_ops() in tpm-space.c. 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 | >=4d57856a21ed2abe33412e0526cc84bdcf67ea08 <5b1d2561a03e534064b51c50c774657833d3d2cf || >=4d57856a21ed2abe33412e0526cc84bdcf67ea08 <95193d12f10a8a088843b25e0f5fe1d83ec6b079 || >=4d57856a21ed2abe33412e0526cc84bdcf67ea08 <476ddd23f818fb94cf86fb5617f3bb9a7c92113d || >=4d57856a21ed2abe33412e0526cc84bdcf67ea08 <eda1662cce964c8a65bb86321f8d9cfa6e9ceaab || >=4d57856a21ed2abe33412e0526cc84bdcf67ea08 <ba84f9a48366dcc3cdef978599433efe101dd5bd || >=4d57856a21ed2abe33412e0526cc84bdcf67ea08 <fb5abce6b2bb5cb3d628aaa63fa821da8c4600f9 | 5b1d2561a03e534064b51c50c774657833d3d2cf, 95193d12f10a8a088843b25e0f5fe1d83ec6b079, 476ddd23f818fb94cf86fb5617f3bb9a7c92113d, eda1662cce964c8a65bb86321f8d9cfa6e9ceaab, ba84f9a48366dcc3cdef978599433efe101dd5bd, fb5abce6b2bb5cb3d628aaa63fa821da8c4600f9 |
| Linux/Linuxgeneric | 4.12 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 13, 2026
In the Linux kernel, the following vulnerability has been resolved: tpm: use try_get_ops() in tpm-space.c As part of the series conversion to remove nested TPM operations: https://lore.kernel.org/all/[email protected]/ exposure of the chip->tpm_mutex was removed from much of the upper level code. In this conversion, tpm2_del_space() was missed. This didn't matter much because it's usually called closely after a converted operation, so there's only a very tiny race window where the chip can be removed before the space flushing is done which causes a NULL deref on the mutex. However, there are reports of this window being hit in practice, so fix this by converting tpm2_del_space() to use tpm_try_get_ops(), which performs all the teardown checks before acquring the mutex.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-49286 records a Unknown severity vulnerability in tpm: use try_get_ops() in tpm-space.c. 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 | >=4d57856a21ed2abe33412e0526cc84bdcf67ea08 <5b1d2561a03e534064b51c50c774657833d3d2cf || >=4d57856a21ed2abe33412e0526cc84bdcf67ea08 <95193d12f10a8a088843b25e0f5fe1d83ec6b079 || >=4d57856a21ed2abe33412e0526cc84bdcf67ea08 <476ddd23f818fb94cf86fb5617f3bb9a7c92113d || >=4d57856a21ed2abe33412e0526cc84bdcf67ea08 <eda1662cce964c8a65bb86321f8d9cfa6e9ceaab || >=4d57856a21ed2abe33412e0526cc84bdcf67ea08 <ba84f9a48366dcc3cdef978599433efe101dd5bd || >=4d57856a21ed2abe33412e0526cc84bdcf67ea08 <fb5abce6b2bb5cb3d628aaa63fa821da8c4600f9 | 5b1d2561a03e534064b51c50c774657833d3d2cf, 95193d12f10a8a088843b25e0f5fe1d83ec6b079, 476ddd23f818fb94cf86fb5617f3bb9a7c92113d, eda1662cce964c8a65bb86321f8d9cfa6e9ceaab, ba84f9a48366dcc3cdef978599433efe101dd5bd, fb5abce6b2bb5cb3d628aaa63fa821da8c4600f9 |
| Linux/Linuxgeneric | 4.12 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 13, 2026
In the Linux kernel, the following vulnerability has been resolved: tpm: use try_get_ops() in tpm-space.c As part of the series conversion to remove nested TPM operations: https://lore.kernel.org/all/[email protected]/ exposure of the chip->tpm_mutex was removed from much of the upper level code. In this conversion, tpm2_del_space() was missed. This didn't matter much because it's usually called closely after a converted operation, so there's only a very tiny race window where the chip can be removed before the space flushing is done which causes a NULL deref on the mutex. However, there are reports of this window being hit in practice, so fix this by converting tpm2_del_space() to use tpm_try_get_ops(), which performs all the teardown checks before acquring the mutex.
Quoted source text, attributed separately from HOL analysis.