Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-74481

mm/page_reporting: use system_freezable_wq to fix UAF during suspend

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, and 2 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

In the Linux kernel, the following vulnerability has been resolved: mm/page_reporting: use system_freezable_wq to fix UAF during suspend During PM freeze (e.g. S3 suspend or S4 hibernation), device drivers like virtio_balloon reset their underlying virtio devices and delete their virtqueues via vdev->config->del_vqs(). However, page reporting work (page_reporting_process) was scheduled on the global system_wq. Because system_wq lacks the WQ_FREEZABLE flag, the PM freezer skips it, leaving page_reporting_process active during suspend. If pages are freed into the buddy allocator while suspending (for example, when core MM invokes the balloon shrinker during S4 hibernation image saving), page reporting triggers virtballoon_free_page_report() on deleted virtqueues, resulting in a Use-After-Free / General Protection Fault: [ 196.795226] general protection fault, probably for non-canonical address 0xaa1436fe70dae6df: 0000 [#1] SMP NOPTI [ 196.825967] Workqueue: events page_reporting_process [ 196.831038] RIP: 0010:virtqueue_add_split+0x233/0x4c0 [virtio_ring] [ 196.927073] virtballoon_free_page_report+0x3a/0xe0 [virtio_balloon] [ 196.946943] page_reporting_process+0x370/0x4f0 Fix this by switching page reporting work to system_freezable_wq. This ensures that the PM freezer pauses page_reporting_process before device drivers destroy their reporting virtqueues. Because the reporting worker is frozen, memory reclamation/freeing (e.g. via shrinker execution) can safely return pages to MM during freeze without triggering unfrozen reporting work on deleted virtqueues. This aligns with the driver's existing design. The comment in virtballoon_freeze() states: /* • The workqueue is already frozen by the PM core before this • function is called. */ Testing: I have verified these fixes using Google’s virtualization infrastructure by running continuous suspend/resume iterations (40+ cycles) while churning memory using stress-ng (`stress-ng --vm 4 --vm-bytes 60% --timeout 1`) to constantly create free pages for the buddy allocator. We also set the `page_reporting_order` parameter to 0 to make the page reporting worker highly sensitive, forcing it to pick up any 4K free pages. This confirmed that the UAF crashes are no longer reproducible.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  3. Record last updated

Affected versions

  • Linux Linux

    From 36e66c554b5c6a9d17a229faca7a61693527b0bd · fixed in a4c60046052777ca1dcc83fe3ece2a5136b301f1; From 36e66c554b5c6a9d17a229faca7a61693527b0bd · fixed in b2c094e98f8bb823b3ae475f7169fe2091c40c6d; From 36e66c554b5c6a9d17a229faca7a61693527b0bd · fixed in 992f270fd808338fbae1f498a5e325e7e2e20368; From 36e66c554b5c6a9d17a229faca7a61693527b0bd · fixed in f978048326570047e8216e81a67f9c71ef2bb1b1; From 36e66c554b5c6a9d17a229faca7a61693527b0bd · fixed in 450f35f4d5a682a0796757e52295df58ddb63bc9; From 36e66c554b5c6a9d17a229faca7a61693527b0bd · fixed in b11907c905fa08eda925395f0724b7a409870f65; From 36e66c554b5c6a9d17a229faca7a61693527b0bd · fixed in faf439b5fa7b231120eac4f7a617e0bfd4f6f5c7; From 36e66c554b5c6a9d17a229faca7a61693527b0bd · fixed in 0b45f6927a14914ff685fe0e6f9d11232a1e03df

  • Linux Linux

    5.7

  • KernelLinux

    From 5.7.0 · fixed in 5.10.265; From 5.11.0 · fixed in 5.15.216; From 5.16.0 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.151; From 6.7.0 · fixed in 6.12.103; From 6.13.0 · fixed in 6.18.44; From 6.19.0 · fixed in 7.1.8

References 8

git.kernel.org