{
  "id": "CVE-2026-74481",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-74481",
  "published_at": "2026-08-15T12:27:14.441Z",
  "title": "mm/page_reporting: use system_freezable_wq to fix UAF during suspend",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 7.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_reporting: use system_freezable_wq to fix UAF during suspend\n\nDuring PM freeze (e.g.  S3 suspend or S4 hibernation), device drivers like\nvirtio_balloon reset their underlying virtio devices and delete their\nvirtqueues via vdev-\u003econfig-\u003edel_vqs().\n\nHowever, page reporting work (page_reporting_process) was scheduled on the\nglobal system_wq.  Because system_wq lacks the WQ_FREEZABLE flag, the PM\nfreezer skips it, leaving page_reporting_process active during suspend.\n\nIf pages are freed into the buddy allocator while suspending (for example,\nwhen core MM invokes the balloon shrinker during S4 hibernation image\nsaving), page reporting triggers virtballoon_free_page_report() on deleted\nvirtqueues, resulting in a Use-After-Free / General Protection Fault:\n\n    [  196.795226] general protection fault, probably for non-canonical address 0xaa1436fe70dae6df: 0000 [#1] SMP NOPTI\n    [  196.825967] Workqueue: events page_reporting_process\n    [  196.831038] RIP: 0010:virtqueue_add_split+0x233/0x4c0 [virtio_ring]\n    [  196.927073] virtballoon_free_page_report+0x3a/0xe0 [virtio_balloon]\n    [  196.946943] page_reporting_process+0x370/0x4f0\n\nFix this by switching page reporting work to system_freezable_wq.  This\nensures that the PM freezer pauses page_reporting_process before device\ndrivers destroy their reporting virtqueues.  Because the reporting worker\nis frozen, memory reclamation/freeing (e.g.  via shrinker execution) can\nsafely return pages to MM during freeze without triggering unfrozen\nreporting work on deleted virtqueues.\n\nThis aligns with the driver's existing design. The comment in\nvirtballoon_freeze() states:\n    /*\n     * The workqueue is already frozen by the PM core before this\n     * function is called.\n     */\n\nTesting:\nI have verified these fixes using Google’s virtualization infrastructure\nby running continuous suspend/resume iterations (40+ cycles) while\nchurning memory using stress-ng (`stress-ng --vm 4 --vm-bytes 60%\n--timeout 1`) to constantly create free pages for the buddy allocator.  We\nalso set the `page_reporting_order` parameter to 0 to make the page\nreporting worker highly sensitive, forcing it to pick up any 4K free\npages.  This confirmed that the UAF crashes are no longer reproducible.",
  "cvss_by_source": {
    "cna": 7.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= 36e66c554b5c6a9d17a229faca7a61693527b0bd, \u003c a4c60046052777ca1dcc83fe3ece2a5136b301f1",
          "\u003e= 36e66c554b5c6a9d17a229faca7a61693527b0bd, \u003c b2c094e98f8bb823b3ae475f7169fe2091c40c6d",
          "\u003e= 36e66c554b5c6a9d17a229faca7a61693527b0bd, \u003c 992f270fd808338fbae1f498a5e325e7e2e20368",
          "\u003e= 36e66c554b5c6a9d17a229faca7a61693527b0bd, \u003c f978048326570047e8216e81a67f9c71ef2bb1b1",
          "\u003e= 36e66c554b5c6a9d17a229faca7a61693527b0bd, \u003c 450f35f4d5a682a0796757e52295df58ddb63bc9",
          "\u003e= 36e66c554b5c6a9d17a229faca7a61693527b0bd, \u003c b11907c905fa08eda925395f0724b7a409870f65",
          "\u003e= 36e66c554b5c6a9d17a229faca7a61693527b0bd, \u003c faf439b5fa7b231120eac4f7a617e0bfd4f6f5c7",
          "\u003e= 36e66c554b5c6a9d17a229faca7a61693527b0bd, \u003c 0b45f6927a14914ff685fe0e6f9d11232a1e03df"
        ],
        "fixed_in": [
          "a4c60046052777ca1dcc83fe3ece2a5136b301f1",
          "b2c094e98f8bb823b3ae475f7169fe2091c40c6d",
          "992f270fd808338fbae1f498a5e325e7e2e20368",
          "f978048326570047e8216e81a67f9c71ef2bb1b1",
          "450f35f4d5a682a0796757e52295df58ddb63bc9",
          "b11907c905fa08eda925395f0724b7a409870f65",
          "faf439b5fa7b231120eac4f7a617e0bfd4f6f5c7",
          "0b45f6927a14914ff685fe0e6f9d11232a1e03df"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "5.7"
        ],
        "fixed_in": [
          "0",
          "5.10.265",
          "5.15.216",
          "6.1.183",
          "6.6.151",
          "6.12.103",
          "6.18.44",
          "7.1.8",
          "7.2"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to a4c60046052777ca1dcc83fe3ece2a5136b301f1 or b2c094e98f8bb823b3ae475f7169fe2091c40c6d or 992f270fd808338fbae1f498a5e325e7e2e20368 or f978048326570047e8216e81a67f9c71ef2bb1b1 or 450f35f4d5a682a0796757e52295df58ddb63bc9 or b11907c905fa08eda925395f0724b7a409870f65 or faf439b5fa7b231120eac4f7a617e0bfd4f6f5c7 or 0b45f6927a14914ff685fe0e6f9d11232a1e03df or later.",
      "Upgrade Linux to 0 or 5.10.265 or 5.15.216 or 6.1.183 or 6.6.151 or 6.12.103 or 6.18.44 or 7.1.8 or 7.2 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
