Bug 1225200 (CVE-2021-47377) - VUL-0: REJECTED: CVE-2021-47377: kernel: xen/balloon: use a kernel thread instead a workqueue
Summary: VUL-0: REJECTED: CVE-2021-47377: kernel: xen/balloon: use a kernel thread ins...
Status: RESOLVED INVALID
Alias: CVE-2021-47377
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/407016/
Whiteboard: CVSSv3.1:SUSE:CVE-2021-47377:3.3:(AV:...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-24 09:43 UTC by SMASH SMASH
Modified: 2024-05-29 09:32 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-05-24 09:43:28 UTC
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.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-47377
https://www.cve.org/CVERecord?id=CVE-2021-47377
https://git.kernel.org/stable/c/29917bbb07c30be295dece245c7c21872e1a6fbb
https://git.kernel.org/stable/c/372d3e6ea1e115942fdfb4b25f7003d822d071be
https://git.kernel.org/stable/c/6bba79c6a073741b672b0bf86a1f03c0fe47f973
https://git.kernel.org/stable/c/8480ed9c2bbd56fc86524998e5f2e3e22f5038f6
https://git.kernel.org/stable/c/922fd5b6bb13ad31ff36e86e2eba2f26d8135272
https://git.kernel.org/stable/c/c5d5a43dd2b649a0a290bfed00fb76d1aff89be6
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2021/CVE-2021-47377.mbox
https://bugzilla.redhat.com/show_bug.cgi?id=2282363
Comment 3 Jürgen Groß 2024-05-27 08:42:03 UTC
This is no security relevant issue.

The BUG() can happen only in a guest not having this fix. It can't be triggered by an unprivileged user.

I will dispute the CVE.
Comment 4 Jürgen Groß 2024-05-29 06:04:03 UTC
CVE has been revoked now.
Comment 5 Andrea Mattiazzo 2024-05-29 09:32:48 UTC
Closing as CVE is now rejected: https://lore.kernel.org/linux-cve-announce/2024052823-REJECTED-cc32@gregkh/