{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54034 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54034 is a vulnerability in Linux, published on 24 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-54034 and fix it if it is affected.\n\nWhat it is: CVE-2023-54034 is a vulnerability in Linux, published on 24 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-54034 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-54034/ (Markdown: https://insights.sbomify.com/CVE-2023-54034/index.md)","id":"CVE-2023-54034","markdown":"https://insights.sbomify.com/CVE-2023-54034/index.md","name":"CVE-2023-54034","record":{"aliases":["BELL-CVE-2023-54034","GHSA-47gj-cqh4-pq8c","UBUNTU-CVE-2023-54034"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can read uninitialized kernel memory via the iommufd subsystem due to missing zero initialization in vfio_iommu_type1_info.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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\niommufd: Make sure to zero vfio_iommu_type1_info before copying to user\n\nMissed a zero initialization here. Most of the struct is filled with\na copy_from_user(), however minsz for that copy is smaller than the\nactual struct by 8 bytes, thus we don't fill the padding.","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":"iommufd: Make sure to zero vfio_iommu_type1_info before copying to user","id":"CVE-2023-54034","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"netfilter: nf_tables: fix underflow in chain reference counter","id":"CVE-2023-54035"},"packages":[],"prev":{"headline":"bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps","id":"CVE-2023-54033"},"products":["Linux"],"published":"2025-12-24","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 local attacker can read uninitialized kernel memory via the iommufd subsystem due to missing zero initialization in vfio_iommu_type1_info.","url":"https://insights.sbomify.com/CVE-2023-54034/"}