{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-21713 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-21713 is a medium-severity vulnerability in Linux kernel, published on 27 Feb 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-21713 and fix it if it is affected.\n\nWhat it is: CVE-2025-21713 is a medium-severity vulnerability in Linux kernel, published on 27 Feb 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-21713 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-21713/ (Markdown: https://insights.sbomify.com/CVE-2025-21713/index.md)","id":"CVE-2025-21713","markdown":"https://insights.sbomify.com/CVE-2025-21713/index.md","name":"CVE-2025-21713","record":{"aliases":["BELL-CVE-2025-21713","DEBIAN-CVE-2025-21713","GHSA-r24p-j496-7rxg","UBUNTU-CVE-2025-21713"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can trigger a kernel crash by attaching a VFIO group to a container, causing a null pointer dereference in the PowerPC IOMMU driver.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/pseries/iommu: Don't unset window if it was never set\n\nOn pSeries, when user attempts to use the same vfio container used by\ndifferent iommu group, the spapr_tce_set_window() returns -EPERM\nand the subsequent cleanup leads to the below crash.\n\n   Kernel attempted to read user page (308) - exploit attempt?\n   BUG: Kernel NULL pointer dereference on read at 0x00000308\n   Faulting instruction address: 0xc0000000001ce358\n   Oops: Kernel access of bad area, sig: 11 [#1]\n   NIP:  c0000000001ce358 LR: c0000000001ce05c CTR: c00000000005add0\n   \u003csnip\u003e\n   NIP [c0000000001ce358] spapr_tce_unset_window+0x3b8/0x510\n   LR [c0000000001ce05c] spapr_tce_unset_window+0xbc/0x510\n   Call Trace:\n     spapr_tce_unset_window+0xbc/0x510 (unreliable)\n     tce_iommu_attach_group+0x24c/0x340 [vfio_iommu_spapr_tce]\n     vfio_container_attach_group+0xec/0x240 [vfio]\n     vfio_group_fops_unl_ioctl+0x548/0xb00 [vfio]\n     sys_ioctl+0x754/0x1580\n     system_call_exception+0x13c/0x330\n     system_call_vectored_common+0x15c/0x2ec\n   \u003csnip\u003e\n   --- interrupt: 3000\n\nFix this by having null check for the tbl passed to the\nspapr_tce_unset_window().","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":"powerpc/pseries/iommu: Don't unset window if it was never set","id":"CVE-2025-21713","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"RDMA/mlx5: Fix implicit ODP use after free","id":"CVE-2025-21714"},"packages":[],"prev":{"headline":"md/md-bitmap: Synchronize bitmap_get_stats() with bitmap lifetime","id":"CVE-2025-21712"},"products":["Linux"],"published":"2025-02-27","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A local attacker can trigger a kernel crash by attaching a VFIO group to a container, causing a null pointer dereference in the PowerPC IOMMU driver.","url":"https://insights.sbomify.com/CVE-2025-21713/"}