ghsa-7rxq-5vw3-rhvg
Vulnerability from github
Published
2024-05-21 15:31
Modified
2024-05-21 15:31
Details

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

xen/balloon: use a kernel thread instead a workqueue

Today the Xen ballooning is done via delayed work in a workqueue. This might result in workqueue hangups being reported in case of large amounts of memory are being ballooned in one go (here 16GB):

BUG: workqueue lockup - pool cpus=6 node=0 flags=0x0 nice=0 stuck for 64s! Showing busy workqueues and worker pools: workqueue events: flags=0x0 pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=2/256 refcnt=3 in-flight: 229:balloon_process pending: cache_reap workqueue events_freezable_power_: flags=0x84 pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 pending: disk_events_workfn workqueue mm_percpu_wq: flags=0x8 pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 pending: vmstat_update pool 12: cpus=6 node=0 flags=0x0 nice=0 hung=64s workers=3 idle: 2222 43

This can easily be avoided by using a dedicated kernel thread for doing the ballooning work.

Show details on source website


{
  "affected": [],
  "aliases": [
    "CVE-2021-47377"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-05-21T15:15:23Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nxen/balloon: use a kernel thread instead a workqueue\n\nToday the Xen ballooning is done via delayed work in a workqueue. This\nmight result in workqueue hangups being reported in case of large\namounts of memory are being ballooned in one go (here 16GB):\n\nBUG: workqueue lockup - pool cpus=6 node=0 flags=0x0 nice=0 stuck for 64s!\nShowing busy workqueues and worker pools:\nworkqueue events: flags=0x0\n  pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=2/256 refcnt=3\n    in-flight: 229:balloon_process\n    pending: cache_reap\nworkqueue events_freezable_power_: flags=0x84\n  pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=1/256 refcnt=2\n    pending: disk_events_workfn\nworkqueue mm_percpu_wq: flags=0x8\n  pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=1/256 refcnt=2\n    pending: vmstat_update\npool 12: cpus=6 node=0 flags=0x0 nice=0 hung=64s workers=3 idle: 2222 43\n\nThis can easily be avoided by using a dedicated kernel thread for doing\nthe ballooning work.",
  "id": "GHSA-7rxq-5vw3-rhvg",
  "modified": "2024-05-21T15:31:44Z",
  "published": "2024-05-21T15:31:44Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-47377"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/29917bbb07c30be295dece245c7c21872e1a6fbb"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/372d3e6ea1e115942fdfb4b25f7003d822d071be"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/6bba79c6a073741b672b0bf86a1f03c0fe47f973"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8480ed9c2bbd56fc86524998e5f2e3e22f5038f6"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/922fd5b6bb13ad31ff36e86e2eba2f26d8135272"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c5d5a43dd2b649a0a290bfed00fb76d1aff89be6"
    }
  ],
  "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 seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.