CVE-2026-53361
In the Linux kernel, the following vulnerability has been resolved: …
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().
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/0cfa78c050662784fc8e3ab26dbfd1dc632b2082
- git.kernel.org/stable/c/591f1ac217428a6d2b32a8ac14aac0fab44f155a
- git.kernel.org/stable/c/82c17e13d404f686e164590483fd6c1abaa675d0
- git.kernel.org/stable/c/d82ba05263c69fa2437fe93e4e561cc40f4c03af
- git.kernel.org/stable/c/20aa894d475bd8086b25c1113ec4ca70f70c7a98
- nvd.nist.gov/vuln/detail/CVE-2026-53361
- cve.org/CVERecord?id=CVE-2026-53361
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.