Answer in brief
CVE-2026-43345 records a Unknown severity vulnerability in net: ipa: fix event ring index not programmed for IPA v5.0+. 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 | >=faf0678ec8a0aa9039d8b188d012206abd67dd5c <ae8343a19ccb051d519dbb3a9082ddea9f0551d3 || >=faf0678ec8a0aa9039d8b188d012206abd67dd5c <2bf18b643c4656413f7cfd5615af60a6b4e261da || >=faf0678ec8a0aa9039d8b188d012206abd67dd5c <2d2dc166d55148cfcf8ae67b415f8d6d110e6fca || >=faf0678ec8a0aa9039d8b188d012206abd67dd5c <34c988bb04cbdf093d2134e179433da49ffcd044 || >=faf0678ec8a0aa9039d8b188d012206abd67dd5c <56007972c0b1e783ca714d6f1f4d6e66e531d21f | ae8343a19ccb051d519dbb3a9082ddea9f0551d3, 2bf18b643c4656413f7cfd5615af60a6b4e261da, 2d2dc166d55148cfcf8ae67b415f8d6d110e6fca, 34c988bb04cbdf093d2134e179433da49ffcd044, 56007972c0b1e783ca714d6f1f4d6e66e531d21f |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
May 8, 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: net: ipa: fix event ring index not programmed for IPA v5.0+ For IPA v5.0+, the event ring index field moved from CH_C_CNTXT_0 to CH_C_CNTXT_1. The v5.0 register definition intended to define this field in the CH_C_CNTXT_1 fmask array but used the old identifier of ERINDEX instead of CH_ERINDEX. Without a valid event ring, GSI channels could never signal transfer completions. This caused gsi_channel_trans_quiesce() to block forever in wait_for_completion(). At least for IPA v5.2 this resolves an issue seen where runtime suspend, system suspend, and remoteproc stop all hanged forever. It also meant the IPA data path was completely non functional.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-43345 records a Unknown severity vulnerability in net: ipa: fix event ring index not programmed for IPA v5.0+. 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 | >=faf0678ec8a0aa9039d8b188d012206abd67dd5c <ae8343a19ccb051d519dbb3a9082ddea9f0551d3 || >=faf0678ec8a0aa9039d8b188d012206abd67dd5c <2bf18b643c4656413f7cfd5615af60a6b4e261da || >=faf0678ec8a0aa9039d8b188d012206abd67dd5c <2d2dc166d55148cfcf8ae67b415f8d6d110e6fca || >=faf0678ec8a0aa9039d8b188d012206abd67dd5c <34c988bb04cbdf093d2134e179433da49ffcd044 || >=faf0678ec8a0aa9039d8b188d012206abd67dd5c <56007972c0b1e783ca714d6f1f4d6e66e531d21f | ae8343a19ccb051d519dbb3a9082ddea9f0551d3, 2bf18b643c4656413f7cfd5615af60a6b4e261da, 2d2dc166d55148cfcf8ae67b415f8d6d110e6fca, 34c988bb04cbdf093d2134e179433da49ffcd044, 56007972c0b1e783ca714d6f1f4d6e66e531d21f |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
May 8, 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: net: ipa: fix event ring index not programmed for IPA v5.0+ For IPA v5.0+, the event ring index field moved from CH_C_CNTXT_0 to CH_C_CNTXT_1. The v5.0 register definition intended to define this field in the CH_C_CNTXT_1 fmask array but used the old identifier of ERINDEX instead of CH_ERINDEX. Without a valid event ring, GSI channels could never signal transfer completions. This caused gsi_channel_trans_quiesce() to block forever in wait_for_completion(). At least for IPA v5.2 this resolves an issue seen where runtime suspend, system suspend, and remoteproc stop all hanged forever. It also meant the IPA data path was completely non functional.
Quoted source text, attributed separately from HOL analysis.