{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-47535 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2021-47535 is a high-severity memory corruption vulnerability in Linux kernel, published on 24 May 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-47535 and fix it if it is affected.\n\nWhat it is: CVE-2021-47535 is a high-severity memory corruption vulnerability in Linux kernel, published on 24 May 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-47535 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-47535/ (Markdown: https://insights.sbomify.com/CVE-2021-47535/index.md)","id":"CVE-2021-47535","markdown":"https://insights.sbomify.com/CVE-2021-47535/index.md","name":"CVE-2021-47535","record":{"aliases":["DEBIAN-CVE-2021-47535","UBUNTU-CVE-2021-47535"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel GPU driver","requires_auth":"low_privilege","summary":"A memory corruption vulnerability in the Linux kernel's MSM GPU driver allows a local attacker to cause a system crash via out-of-bounds write.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/a6xx: Allocate enough space for GMU registers\n\nIn commit 142639a52a01 (\"drm/msm/a6xx: fix crashstate capture for\nA650\") we changed a6xx_get_gmu_registers() to read 3 sets of\nregisters. Unfortunately, we didn't change the memory allocation for\nthe array. That leads to a KASAN warning (this was on the chromeos-5.4\nkernel, which has the problematic commit backported to it):\n\n  BUG: KASAN: slab-out-of-bounds in _a6xx_get_gmu_registers+0x144/0x430\n  Write of size 8 at addr ffffff80c89432b0 by task A618-worker/209\n  CPU: 5 PID: 209 Comm: A618-worker Tainted: G        W         5.4.156-lockdep #22\n  Hardware name: Google Lazor Limozeen without Touchscreen (rev5 - rev8) (DT)\n  Call trace:\n   dump_backtrace+0x0/0x248\n   show_stack+0x20/0x2c\n   dump_stack+0x128/0x1ec\n   print_address_description+0x88/0x4a0\n   __kasan_report+0xfc/0x120\n   kasan_report+0x10/0x18\n   __asan_report_store8_noabort+0x1c/0x24\n   _a6xx_get_gmu_registers+0x144/0x430\n   a6xx_gpu_state_get+0x330/0x25d4\n   msm_gpu_crashstate_capture+0xa0/0x84c\n   recover_worker+0x328/0x838\n   kthread_worker_fn+0x32c/0x574\n   kthread+0x2dc/0x39c\n   ret_from_fork+0x10/0x18\n\n  Allocated by task 209:\n   __kasan_kmalloc+0xfc/0x1c4\n   kasan_kmalloc+0xc/0x14\n   kmem_cache_alloc_trace+0x1f0/0x2a0\n   a6xx_gpu_state_get+0x164/0x25d4\n   msm_gpu_crashstate_capture+0xa0/0x84c\n   recover_worker+0x328/0x838\n   kthread_worker_fn+0x32c/0x574\n   kthread+0x2dc/0x39c\n   ret_from_fork+0x10/0x18","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":"drm/msm/a6xx: Allocate enough space for GMU registers","id":"CVE-2021-47535","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"net/smc: fix wrong list_del in smc_lgr_cleanup_early","id":"CVE-2021-47536"},"packages":[],"prev":{"headline":"drm/vc4: kms: Add missing drm_crtc_commit_put","id":"CVE-2021-47534"},"products":["Linux"],"published":"2024-05-24","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-08-05","vendors":["Linux"]},"summary":"A memory corruption vulnerability in the Linux kernel's MSM GPU driver allows a local attacker to cause a system crash via out-of-bounds write.","url":"https://insights.sbomify.com/CVE-2021-47535/"}