Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 1 month, 3 weeks ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
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 products

Linux
  • <d82ba05263c69fa2437fe93e4e561cc40f4c03af
  • =<*
  • <0cfa78c050662784fc8e3ab26dbfd1dc632b2082
  • ==ceb8bd6c69c1680fd9b45e7f16d7170c9c7513a5
  • <6.9
  • <6.6.144
  • =<6.18.*
  • ==6.9
  • <591f1ac217428a6d2b32a8ac14aac0fab44f155a
  • =<6.6.*
  • <6.2
  • =<6.12.*
  • <82c17e13d404f686e164590483fd6c1abaa675d0