Fedora Account System
Red Hat Associate
Red Hat Customer
In the Linux kernel, the following vulnerability has been resolved: af_unix: Set gc_in_progress to true in unix_gc(). Igor Ushakov reported that unix_gc() could run with gc_in_progress being false if the work is scheduled while running: Thread 1 Thread 2 Thread 3 -------- -------- -------- unix_schedule_gc() unix_schedule_gc() `- if (!gc_in_progress) `- if (!gc_in_progress) |- gc_in_progress = true | `- queue_work() | unix_gc() <----------------/ | | |- gc_in_progress = true ... `- queue_work() | | `- gc_in_progress = false | | unix_gc() <---------------------------------------------' | ... /* gc_in_progress == false */ | `- gc_in_progress = false unix_peek_fpl() relies on gc_in_progress not to confuse GC by MSG_PEEK. Let's set gc_in_progress to true in unix_gc().
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2026070436-CVE-2026-53361-f969@gregkh/T
FYI: A public container escape exploit for CVE-2026-53361 ("bad_garbage") was released on Aug 11. It explicitly targets RHEL/AlmaLinux 10.2 (kernel-6.12.0-211.43.1.el10_2) and CentOS Stream 10, including RHEL-specific offsets and SELinux bypasses. Given that AlmaLinux published kernel-6.12.0-211.43.1.el10_2 just yesterday—the exact kernel targeted by the exploit—could someone confirm if the current release is affected and if a backport fix is planned? Patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=82c17e13d404f686e164590483fd6c1abaa675d0 Public exploit: https://github.com/sgkdev/bad_garbage Writeup: https://www.linkedin.com/pulse/badgarbagec-afunix-container-escape-resurrected-twice-oldani-sicvf/
Correction: The patch link in my previous comment was for the Linux 6.6.y stable branch. For the Linux 6.12.y stable branch, the corresponding fix is: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=591f1ac217428a6d2b32a8ac14aac0fab44f155a This fix was included in Linux 6.12.95. Sorry for the confusion.
This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2026:62609 https://access.redhat.com/errata/RHSA-2026:62609
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:67471 https://access.redhat.com/errata/RHSA-2026:67471