{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-47025 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-47025 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-47025 is a high-severity vulnerability in Linux kernel, published on 28 Feb 2024. 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-2021-47025 and fix it if it is affected.\n\nWhat it is: CVE-2021-47025 is a high-severity vulnerability in Linux kernel, published on 28 Feb 2024. 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-2021-47025 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-2021-47025/ (Markdown: https://insights.sbomify.com/CVE-2021-47025/index.md)","id":"CVE-2021-47025","markdown":"https://insights.sbomify.com/CVE-2021-47025/index.md","name":"CVE-2021-47025","record":{"aliases":["GHSA-w7xf-wp34-j8rv","UBUNTU-CVE-2021-47025"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A null pointer dereference in the MediaTek IOMMU driver during resume can cause a kernel warning and potential system instability.","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":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/mediatek: Always enable the clk on resume\n\nIn mtk_iommu_runtime_resume always enable the clk, even\nif m4u_dom is null. Otherwise the 'suspend' cb might\ndisable the clk which is already disabled causing the warning:\n\n[    1.586104] infra_m4u already disabled\n[    1.586133] WARNING: CPU: 0 PID: 121 at drivers/clk/clk.c:952 clk_core_disable+0xb0/0xb8\n[    1.594391] mtk-iommu 10205000.iommu: bound 18001000.larb (ops mtk_smi_larb_component_ops)\n[    1.598108] Modules linked in:\n[    1.598114] CPU: 0 PID: 121 Comm: kworker/0:2 Not tainted 5.12.0-rc5 #69\n[    1.609246] mtk-iommu 10205000.iommu: bound 14027000.larb (ops mtk_smi_larb_component_ops)\n[    1.617487] Hardware name: Google Elm (DT)\n[    1.617491] Workqueue: pm pm_runtime_work\n[    1.620545] mtk-iommu 10205000.iommu: bound 19001000.larb (ops mtk_smi_larb_component_ops)\n\n[    1.627229] pstate: 60000085 (nZCv daIf -PAN -UAO -TCO BTYPE=--)\n[    1.659297] pc : clk_core_disable+0xb0/0xb8\n[    1.663475] lr : clk_core_disable+0xb0/0xb8\n[    1.667652] sp : ffff800011b9bbe0\n[    1.670959] x29: ffff800011b9bbe0 x28: 0000000000000000\n[    1.676267] x27: ffff800011448000 x26: ffff8000100cfd98\n[    1.681574] x25: ffff800011b9bd48 x24: 0000000000000000\n[    1.686882] x23: 0000000000000000 x22: ffff8000106fad90\n[    1.692189] x21: 000000000000000a x20: ffff0000c0048500\n[    1.697496] x19: ffff0000c0048500 x18: ffffffffffffffff\n[    1.702804] x17: 0000000000000000 x16: 0000000000000000\n[    1.708112] x15: ffff800011460300 x14: fffffffffffe0000\n[    1.713420] x13: ffff8000114602d8 x12: 0720072007200720\n[    1.718727] x11: 0720072007200720 x10: 0720072007200720\n[    1.724035] x9 : ffff800011b9bbe0 x8 : ffff800011b9bbe0\n[    1.729342] x7 : 0000000000000009 x6 : ffff8000114b8328\n[    1.734649] x5 : 0000000000000000 x4 : 0000000000000000\n[    1.739956] x3 : 00000000ffffffff x2 : ffff800011460298\n[    1.745263] x1 : 1af1d7de276f4500 x0 : 0000000000000000\n[    1.750572] Call trace:\n[    1.753010]  clk_core_disable+0xb0/0xb8\n[    1.756840]  clk_core_disable_lock+0x24/0x40\n[    1.761105]  clk_disable+0x20/0x30\n[    1.764501]  mtk_iommu_runtime_suspend+0x88/0xa8\n[    1.769114]  pm_generic_runtime_suspend+0x2c/0x48\n[    1.773815]  __rpm_callback+0xe0/0x178\n[    1.777559]  rpm_callback+0x24/0x88\n[    1.781041]  rpm_suspend+0xdc/0x470\n[    1.784523]  rpm_idle+0x12c/0x170\n[    1.787831]  pm_runtime_work+0xa8/0xc0\n[    1.791573]  process_one_work+0x1e8/0x360\n[    1.795580]  worker_thread+0x44/0x478\n[    1.799237]  kthread+0x150/0x158\n[    1.802460]  ret_from_fork+0x10/0x30\n[    1.806034] ---[ end trace 82402920ef64573b ]---\n[    1.810728] ------------[ cut here ]------------\n\nIn addition, we now don't need to enable the clock from the\nfunction mtk_iommu_hw_init since it is already enabled by the resume.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"iommu/mediatek: Always enable the clk on resume","id":"CVE-2021-47025","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"RDMA/rtrs-clt: destroy sysfs after removing session from active list","id":"CVE-2021-47026"},"packages":[],"prev":{"headline":"vsock/virtio: free queued packets when closing socket","id":"CVE-2021-47024"},"products":["Linux"],"published":"2024-02-28","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A null pointer dereference in the MediaTek IOMMU driver during resume can cause a kernel warning and potential system instability.","url":"https://insights.sbomify.com/CVE-2021-47025/"}