Skip to main content

Linux Kernel CVE-2026-80565

| EUVDEUVD-2026-66480 HIGH
2026-08-26 Linux GHSA-5465-f6h2-xr5j
7.8
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privilege local access on Qualcomm SoC device
  2. Delivery
    Trigger QCE driver registration failure condition
  3. Exploit
    Incorrect unregister call corrupts crypto subsystem state
  4. Execution
    Exploit memory corruption primitive
  5. Impact
    Escalate to kernel privileges

Vulnerability Assessment

Exploitation Conditions

Exploitation requires: (1) the target system must contain Qualcomm QCE crypto hardware and have the kernel built with CONFIG_CRYPTO_DEV_QCE enabled - systems without this hardware or configuration are entirely unaffected; (2) the attacker must trigger a failure in ops->register_algs() during the algorithm registration loop, which is a non-default, transient condition typically associated with driver probe failure or resource exhaustion; (3) local access with at least low-privilege credentials is required per the CVSS PR:L metric. Exploitation is limited by the hardware-specificity of the QCE driver and the need to reproduce a driver initialization failure path, which is not trivially controllable from userspace under normal conditions.

Impact

The NVD-assigned CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects worst-case exploitation of a memory-corruption primitive on a local system. However, several factors constrain real-world risk substantially. First, the flaw is hardware-gated: only systems with Qualcomm QCE hardware (Snapdragon SoC devices, certain ARM-based embedded platforms, or mobile devices running mainline Linux) load this driver. Standard x86 servers and most cloud instances are entirely unaffected. Second, the triggering condition requires a failed algorithm registration - a non-default, typically transient hardware or driver initialization failure. Third, exploitability depends on whether the incorrect unregister call causes actionable memory corruption or merely a resource leak, which is not independently confirmed from the available description. EPSS data was not provided. No POC code is publicly known. No KEV listing exists. The assessed real-world priority is LOW for most environments and MEDIUM only for organizations managing fleets of Qualcomm-based embedded Linux devices (Android, industrial IoT, networking appliances). The provided AC:L metric may overstate exploitability - reliably triggering a registration failure in a controlled way likely requires AC:H conditions in practice.

Exploit ScenarioDerived

An attacker with local low-privilege access on a Qualcomm SoC-based Linux system (such as an Android device running mainline Linux, an embedded networking appliance, or a Snapdragon-based development board) could attempt to trigger a QCE algorithm registration failure - for example, by inducing a resource exhaustion or hardware fault condition during driver initialization. If the incorrect unregister path causes a use-after-free or double-free in the crypto subsystem, the attacker could potentially leverage this memory corruption primitive to escalate to kernel execution privileges. No public proof-of-concept exploit exists, making this scenario theoretical at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 27, 2026

Incorrect error-path logic in the Linux kernel's Qualcomm Crypto Engine (QCE) driver allows a local attacker with low privileges on Qualcomm SoC-based hardware to potentially trigger memory corruption via a use-after-free or improper resource release condition. The flaw resides in devm_qce_register_algs, where a failed ops->register_algs() call causes the cleanup loop to repeatedly invoke ops->unregister_algs() on the failed slot rather than iterating over previously successfully registered algorithm slots - leaving registered algorithms unreleased and potentially double-freeing or corrupting state. No public exploit identified at time of analysis, and the flaw is not listed in the CISA Known Exploited Vulnerabilities catalog.

RemediationAI

The primary fix is to upgrade to the patched kernel version for your LTS branch: 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, or 6.14, per your deployment. Patch commits are available at git.kernel.org/stable/c/ for each stable branch (commit IDs: dbca8b798caf, fef187c6194d, 1ece8e16c085, de52c713d218, c7dc487aade1, a134e4b8102c, 4e88b4fda482, 9c75402286409f). For systems where a kernel upgrade is not immediately feasible, a targeted workaround is to prevent loading of the QCE driver module entirely via echo 'blacklist qce' >> /etc/modprobe.d/blacklist.conf and update-initramfs -u - trade-off is loss of hardware crypto acceleration, falling back to software implementations which may impact throughput on high-volume cryptographic workloads. Systems that do not use Qualcomm QCE hardware are unaffected regardless of kernel version.

