CVE-2026-53361
af_unix: Set gc_in_progress to true in unix_gc().
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().
- Affected
- Linux
- CVSS v3.1 CNA
- 7.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H - EPSS
- 0.23% chance of exploitation in the next 30 days, 13th percentile
- Published
- 2026-07-04
- Updated
- 2026-10-16
Proof-of-concept exploits (1)
- sgkdev/bad_garbage26★ · 2026-08-11
Exploit collections (1)
- linux/kernelctf/CVE-2026-53361_ltsgoogle/security-research
Security advisories
- https://git.kernel.org/stable/c/0cfa78c050662784fc8e3ab26dbfd1dc632b2082
- https://git.kernel.org/stable/c/591f1ac217428a6d2b32a8ac14aac0fab44f155a
- https://git.kernel.org/stable/c/82c17e13d404f686e164590483fd6c1abaa675d0
- https://git.kernel.org/stable/c/d82ba05263c69fa2437fe93e4e561cc40f4c03af