{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68787 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68787 is a memory corruption vulnerability in Linux, published on 13 Jan 2026. 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-2025-68787 and fix it if it is affected.\n\nWhat it is: CVE-2025-68787 is a memory corruption vulnerability in Linux, published on 13 Jan 2026. 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-2025-68787 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-2025-68787/ (Markdown: https://insights.sbomify.com/CVE-2025-68787/index.md)","id":"CVE-2025-68787","markdown":"https://insights.sbomify.com/CVE-2025-68787/index.md","name":"CVE-2025-68787","record":{"aliases":["AZL-74390","BELL-CVE-2025-68787","DEBIAN-CVE-2025-68787","GHSA-6prc-rrx9-j93r","ROOT-OS-DEBIAN-11-CVE-2025-68787","ROOT-OS-DEBIAN-12-CVE-2025-68787","ROOT-OS-DEBIAN-13-CVE-2025-68787","ROOT-OS-UBUNTU-2204-CVE-2025-68787","ROOT-OS-UBUNTU-2404-CVE-2025-68787","UBUNTU-CVE-2025-68787"],"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":"low_privilege","summary":"A memory leak in the Linux kernel's netrom module allows local attackers to exhaust system memory, causing denial of service.","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\nnetrom: Fix memory leak in nr_sendmsg()\n\nsyzbot reported a memory leak [1].\n\nWhen function sock_alloc_send_skb() return NULL in nr_output(), the\noriginal skb is not freed, which was allocated in nr_sendmsg(). Fix this\nby freeing it before return.\n\n[1]\nBUG: memory leak\nunreferenced object 0xffff888129f35500 (size 240):\n  comm \"syz.0.17\", pid 6119, jiffies 4294944652\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n    00 00 00 00 00 00 00 00 00 10 52 28 81 88 ff ff  ..........R(....\n  backtrace (crc 1456a3e4):\n    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]\n    slab_post_alloc_hook mm/slub.c:4983 [inline]\n    slab_alloc_node mm/slub.c:5288 [inline]\n    kmem_cache_alloc_node_noprof+0x36f/0x5e0 mm/slub.c:5340\n    __alloc_skb+0x203/0x240 net/core/skbuff.c:660\n    alloc_skb include/linux/skbuff.h:1383 [inline]\n    alloc_skb_with_frags+0x69/0x3f0 net/core/skbuff.c:6671\n    sock_alloc_send_pskb+0x379/0x3e0 net/core/sock.c:2965\n    sock_alloc_send_skb include/net/sock.h:1859 [inline]\n    nr_sendmsg+0x287/0x450 net/netrom/af_netrom.c:1105\n    sock_sendmsg_nosec net/socket.c:727 [inline]\n    __sock_sendmsg net/socket.c:742 [inline]\n    sock_write_iter+0x293/0x2a0 net/socket.c:1195\n    new_sync_write fs/read_write.c:593 [inline]\n    vfs_write+0x45d/0x710 fs/read_write.c:686\n    ksys_write+0x143/0x170 fs/read_write.c:738\n    do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n    do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94\n    entry_SYSCALL_64_after_hwframe+0x77/0x7f","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":"netrom: Fix memory leak in nr_sendmsg()","id":"CVE-2025-68787","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"fsnotify: do not generate ACCESS/MODIFY events on child for special files","id":"CVE-2025-68788"},"packages":[],"prev":{"headline":"ksmbd: skip lock-range check on equal size to avoid size==0 underflow","id":"CVE-2025-68786"},"products":["Linux"],"published":"2026-01-13","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-10-15","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel's netrom module allows local attackers to exhaust system memory, causing denial of service.","url":"https://insights.sbomify.com/CVE-2025-68787/"}