{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54167 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54167 is a vulnerability in Linux, published on 30 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-54167 and fix it if it is affected.\n\nWhat it is: CVE-2023-54167 is a vulnerability in Linux, published on 30 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-54167 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-54167/ (Markdown: https://insights.sbomify.com/CVE-2023-54167/index.md)","id":"CVE-2023-54167","markdown":"https://insights.sbomify.com/CVE-2023-54167/index.md","name":"CVE-2023-54167","record":{"aliases":["BELL-CVE-2023-54167","DEBIAN-CVE-2023-54167","GHSA-m7mj-mw9m-293g","UBUNTU-CVE-2023-54167"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A kernel crash occurs when booting with an initial ramdisk on specific m68k platforms due to premature memory address translation.","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\nm68k: mm: Move initrd phys_to_virt handling after paging_init()\n\nWhen booting with an initial ramdisk on platforms where physical memory\ndoes not start at address zero (e.g. on Amiga):\n\n    initrd: 0ef0602c - 0f800000\n    Zone ranges:\n      DMA      [mem 0x0000000008000000-0x000000f7ffffffff]\n      Normal   empty\n    Movable zone start for each node\n    Early memory node ranges\n      node   0: [mem 0x0000000008000000-0x000000000f7fffff]\n    Initmem setup node 0 [mem 0x0000000008000000-0x000000000f7fffff]\n    Unable to handle kernel access at virtual address (ptrval)\n    Oops: 00000000\n    Modules linked in:\n    PC: [\u003c00201d3c\u003e] memcmp+0x28/0x56\n\nAs phys_to_virt() relies on m68k_memoffset and module_fixup(), it must\nnot be called before paging_init().  Hence postpone the phys_to_virt\nhandling for the initial ramdisk until after calling paging_init().\n\nWhile at it, reduce #ifdef clutter by using IS_ENABLED() instead.","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":"m68k: mm: Move initrd phys_to_virt handling after paging_init()","id":"CVE-2023-54167","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":"RDMA/mlx4: Prevent shift wrapping in set_user_sq_size()","id":"CVE-2023-54168"},"packages":[],"prev":{"headline":"igc: Fix Kernel Panic during ndo_tx_timeout callback","id":"CVE-2023-54166"},"products":["Linux"],"published":"2025-12-30","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 kernel crash occurs when booting with an initial ramdisk on specific m68k platforms due to premature memory address translation.","url":"https://insights.sbomify.com/CVE-2023-54167/"}