{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74524 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74524 is a memory corruption vulnerability in Linux, published on 15 Aug 2026. 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-2026-74524 and fix it if it is affected.\n\nWhat it is: CVE-2026-74524 is a memory corruption vulnerability in Linux, published on 15 Aug 2026. 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-2026-74524 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-2026-74524/ (Markdown: https://insights.sbomify.com/CVE-2026-74524/index.md)","id":"CVE-2026-74524","markdown":"https://insights.sbomify.com/CVE-2026-74524/index.md","name":"CVE-2026-74524","record":{"aliases":["BELL-CVE-2026-74524","DEBIAN-CVE-2026-74524","GHSA-273p-44hj-2v3c","UBUNTU-CVE-2026-74524"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A memory hot-remove flaw in the RISC-V Linux kernel allows out-of-bounds page-table walks, potentially causing system crashes or arbitrary code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: mm: Fix out-of-bounds page-table walk during memory hot-remove\n\nremove_pud_mapping() and remove_p4d_mapping() obtain a child table base\nwith pud_offset(p4dp, 0) and p4d_offset(pgd, 0), then add the index for\naddr.\n\nRISC-V folds page-table levels at runtime. When a level is folded, its\noffset helper returns the parent entry itself, but the index can still be\nnonzero. Adding it walks past the parent table. Sv48 folds P4D, while Sv39\nfolds both P4D and PUD, so memory hot-remove can descend into unrelated\nmemory and pass an invalid page to __free_pages(). This can trigger:\n\n  kernel BUG at include/linux/mm.h:1810!\n  VM_BUG_ON_PAGE(page_ref_count(page) == 0)\n  arch_remove_memory+0x1e/0x5c\n  try_remove_memory+0x15e/0x200\n  remove_memory+0x24/0x3c\n\nOnly add the index when the corresponding page-table level is enabled,\nmatching p4d_offset() and pud_offset().","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":"riscv: mm: Fix out-of-bounds page-table walk during memory hot-remove","id":"CVE-2026-74524","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"net: sxgbe: free TX rings on RX allocation failure","id":"CVE-2026-74525"},"packages":[],"prev":{"headline":"qede: sync udp_tunnel ports outside qede_lock in the recovery path","id":"CVE-2026-74523"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A memory hot-remove flaw in the RISC-V Linux kernel allows out-of-bounds page-table walks, potentially causing system crashes or arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2026-74524/"}