Linux
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= ceb8bd6c69c1680fd9b45e7f16d7170c9c7513a5, < 20aa894d475bd8086b25c1113ec4ca70f70c7a98
- >= 328840c93bd6a4871dd10908d01b41eab83eb8e2, < 82c17e13d404f686e164590483fd6c1abaa675d0
- >= 8b90a9f819dc2a06baae4ec1a64d875e53b824ec, < 591f1ac217428a6d2b32a8ac14aac0fab44f155a
- >= 8b90a9f819dc2a06baae4ec1a64d875e53b824ec, < 0cfa78c050662784fc8e3ab26dbfd1dc632b2082
- >= 8b90a9f819dc2a06baae4ec1a64d875e53b824ec, < d82ba05263c69fa2437fe93e4e561cc40f4c03af
- >= 6.1.141, < 6.1.183
- >= 6.6.93, < 6.6.144
Fixed in 20aa894d475bd8086b25c1113ec4ca70f70c7a98, 82c17e13d404f686e164590483fd6c1abaa675d0, 591f1ac217428a6d2b32a8ac14aac0fab44f155a, 0cfa78c050662784fc8e3ab26dbfd1dc632b2082, d82ba05263c69fa2437fe93e4e561cc40f4c03af, 6.1.183, 6.6.144
- 6.9
Fixed in 0, 6.1.183, 6.6.144, 6.12.95, 6.18.38, 7.1
Mitigation
Upgrade Linux to 20aa894d475bd8086b25c1113ec4ca70f70c7a98 or 82c17e13d404f686e164590483fd6c1abaa675d0 or 591f1ac217428a6d2b32a8ac14aac0fab44f155a or 0cfa78c050662784fc8e3ab26dbfd1dc632b2082 or d82ba05263c69fa2437fe93e4e561cc40f4c03af or 6.1.183 or 6.6.144 or later.
Upgrade Linux to 0 or 6.1.183 or 6.6.144 or 6.12.95 or 6.18.38 or 7.1 or later.
Timeline
Days relative to CVE publicationFirst public PoC 37 days after publication; not in CISA KEV. First PoC: sgkdev/bad_garbage (created 10 Aug 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| sgkdev/bad_garbage | 10 Aug 2026 +37 d | 28 | PoC via PoC Index |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.