CVE-2026-53361
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 versions
Linux kernel versions
6.6.93,
6.1.141,
6.9
and later are affected. Fixed in
6.6.144,
6.12.95,
6.18.38,
7.1
and their respective stable series.
References
4 totalFrequently asked questions
-
What is CVE-2026-53361?
CVE-2026-53361 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.6.93 onward and has been patched in 6.6.144, 6.12.95, 6.18.38 and others. CVE-2026-53361 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-53361?
Yes — CVE-2026-53361 has been patched. Fixed versions include 6.6.144, 6.12.95, 6.18.38 and others. If you are running Linux kernel 6.6.93 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-53361 actively exploited?
No — CVE-2026-53361 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.