Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-40058: iommu/vt-d: Disallow dirty tracking if incoherent page walk

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.16% (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 57f55048e564dedd8a4546d018e29d6bbfff0a7e, 8d096ce0e87bdc361f0b25d7943543bc53aa0b9e, ebe16d245a00626bb87163862a1b07daf5475a3e.

Low priority for now. Upgrade to Linux Linux 57f55048e564dedd8a4546d018e29d6bbfff0a7e, 8d096ce0e87bdc361f0b25d7943543bc53aa0b9e, ebe16d245a00626bb87163862a1b07daf5475a3e 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: Disallow dirty tracking if incoherent page walk Dirty page tracking relies on the IOMMU atomically updating the dirty bit in the paging-structure entry. For this operation to succeed, the paging- structure memory must be coherent between the IOMMU and the CPU. In another word, if the iommu page walk is incoherent, dirty page tracking doesn't work. The Intel VT-d specification, Section 3.10 "Snoop Behavior" states: "Remapping hardware encountering the need to atomically update A/EA/D bits in a paging-structure entry that is not snooped will result in a non- recoverable fault." To prevent an IOMMU from being incorrectly configured for dirty page tracking when it is operating in an incoherent mode, mark SSADS as supported only when both ecap_slads and ecap_smpwc are supported.

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Oct 28, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 5th percentile
CWE
—

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%

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-2025-40058

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.

—

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.7affected
    • f35f22cc760eb2c7034bf53251399685d611e03f and later · before ebe16d245a00626bb87163862a1b07daf5475a3eaffected · git
    • f35f22cc760eb2c7034bf53251399685d611e03f and later · before 8d096ce0e87bdc361f0b25d7943543bc53aa0b9eaffected · git
    • f35f22cc760eb2c7034bf53251399685d611e03f and later · before 57f55048e564dedd8a4546d018e29d6bbfff0a7eaffected · git
    • before 6.7not affected · semver
    • 6.12.53 and later · up to and including 6.12.*not affected · semver
    • 6.17.3 and later · up to and including 6.17.*not affected · semver
    • 6.18 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.20.1.el10_16.12.0-124.20.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.20.1.el10_16.12.0-124.20.1.el10_1
AlmaLinux:9kernelbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64kbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64k-corebefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64k-debugbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64k-develbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-corebefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-cross-headersbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-debugbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-debug-corebefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-debug-develbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-611.11.1.el9_75.14.0-611.11.1.el9_7

+96

Same product

linux: all records

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-2025-40056Oct 28, 2025 · vhost: vringh: Fix copy_to_iter return value check
    0Monitor
  • ← EarlierCVE-2025-40057Oct 28, 2025 · ptp: Add a upper bound on max_vclocks
    0Monitor
  • Later →CVE-2025-40059Oct 28, 2025 · coresight: Fix incorrect handling for return value of devm_kzalloc
    0Monitor

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 Linux57f55048e564dedd8a4546d018e29d6bbfff0a7eVendor (CNA)
Linux Linux8d096ce0e87bdc361f0b25d7943543bc53aa0b9eVendor (CNA)
Linux Linuxebe16d245a00626bb87163862a1b07daf5475a3eVendor (CNA)
almalinux:kernel5.14.0-611.11.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.11.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.11.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.11.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.11.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.11.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.11.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.11.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.11.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.11.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-611.11.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-611.11.1.el9_7 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.57-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:kernel0:5.14.0-611.11.1.el9_7 · Rocky Linux:9Package registry (OSV)

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).

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)

—

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. Fix✗ → ✓

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

References

Show all references (2 more)

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

All records