GHSA-JX6X-8PX6-93F6

Vulnerability from github – Published: 2026-07-19 18:31 – Updated: 2026-07-19 18:31
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

wifi: wilc1000: fix dma_buffer leak on bus acquire failure

wilc_wlan_firmware_download() allocates dma_buffer with kmalloc() at the top of the function and uses a 'fail:' label to free it via kfree(dma_buffer) on error.

All later error paths correctly use 'goto fail' to route through this cleanup. However, the early failure path after the first acquire_bus() call uses a bare 'return ret;', which leaks dma_buffer whenever the bus acquire fails.

Replace the early return with goto fail so the existing cleanup path runs.

Found via a custom Coccinelle semantic patch hunting for kmalloc'd locals leaked on early-return error paths in driver firmware-download code.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-64145"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-19T16:17:56Z",
    "severity": null
  },
  "details": "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 \u0027fail:\u0027 label to free it via\nkfree(dma_buffer) on error.\n\nAll later error paths correctly use \u0027goto fail\u0027 to route through this\ncleanup. However, the early failure path after the first acquire_bus()\ncall uses a bare \u0027return ret;\u0027, 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\u0027d\nlocals leaked on early-return error paths in driver firmware-download\ncode.",
  "id": "GHSA-jx6x-8px6-93f6",
  "modified": "2026-07-19T18:31:53Z",
  "published": "2026-07-19T18:31:53Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-64145"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/32d7584441b9ecb279a03653b432612546e5efbe"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/95c82d498d74c4e587db30021ca1aec90e29b5a5"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/dd7b6a8671939708cc4b7a46786d8c11297e8f69"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…