{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-53193 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53193 is a medium-severity vulnerability in Linux kernel, published on 15 Sep 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-2023-53193 and fix it if it is affected.\n\nWhat it is: CVE-2023-53193 is a medium-severity vulnerability in Linux kernel, published on 15 Sep 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-2023-53193 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-2023-53193/ (Markdown: https://insights.sbomify.com/CVE-2023-53193/index.md)","id":"CVE-2023-53193","markdown":"https://insights.sbomify.com/CVE-2023-53193/index.md","name":"CVE-2023-53193","record":{"aliases":["BELL-CVE-2023-53193","DEBIAN-CVE-2023-53193","GHSA-gp6f-2x9v-vp2f","UBUNTU-CVE-2023-53193"],"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 amdgpu driver causes a kernel call trace and potential system crash during hardware finalization.","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":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix amdgpu_irq_put call trace in gmc_v10_0_hw_fini\n\nThe gmc.ecc_irq is enabled by firmware per IFWI setting,\nand the host driver is not privileged to enable/disable\nthe interrupt. So, it is meaningless to use the amdgpu_irq_put\nfunction in gmc_v10_0_hw_fini, which also leads to the call\ntrace.\n\n[   82.340264] Call Trace:\n[   82.340265]  \u003cTASK\u003e\n[   82.340269]  gmc_v10_0_hw_fini+0x83/0xa0 [amdgpu]\n[   82.340447]  gmc_v10_0_suspend+0xe/0x20 [amdgpu]\n[   82.340623]  amdgpu_device_ip_suspend_phase2+0x127/0x1c0 [amdgpu]\n[   82.340789]  amdgpu_device_ip_suspend+0x3d/0x80 [amdgpu]\n[   82.340955]  amdgpu_device_pre_asic_reset+0xdd/0x2b0 [amdgpu]\n[   82.341122]  amdgpu_device_gpu_recover.cold+0x4dd/0xbb2 [amdgpu]\n[   82.341359]  amdgpu_debugfs_reset_work+0x4c/0x70 [amdgpu]\n[   82.341529]  process_one_work+0x21d/0x3f0\n[   82.341535]  worker_thread+0x1fa/0x3c0\n[   82.341538]  ? process_one_work+0x3f0/0x3f0\n[   82.341540]  kthread+0xff/0x130\n[   82.341544]  ? kthread_complete_and_exit+0x20/0x20\n[   82.341547]  ret_from_fork+0x22/0x30","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/amdgpu: fix amdgpu_irq_put call trace in gmc_v10_0_hw_fini","id":"CVE-2023-53193","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"fs/ntfs3: Add length check in indx_get_root","id":"CVE-2023-53194"},"packages":[],"prev":{"headline":"vxlan: Fix nexthop hash size","id":"CVE-2023-53192"},"products":["Linux"],"published":"2025-09-15","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-23","vendors":["Linux"]},"summary":"A null pointer dereference in the amdgpu driver causes a kernel call trace and potential system crash during hardware finalization.","url":"https://insights.sbomify.com/CVE-2023-53193/"}