{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-53825 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53825 is a memory corruption vulnerability in Linux, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-53825 and fix it if it is affected.\n\nWhat it is: CVE-2023-53825 is a memory corruption vulnerability in Linux, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-53825 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-53825/ (Markdown: https://insights.sbomify.com/CVE-2023-53825/index.md)","id":"CVE-2023-53825","markdown":"https://insights.sbomify.com/CVE-2023-53825/index.md","name":"CVE-2023-53825","record":{"aliases":["BELL-CVE-2023-53825","DEBIAN-CVE-2023-53825","GHSA-qqwx-6fr4-mfj2","UBUNTU-CVE-2023-53825"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A memory leak in the Linux kernel's kcm module can lead to resource exhaustion and denial of service when handling SOCK_DGRAM messages.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nkcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().\n\nsyzkaller found a memory leak in kcm_sendmsg(), and commit c821a88bd720\n(\"kcm: Fix memory leak in error path of kcm_sendmsg()\") suppressed it by\nupdating kcm_tx_msg(head)-\u003elast_skb if partial data is copied so that the\nfollowing sendmsg() will resume from the skb.\n\nHowever, we cannot know how many bytes were copied when we get the error.\nThus, we could mess up the MSG_MORE queue.\n\nWhen kcm_sendmsg() fails for SOCK_DGRAM, we should purge the queue as we\ndo so for UDP by udp_flush_pending_frames().\n\nEven without this change, when the error occurred, the following sendmsg()\nresumed from a wrong skb and the queue was messed up.  However, we have\nyet to get such a report, and only syzkaller stumbled on it.  So, this\ncan be changed safely.\n\nNote this does not change SOCK_SEQPACKET behaviour.","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":"kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().","id":"CVE-2023-53825","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":8,"next":{"headline":"ubi: Fix UAF wear-leveling entry in eraseblk_count_seq_show()","id":"CVE-2023-53826"},"packages":[],"prev":{"headline":"netlink: annotate lockless accesses to nlk-\u003emax_recvmsg_len","id":"CVE-2023-53824"},"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 memory leak in the Linux kernel's kcm module can lead to resource exhaustion and denial of service when handling SOCK_DGRAM messages.","url":"https://insights.sbomify.com/CVE-2023-53825/"}