GHSA-HCPJ-XWWG-JGH9

Vulnerability from github – Published: 2025-12-24 12:30 – Updated: 2025-12-24 12:30
VLAI?
Details

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

bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps

The LRU and LRU_PERCPU maps allocate a new element on update before locking the target hash table bucket. Right after that the maps try to lock the bucket. If this fails, then maps return -EBUSY to the caller without releasing the allocated element. This makes the element untracked: it doesn't belong to either of free lists, and it doesn't belong to the hash table, so can't be re-used; this eventually leads to the permanent -ENOMEM on LRU map updates, which is unexpected. Fix this by returning the element to the local free list if bucket locking fails.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-54033"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-24T11:15:56Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: fix a memory leak in the LRU and LRU_PERCPU hash maps\n\nThe LRU and LRU_PERCPU maps allocate a new element on update before locking the\ntarget hash table bucket. Right after that the maps try to lock the bucket.\nIf this fails, then maps return -EBUSY to the caller without releasing the\nallocated element. This makes the element untracked: it doesn\u0027t belong to\neither of free lists, and it doesn\u0027t belong to the hash table, so can\u0027t be\nre-used; this eventually leads to the permanent -ENOMEM on LRU map updates,\nwhich is unexpected. Fix this by returning the element to the local free list\nif bucket locking fails.",
  "id": "GHSA-hcpj-xwwg-jgh9",
  "modified": "2025-12-24T12:30:28Z",
  "published": "2025-12-24T12:30:28Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-54033"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1a9e80f757bbb1562d82e350afce2bb2f712cc3d"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/79ea1a12fb9a8275b6e19d4ca625dd872dedcbb9"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/965e9cccbe6b9c7b379908cebcb5e3a47f20dd5e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b34ffb0c6d23583830f9327864b9c1f486003305"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

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…