Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-74574: dmaengine: idxd: fix fdev setup failure cleanup in idxd_cdev_open()

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0679c0c189d2548f00e1bac95be28e2df5c6c7f7, 6e26a41c4c1a706edaaa7c7dffc6b3b945707a55, 778ccbded2c8749c5be7f0dfa04fc9977a36fb7e.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0679c0c189d2548f00e1bac95be28e2df5c6c7f7, 6e26a41c4c1a706edaaa7c7dffc6b3b945707a55, 778ccbded2c8749c5be7f0dfa04fc9977a36fb7e or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Aug 15, 2026
Updated
Oct 16, 2026
EPSS
0.1% · 2th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-74574

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.4affected
    • e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec and later · before 778ccbded2c8749c5be7f0dfa04fc9977a36fb7eaffected · git
    • e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec and later · before 8d5d28285728be47c82fdf1c48be4268293c90e7affected · git
    • e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec and later · before 0679c0c189d2548f00e1bac95be28e2df5c6c7f7affected · git
    • e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec and later · before 6e26a41c4c1a706edaaa7c7dffc6b3b945707a55affected · git
    • e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec and later · before ee1d7274102285d78a53161fc705a8d8cd40b066affected · git
    • before 6.4not affected · semver
    • 6.6.151 and later · up to and including 6.6.*not affected · semver
    • 6.12.103 and later · up to and including 6.12.*not affected · semver
    • 6.18.44 and later · up to and including 6.18.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-74572Aug 15, 2026 · btrfs: zoned: fix deadlock between metadata writeback and transaction commit
    30Monitor
  • ← EarlierCVE-2026-74573Aug 15, 2026 · iommu/arm-smmu-v3-iommufd: Require exactly one Stream ID for a vDEVICE
    37Monitor
  • Later →CVE-2026-74575Aug 15, 2026 · thunderbolt: Prevent XDomain delayed work use-after-free on disconnect
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0679c0c189d2548f00e1bac95be28e2df5c6c7f7Vendor (CNA)
Linux Linux6e26a41c4c1a706edaaa7c7dffc6b3b945707a55Vendor (CNA)
Linux Linux778ccbded2c8749c5be7f0dfa04fc9977a36fb7eVendor (CNA)
Linux Linux8d5d28285728be47c82fdf1c48be4268293c90e7Vendor (CNA)
Linux Linuxee1d7274102285d78a53161fc705a8d8cd40b066Vendor (CNA)
almalinux:kernel6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.12.105-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.107-1~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+2

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records