{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-64145 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-64145 is a high-severity memory corruption vulnerability in Linux kernel, published on 19 Jul 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-2026-64145 and fix it if it is affected.\n\nWhat it is: CVE-2026-64145 is a high-severity memory corruption vulnerability in Linux kernel, published on 19 Jul 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-2026-64145 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-2026-64145/ (Markdown: https://insights.sbomify.com/CVE-2026-64145/index.md)","id":"CVE-2026-64145","markdown":"https://insights.sbomify.com/CVE-2026-64145/index.md","name":"CVE-2026-64145","record":{"aliases":["BELL-CVE-2026-64145","DEBIAN-CVE-2026-64145","GHSA-jx6x-8px6-93f6","UBUNTU-CVE-2026-64145"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A memory leak in the wilc1000 WiFi driver allows attackers to cause denial of service by triggering bus acquire failures during firmware download.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: wilc1000: fix dma_buffer leak on bus acquire failure\n\nwilc_wlan_firmware_download() allocates dma_buffer with kmalloc() at\nthe top of the function and uses a 'fail:' label to free it via\nkfree(dma_buffer) on error.\n\nAll later error paths correctly use 'goto fail' to route through this\ncleanup. However, the early failure path after the first acquire_bus()\ncall uses a bare 'return ret;', which leaks dma_buffer whenever the bus\nacquire fails.\n\nReplace the early return with goto fail so the existing cleanup path\nruns.\n\nFound via a custom Coccinelle semantic patch hunting for kmalloc'd\nlocals leaked on early-return error paths in driver firmware-download\ncode.","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":"wifi: wilc1000: fix dma_buffer leak on bus acquire failure","id":"CVE-2026-64145","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"erofs: fix metabuf leak in inode xattr initialization","id":"CVE-2026-64146"},"packages":[],"prev":{"headline":"Bluetooth: btmtk: fix urb-\u003esetup_packet leak in error paths","id":"CVE-2026-64144"},"products":["Linux"],"published":"2026-07-19","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-07-19","vendors":["Linux"]},"summary":"A memory leak in the wilc1000 WiFi driver allows attackers to cause denial of service by triggering bus acquire failures during firmware download.","url":"https://insights.sbomify.com/CVE-2026-64145/"}