GHSA-WFJG-CRVW-F25H

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

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

debugobjects: Don't wake up kswapd from fill_pool()

syzbot is reporting a lockdep warning in fill_pool() because the allocation from debugobjects is using GFP_ATOMIC, which is (__GFP_HIGH | __GFP_KSWAPD_RECLAIM) and therefore tries to wake up kswapd, which acquires kswapd_wait::lock.

Since fill_pool() might be called with arbitrary locks held, fill_pool() should not assume that acquiring kswapd_wait::lock is safe.

Use __GFP_HIGH instead and remove __GFP_NORETRY as it is pointless for !__GFP_DIRECT_RECLAIM allocation.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2023-54268"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-30T13:16:15Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndebugobjects: Don\u0027t wake up kswapd from fill_pool()\n\nsyzbot is reporting a lockdep warning in fill_pool() because the allocation\nfrom debugobjects is using GFP_ATOMIC, which is (__GFP_HIGH | __GFP_KSWAPD_RECLAIM)\nand therefore tries to wake up kswapd, which acquires kswapd_wait::lock.\n\nSince fill_pool() might be called with arbitrary locks held, fill_pool()\nshould not assume that acquiring kswapd_wait::lock is safe.\n\nUse __GFP_HIGH instead and remove __GFP_NORETRY as it is pointless for\n!__GFP_DIRECT_RECLAIM allocation.",
  "id": "GHSA-wfjg-crvw-f25h",
  "modified": "2025-12-30T15:30:34Z",
  "published": "2025-12-30T15:30:34Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-54268"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4c088d30a72d9b8f9c6ae9362222942e4075cb00"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/aee97eec77029270866c704f66cdf2881cbd2fe1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/be646802b3dc408c4dc72a3ac32c3f4a0282414d"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d7fff52c99d52f180d8bef95d8ed8fec6343889c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/eb799279fb1f9c63c520fe8c1c41cb9154252db6"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/fd673079749bac97bb30f1461df079e6c8e86511"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.



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.