{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40058 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40058 is a high-severity vulnerability in Linux, published on 28 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-40058 and fix it if it is affected.\n\nWhat it is: CVE-2025-40058 is a high-severity vulnerability in Linux, published on 28 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-40058 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-40058/ (Markdown: https://insights.sbomify.com/CVE-2025-40058/index.md)","id":"CVE-2025-40058","markdown":"https://insights.sbomify.com/CVE-2025-40058/index.md","name":"CVE-2025-40058","record":{"aliases":["BELL-CVE-2025-40058","DEBIAN-CVE-2025-40058","GHSA-hwfw-95mf-c924","ROOT-OS-DEBIAN-13-CVE-2025-40058","ROOT-OS-UBUNTU-2404-CVE-2025-40058","UBUNTU-CVE-2025-40058"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel IOMMU","requires_auth":"low_privilege","summary":"Improper IOMMU configuration allows non-recoverable faults when dirty tracking is enabled on incoherent page walks, causing system crashes.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/vt-d: Disallow dirty tracking if incoherent page walk\n\nDirty page tracking relies on the IOMMU atomically updating the dirty bit\nin the paging-structure entry. For this operation to succeed, the paging-\nstructure memory must be coherent between the IOMMU and the CPU. In\nanother word, if the iommu page walk is incoherent, dirty page tracking\ndoesn't work.\n\nThe Intel VT-d specification, Section 3.10 \"Snoop Behavior\" states:\n\n\"Remapping hardware encountering the need to atomically update A/EA/D bits\n in a paging-structure entry that is not snooped will result in a non-\n recoverable fault.\"\n\nTo prevent an IOMMU from being incorrectly configured for dirty page\ntracking when it is operating in an incoherent mode, mark SSADS as\nsupported only when both ecap_slads and ecap_smpwc are supported.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"iommu/vt-d: Disallow dirty tracking if incoherent page walk","id":"CVE-2025-40058","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"coresight: Fix incorrect handling for return value of devm_kzalloc","id":"CVE-2025-40059"},"packages":[],"prev":{"headline":"ptp: Add a upper bound on max_vclocks","id":"CVE-2025-40057"},"products":["Linux"],"published":"2025-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"Improper IOMMU configuration allows non-recoverable faults when dirty tracking is enabled on incoherent page walks, causing system crashes.","url":"https://insights.sbomify.com/CVE-2025-40058/"}