{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40053 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40053 is a high-severity vulnerability in Linux, published on 28 Oct 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-2025-40053 and fix it if it is affected.\n\nWhat it is: CVE-2025-40053 is a high-severity vulnerability in Linux, published on 28 Oct 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-2025-40053 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-40053/ (Markdown: https://insights.sbomify.com/CVE-2025-40053/index.md)","id":"CVE-2025-40053","markdown":"https://insights.sbomify.com/CVE-2025-40053/index.md","name":"CVE-2025-40053","record":{"aliases":["AZL-68855","BELL-CVE-2025-40053","DEBIAN-CVE-2025-40053","GHSA-xxjc-4ppm-x655","ROOT-OS-DEBIAN-11-CVE-2025-40053","ROOT-OS-DEBIAN-12-CVE-2025-40053","ROOT-OS-DEBIAN-13-CVE-2025-40053","ROOT-OS-UBUNTU-2204-CVE-2025-40053","ROOT-OS-UBUNTU-2404-CVE-2025-40053","UBUNTU-CVE-2025-40053"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A missing check for memory allocation failure in the D-Link network driver can cause a kernel crash via null pointer dereference.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: dlink: handle copy_thresh allocation failure\n\nThe driver did not handle failure of `netdev_alloc_skb_ip_align()`.\nIf the allocation failed, dereferencing `skb-\u003eprotocol` could lead to\na NULL pointer dereference.\n\nThis patch tries to allocate `skb`. If the allocation fails, it falls\nback to the normal path.\n\nTested-on: D-Link DGE-550T Rev-A3","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":"net: dlink: handle copy_thresh allocation failure","id":"CVE-2025-40053","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"f2fs: fix UAF issue in f2fs_merge_page_bio()","id":"CVE-2025-40054"},"packages":[],"prev":{"headline":"smb: client: fix crypto buffers in non-linear memory","id":"CVE-2025-40052"},"products":["Linux"],"published":"2025-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"A missing check for memory allocation failure in the D-Link network driver can cause a kernel crash via null pointer dereference.","url":"https://insights.sbomify.com/CVE-2025-40053/"}