Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53281: iommu/vt-d: Avoid NULL pointer dereference or refcount corruption

Noroxi assessment

Priority: Monitor (action score 35/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.18% (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 6.12.114, 6.14, 79ea2feb917b05366b49d85573c9c5331f043b2c.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 6.12.114, 6.14, 79ea2feb917b05366b49d85573c9c5331f043b2c 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: iommu/vt-d: Avoid NULL pointer dereference or refcount corruption Commit 60f030f7418d ("iommu/vt-d: Avoid use of NULL after WARN_ON_ONCE") fixed a NULL pointer dereference in an unlikely situation partly. If dev_pasid is not found in the dev_pasids list, it remains NULL. However, the teardown operations are executed unconditionally, this lead to a NULL pointer dereference or refcount corruption. If the domain was never attached to this IOMMU, info will be NULL, which would cause an immediate dereference when checking --info->refcnt. Even if info is not NULL, decrementing the refcount without having removed a valid PASID might unbalance the count. This could lead to premature dropping of the refcount to 0, potentially causing a use-after-free for the remaining active devices sharing the domain. Fix it by returning early if dev_pasid is NULL, before executing the teardown operations. Issue found by AI review and suggested by Kevin Tian. https://sashiko.dev/#/patchset/20260421031347.1408890-1-zhenzhong.duan%40intel.com

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Jun 26, 2026
Updated
Oct 21, 2026
EPSS
0.1% · 8th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.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
8.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-53281

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.12.57 and later · before 6.13
  • linux linux kernel6.13.3 and later · before 6.18.33
  • linux linux kernel6.19 and later · before 7.0.10
  • linux linux kernel7.1

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

    • df96876be3b064aefc493f760e0639765d13ed0d, 6.14affected
    • 68ec78beb4a3fb0877cbaaf49758c85410c05977 and later · before d1a677f9c5e02c4ae49614044ac21296660d1391affected · git
    • 60f030f7418d3f1d94f2fb207fe3080e1844630b and later · before 9022cb9ac0c2a72a57fa8ebf92ac74f953ca0153affected · git
    • 60f030f7418d3f1d94f2fb207fe3080e1844630b and later · before cdfe3c9f2c9e28a8651ee463c88ad191ced2f840affected · git
    • 60f030f7418d3f1d94f2fb207fe3080e1844630b and later · before 79ea2feb917b05366b49d85573c9c5331f043b2caffected · git
    • 6.12.57 and later · before 6.12.114affected · semver
    • 6.13.3 and later · before 6.14affected · semver
    • before 6.14not affected · semver
    • 6.12.114 and later · up to and including 6.12.*not affected · semver
    • 6.18.33 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.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.40.1.el10_26.12.0-211.40.1.el10_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53323Jun 26, 2026 · net: dsa: remove redundant netdev_lock_ops() from conduit ethtool ops
    22Monitor
  • ← EarlierCVE-2026-53324Jun 26, 2026 · net: mana: Use pci_name() for debugfs directory naming
    22Monitor
  • Later →CVE-2026-53284Jun 26, 2026 · btrfs: only release the dirty pages io tree after successful writes
    30Monitor

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 Linux6.12.114Vendor (CNA)
Linux Linux6.14Vendor (CNA)
Linux Linux79ea2feb917b05366b49d85573c9c5331f043b2cVendor (CNA)
Linux Linux9022cb9ac0c2a72a57fa8ebf92ac74f953ca0153Vendor (CNA)
Linux Linuxcdfe3c9f2c9e28a8651ee463c88ad191ced2f840Vendor (CNA)
Linux Linuxd1a677f9c5e02c4ae49614044ac21296660d1391Vendor (CNA)
almalinux:kernel6.12.0-211.40.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.40.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.40.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.40.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.40.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.40.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.40.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.40.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.40.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.40.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.40.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.40.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux7.0.10-1 · Debian:14Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.40.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.40.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.40.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.40.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.40.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.40.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.40.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.40.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.40.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.40.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-211.40.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.

No history yet (it accumulates with the daily EPSS job).

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.

Credits

All researchers

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

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records