Affected VersionsENISA

Linux 8c735ef894dfcca8d0a1cc554f83a82a70fd5b76
Linux 5.15.179 <5.15.217
Linux 6.6.78 <6.6.153
Linux patch: 6.6.153
Linux e914b2f795b6995bb0e7db45caa4a912dca09e65 <de52c713d21806b93b00a6074056b57aec4f8919
Linux patch: 5.10.266
Linux e80cf84b608725303113d6fe98bb727bf7b7a40d <a134e4b8102c077286818ee112b9f925db613d4c
Linux 4007883dc7df1dbaeb461b850e0b1b27c057affc
Linux 6.12.14 <6.12.105
Linux 6.13.3 <6.14
Linux 6.1.129 <6.1.184
Linux patch: 0
Linux 9e403fea74ecbe6b4a4321f13bd4bc929382908d <dbca8b798caf47fb2799a26dd09c9ad66305883d
Linux patch: 7.2
Linux 6.14
Linux e80cf84b608725303113d6fe98bb727bf7b7a40d <9c75402286409f5e1a75e4a445555c84066f89db
Linux 76e6d50fa5a2fb466edcc8b513d7aad372312c2a <c7dc487aade12c692add3221673c9bdf32dc24f5
Linux 5.10.235 <5.10.266
Linux patch: 6.12.105
Linux patch: 6.1.184
Linux 5.4.291 <5.5
Linux patch: 6.18.46
Linux patch: 7.1.10
Linux f52f00efd8c0088992ac07ef46af6096e4f0e52e <fef187c6194d67395182d58169dd14ba631f1b41
Linux patch: 5.15.217
Linux e80cf84b608725303113d6fe98bb727bf7b7a40d <4e88b4fda48282f3fd504b4d4f5d2d4f996b76ce
Linux 5d5b673b4dd260226b2202f66a920566c27051f3 <1ece8e16c085e8cd60ecbdb641269aaa53d31da4

Affected Packages

euvd linux fix: 5.5, 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.14

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Qualcomm Crypto Engine (QCE) driver (drivers/crypto/qce/) provides kernel-mode access to Qualcomm's hardware cryptographic accelerator found in Snapdragon and similar SoC families. The function devm_qce_register_algs iterates over a set of algorithm operation tables, calling ops->register_algs() for each. On registration failure, the prior implementation used the wrong loop variable to drive the unregister cleanup - calling ops->unregister_algs() on the failing entry repeatedly rather than walking back through the already-registered entries. This violates the pairing invariant of register/unregister, which in a devres-managed kernel driver can result in unreleased algorithm descriptors (resource leak), potential double-free of crypto transform objects, or dangling state in the kernel's crypto API subsystem. The CPE string cpe:2.3:a:linux:linux:* confirms the scope is the upstream Linux kernel across all stable branches. CWE data was not provided, but the root cause class maps to CWE-825 (Expired Pointer Dereference) or CWE-415 (Double Free) depending on exact memory management behavior at the time of the incorrect unregister call.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

AC elevated to H because triggering registration failure in QCE driver requires non-default hardware fault or resource exhaustion conditions, not a straightforward local action.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE 4.1 MEDIUM
AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
Red Hat 5.5 MEDIUM

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Aug 27, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 26, 2026 - 16:17 EUVD
CVE Published
Aug 26, 2026 - 14:37 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 26, 2026 - 14:37 cve.org
HIGH 7.8

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

crypto: qce - fix error path in devm_qce_register_algs

If ops->register_algs() fails, the error path repeatedly calls the same ops->unregister_algs() from the failed registration. Use the loop index to unregister the previously registered algorithms instead.

Executive ViewAI

Why It Matters

A memory corruption vulnerability in the Linux kernel's Qualcomm Crypto Engine driver could allow attackers with local access to gain elevated privileges on affected devices. Organizations relying on Qualcomm SoC-based hardware-including mobile devices, IoT systems, and edge computing platforms-face potential unauthorized system access and data compromise. A vendor patch is available and should be deployed urgently across affected device fleets.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Low
Qualcomm QCE driver specific to Qualcomm SoC hardware targets
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy