Skip to main content

Linux Kernel EUVDEUVD-2026-59639

| CVE-2026-74574 HIGH
2026-08-15 Linux GHSA-6vf2-r72r-2pc8
7.8
CVSS 3.1 · Vendor: Linux
Share

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.8 HIGH

Local access with low privileges required to open the character device; no scope change; full kernel-level C/I/A impact if use-after-free is weaponized.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
6.4 MEDIUM
AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
Red Hat
7.0 HIGH
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 12:34 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 15, 2026 - 13:04 EUVD
CVE Published
Aug 15, 2026 - 12:28 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 15, 2026 - 12:28 cve.org
HIGH 7.8

DescriptionCVE.org

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

dmaengine: idxd: fix fdev setup failure cleanup in idxd_cdev_open()

The failed_dev_add and failed_dev_name paths drop the file-device reference while wq->wq_lock is still held. If put_device(fdev) drops the last reference, idxd_file_dev_release() runs synchronously and tries to take wq->wq_lock again, deadlocking.

Those paths also fall through into the later ctx cleanup labels even though idxd_file_dev_release() owns that cleanup and frees ctx. This can make idxd_xa_pasid_remove(ctx) and kfree(ctx) operate on a freed context.

Move idxd_wq_get() before file-device setup can fail, since the release callback always calls idxd_wq_put(). Then unlock wq->wq_lock before put_device(fdev) and return directly from the file-device setup failure path, leaving ctx cleanup to the release callback.

AnalysisAI

Deadlock and use-after-free conditions in the Linux kernel's IDXD character device driver expose local low-privileged users on Intel DSA-equipped systems to potential kernel memory corruption or denial of service. The vulnerability resides in idxd_cdev_open(), where error cleanup paths call put_device(fdev) while still holding wq->wq_lock, causing idxd_file_dev_release() to deadlock on synchronous reentry; a secondary fallthrough defect then allows idxd_xa_pasid_remove(ctx) and kfree(ctx) to operate on memory already freed by that release callback. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Recon
Identify system with Intel DSA hardware and idxd driver loaded
Delivery
Open IDXD character device node as low-priv user
Exploit
Trigger file-device setup failure in idxd_cdev_open()
Install
put_device(fdev) called while wq_lock held
C2
idxd_file_dev_release() deadlocks attempting wq_lock reacquisition
Execute
Fallthrough executes kfree on already-freed ctx
Impact
Kernel heap corruption enabling privilege escalation

Vulnerability AssessmentAI

Exploitation Three concrete prerequisites must all be satisfied: (1) Intel Data Streaming Accelerator (DSA) hardware must be physically present in the system and the `idxd` kernel module must be loaded - this limits exposure to select data-center-grade Intel Xeon platforms and is a non-default configuration for most deployments; (2) the attacker must have local system access with at minimum low-privilege permissions sufficient to open the IDXD character device node (consistent with CVSS PR:L, AV:L); (3) a file-device setup failure must occur during the open operation - specifically the `failed_dev_add` or `failed_dev_name` error branches in `idxd_cdev_open()` must be reached. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The NVD-supplied CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately reflects that exploitation requires local, low-privileged access rather than remote unauthenticated attack - a meaningful constraint that tempers the headline score. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario A local user with low-privilege access on an Intel DSA-equipped server opens the IDXD character device node, triggering the `failed_dev_add` or `failed_dev_name` error path in `idxd_cdev_open()` while `wq->wq_lock` is held. The resulting deadlock on `idxd_file_dev_release()` re-acquiring the lock halts the kernel thread, and the fallthrough cleanup then operates on the already-freed `ctx` structure, potentially enabling kernel heap corruption that could be leveraged for privilege escalation. …
Remediation Upgrade the Linux kernel to a patched stable release: 6.6.151, 6.12.103, 6.18.44, or 7.1.8 (or 7.2-rc6 for development tracking). … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours, identify all systems equipped with Intel DSA hardware and verify their Linux kernel versions against the vendor advisory; this is critical as only DSA-equipped systems are affected. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

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

Share

EUVD-2026-59639 vulnerability details – vuln.today

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