Answer in brief
CVE-2026-64222 records a Unknown severity vulnerability in octeontx2-pf: avoid double free of pool->stack on AQ init failure. 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-2026-64222 records a Unknown severity vulnerability in octeontx2-pf: avoid double free of pool->stack on AQ init failure. 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 | >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <e6e9bc0bf963662b7042048ab0281014625d4cb4 || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <b92e7ea408b6f1144648909c9c49a55d245d7300 || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <94192b0579333c3deee2441379aab8ca98fc2e6b || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <4c29603498b05c049dbbbc47e882f2fbf0193cd7 || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <0488a0bb344fb1992853b60082acff6be8164d74 || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <0d9b9d7dbef976ae7f855b6358f1d703014e96ea || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <c4b8c5d51632538b19ee01cf6d70cbceeefbd3ec || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <9b244c242bec48b37e82b89787afd6a4c43457e1 | e6e9bc0bf963662b7042048ab0281014625d4cb4, b92e7ea408b6f1144648909c9c49a55d245d7300, 94192b0579333c3deee2441379aab8ca98fc2e6b, 4c29603498b05c049dbbbc47e882f2fbf0193cd7, 0488a0bb344fb1992853b60082acff6be8164d74, 0d9b9d7dbef976ae7f855b6358f1d703014e96ea, c4b8c5d51632538b19ee01cf6d70cbceeefbd3ec, 9b244c242bec48b37e82b89787afd6a4c43457e1 |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
Jul 24, 2026
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: octeontx2-pf: avoid double free of pool->stack on AQ init failure otx2_pool_aq_init() frees pool->stack when mailbox sync or retry allocation fails, but leaves the pointer unchanged. Later, otx2_sq_aura_pool_init() unwinds the partial setup through otx2_aura_pool_free(), which frees pool->stack again. The CN20K-specific cn20k_pool_aq_init() implementation has the same bug in its corresponding error path. Set pool->stack to NULL immediately after the local free so the shared cleanup path does not free the same stack again while cleaning up partially initialized pool state. The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing v6.13-rc1. The tool is still under development and is not yet publicly available. Manual inspection confirms that the bug is still present in v7.1-rc3. Runtime validation was not performed because reproducing this path requires OcteonTX2/CN20K hardware.
Quoted source text, attributed separately from HOL analysis.
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 | >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <e6e9bc0bf963662b7042048ab0281014625d4cb4 || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <b92e7ea408b6f1144648909c9c49a55d245d7300 || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <94192b0579333c3deee2441379aab8ca98fc2e6b || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <4c29603498b05c049dbbbc47e882f2fbf0193cd7 || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <0488a0bb344fb1992853b60082acff6be8164d74 || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <0d9b9d7dbef976ae7f855b6358f1d703014e96ea || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <c4b8c5d51632538b19ee01cf6d70cbceeefbd3ec || >=caa2da34fd25a37e9fd43343b6966fb9d730a6d5 <9b244c242bec48b37e82b89787afd6a4c43457e1 | e6e9bc0bf963662b7042048ab0281014625d4cb4, b92e7ea408b6f1144648909c9c49a55d245d7300, 94192b0579333c3deee2441379aab8ca98fc2e6b, 4c29603498b05c049dbbbc47e882f2fbf0193cd7, 0488a0bb344fb1992853b60082acff6be8164d74, 0d9b9d7dbef976ae7f855b6358f1d703014e96ea, c4b8c5d51632538b19ee01cf6d70cbceeefbd3ec, 9b244c242bec48b37e82b89787afd6a4c43457e1 |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
Jul 24, 2026
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: octeontx2-pf: avoid double free of pool->stack on AQ init failure otx2_pool_aq_init() frees pool->stack when mailbox sync or retry allocation fails, but leaves the pointer unchanged. Later, otx2_sq_aura_pool_init() unwinds the partial setup through otx2_aura_pool_free(), which frees pool->stack again. The CN20K-specific cn20k_pool_aq_init() implementation has the same bug in its corresponding error path. Set pool->stack to NULL immediately after the local free so the shared cleanup path does not free the same stack again while cleaning up partially initialized pool state. The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing v6.13-rc1. The tool is still under development and is not yet publicly available. Manual inspection confirms that the bug is still present in v7.1-rc3. Runtime validation was not performed because reproducing this path requires OcteonTX2/CN20K hardware.
Quoted source text, attributed separately from HOL analysis.