dbcve.org
Linux KernelOperating system · Linux

CVE-2026-43345

HIGH · 7.5 CVSS v3.1 Published 2026-05-08
Fix available
A fix is available. Upgrade to 6.6.136 / 6.12.83 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.4, < 6.6.136>= 6.7, < 6.12.83>= 6.13, < 6.18.24>= 6.19, < 6.19.14= 7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.6.136 / 6.12.83 / 6.18.24 or later
Fixed in 6.6.1366.12.836.18.24
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 6.6.136, 6.12.83, 6.18.24, or 6.19.14 (or later stable) depending on your current branch

  1. Identify the currently running kernel version using 'uname -r'
  2. Determine which affected version range your kernel falls into (>=6.4,<6.6.136, >=6.7,<6.12.83, >=6.13,<6.18.24, or >=6.19,<6.19.14)
  3. Option 1 - Upgrade: Upgrade the Linux kernel to a version that includes the fix (6.6.136, 6.12.83, 6.18.24, or 6.19.14 or later, depending on your branch)
  4. Option 2 - Patch: Apply the stable kernel commit 2bf18b643c4656413f7cfd5615af60a6b4e261da to your kernel source tree and rebuild the kernel
  5. If applying the patch manually, locate the file 'drivers/net/ipa/ipa_reg.h' (or similar path in your kernel tree) containing the ERINDEX/CH_ERINDEX definitions
  6. After kernel update or patch application, rebuild the kernel and ensure IPA (Qualcomm IP Accelerator) driver modules are rebuilt
  7. Reboot into the new kernel and verify IPA functionality by checking system logs for any IPA-related errors
  8. Test IPA functionality (network data path, runtime suspend, system suspend, remoteproc operations) to confirm the fix resolves the hang issues
Caveat Kernel upgrade carries standard upgrade risks; ensure compatibility with userspace tools and verify dependent modules compile correctly

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-43345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-43345 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data