{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-53789 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53789 is a vulnerability in Linux, published on 9 Dec 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-53789 and fix it if it is affected.\n\nWhat it is: CVE-2023-53789 is a vulnerability in Linux, published on 9 Dec 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-53789 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-2023-53789/ (Markdown: https://insights.sbomify.com/CVE-2023-53789/index.md)","id":"CVE-2023-53789","markdown":"https://insights.sbomify.com/CVE-2023-53789/index.md","name":"CVE-2023-53789","record":{"aliases":["BELL-CVE-2023-53789","DEBIAN-CVE-2023-53789","GHSA-p3hr-pr7r-f6m2","ROOT-OS-UBUNTU-2204-CVE-2023-53789","UBUNTU-CVE-2023-53789"],"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":"none","summary":"A null pointer dereference in the AMD IOMMU page fault handler can cause a kernel crash, leading to denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\niommu/amd: Improve page fault error reporting\n\nIf IOMMU domain for device group is not setup properly then we may hit\nIOMMU page fault. Current page fault handler assumes that domain is\nalways setup and it will hit NULL pointer derefence (see below sample log).\n\nLets check whether domain is setup or not and log appropriate message.\n\nSample log:\n----------\n amdgpu 0000:00:01.0: amdgpu: SE 1, SH per SE 1, CU per SH 8, active_cu_number 6\n BUG: kernel NULL pointer dereference, address: 0000000000000058\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n PGD 0 P4D 0\n Oops: 0000 [#1] PREEMPT SMP NOPTI\n CPU: 2 PID: 56 Comm: irq/24-AMD-Vi Not tainted 6.2.0-rc2+ #89\n Hardware name: xxx\n RIP: 0010:report_iommu_fault+0x11/0x90\n [...]\n Call Trace:\n  \u003cTASK\u003e\n  amd_iommu_int_thread+0x60c/0x760\n  ? __pfx_irq_thread_fn+0x10/0x10\n  irq_thread_fn+0x1f/0x60\n  irq_thread+0xea/0x1a0\n  ? preempt_count_add+0x6a/0xa0\n  ? __pfx_irq_thread_dtor+0x10/0x10\n  ? __pfx_irq_thread+0x10/0x10\n  kthread+0xe9/0x110\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork+0x2c/0x50\n  \u003c/TASK\u003e\n\n[joro: Edit commit message]","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":"iommu/amd: Improve page fault error reporting","id":"CVE-2023-53789","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"bpf: Zeroing allocated object from slab in bpf memory allocator","id":"CVE-2023-53790"},"packages":[],"prev":{"headline":"ALSA: hda/ca0132: fixup buffer overrun at tuning_ctl_set()","id":"CVE-2023-53788"},"products":["Linux"],"published":"2025-12-09","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-05-11","vendors":["Linux"]},"summary":"A null pointer dereference in the AMD IOMMU page fault handler can cause a kernel crash, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2023-53789/"}