{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54049 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54049 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-54049 and fix it if it is affected.\n\nWhat it is: CVE-2023-54049 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-54049 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-54049/ (Markdown: https://insights.sbomify.com/CVE-2023-54049/index.md)","id":"CVE-2023-54049","markdown":"https://insights.sbomify.com/CVE-2023-54049/index.md","name":"CVE-2023-54049","record":{"aliases":["BELL-CVE-2023-54049","DEBIAN-CVE-2023-54049","GHSA-r9ff-8j26-q598","UBUNTU-CVE-2023-54049"],"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 missing check for kstrdup return value in the Linux kernel rpmsg glink driver can lead to a NULL pointer dereference and system crash.","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\nrpmsg: glink: Add check for kstrdup\n\nAdd check for the return value of kstrdup() and return the error\nif it fails in order to avoid NULL pointer dereference.","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":"rpmsg: glink: Add check for kstrdup","id":"CVE-2023-54049","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":9,"next":{"headline":"ubifs: Fix memleak when insert_old_idx() failed","id":"CVE-2023-54050"},"packages":[],"prev":{"headline":"RDMA/bnxt_re: Prevent handling any completions after qp destroy","id":"CVE-2023-54048"},"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 missing check for kstrdup return value in the Linux kernel rpmsg glink driver can lead to a NULL pointer dereference and system crash.","url":"https://insights.sbomify.com/CVE-2023-54049/"}