GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-XX23-73HR-9P64

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

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

ALSA: pcm: Fix potential data race at PCM memory allocation helpers

The PCM memory allocation helpers have a sanity check against too many buffer allocations. However, the check is performed without a proper lock and the allocation isn't serialized; this allows user to allocate more memories than predefined max size.

Practically seen, this isn't really a big problem, as it's more or less some "soft limit" as a sanity check, and it's not possible to allocate unlimitedly. But it's still better to address this for more consistent behavior.

The patch covers the size check in do_alloc_pages() with the card->memory_mutex, and increases the allocated size there for preventing the further overflow. When the actual allocation fails, the size is decreased accordingly.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-54072"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-24T13:16:09Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: pcm: Fix potential data race at PCM memory allocation helpers\n\nThe PCM memory allocation helpers have a sanity check against too many\nbuffer allocations.  However, the check is performed without a proper\nlock and the allocation isn\u0027t serialized; this allows user to allocate\nmore memories than predefined max size.\n\nPractically seen, this isn\u0027t really a big problem, as it\u0027s more or\nless some \"soft limit\" as a sanity check, and it\u0027s not possible to\nallocate unlimitedly.  But it\u0027s still better to address this for more\nconsistent behavior.\n\nThe patch covers the size check in do_alloc_pages() with the\ncard-\u003ememory_mutex, and increases the allocated size there for\npreventing the further overflow.  When the actual allocation fails,\nthe size is decreased accordingly.",
  "id": "GHSA-xx23-73hr-9p64",
  "modified": "2025-12-24T15:30:36Z",
  "published": "2025-12-24T15:30:36Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-54072"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3eb4e47a94e3f76521d7d344696db61e6a9619c7"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/773ccad902f67583a58b5650a2f8d8daf2e76fac"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7e11c58b2620a22c67a5ae28d64ce383890ee9f4"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7e1d1456c8db9949459c5a24e8845cfe92430b0f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a0ab49e7a758b488b2090171a75d50735c0876f6"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/bd55842ed998a622ba6611fe59b3358c9f76773d"
    }
  ],
  "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…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…