Answer in brief
CVE-2026-53361 records a Unknown severity vulnerability in af_unix: Set gc_in_progress to true in unix_gc().. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=328840c93bd6a4871dd10908d01b41eab83eb8e2 <82c17e13d404f686e164590483fd6c1abaa675d0 || >=8b90a9f819dc2a06baae4ec1a64d875e53b824ec <591f1ac217428a6d2b32a8ac14aac0fab44f155a || >=8b90a9f819dc2a06baae4ec1a64d875e53b824ec <0cfa78c050662784fc8e3ab26dbfd1dc632b2082 || >=8b90a9f819dc2a06baae4ec1a64d875e53b824ec <d82ba05263c69fa2437fe93e4e561cc40f4c03af || ceb8bd6c69c1680fd9b45e7f16d7170c9c7513a5 || >=6.6.93 <6.6.144 || >=6.1.141 <6.2 | 82c17e13d404f686e164590483fd6c1abaa675d0, 591f1ac217428a6d2b32a8ac14aac0fab44f155a, 0cfa78c050662784fc8e3ab26dbfd1dc632b2082, d82ba05263c69fa2437fe93e4e561cc40f4c03af, 6.6.144, 6.2 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Jul 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-53361 records a Unknown severity vulnerability in af_unix: Set gc_in_progress to true in unix_gc().. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=328840c93bd6a4871dd10908d01b41eab83eb8e2 <82c17e13d404f686e164590483fd6c1abaa675d0 || >=8b90a9f819dc2a06baae4ec1a64d875e53b824ec <591f1ac217428a6d2b32a8ac14aac0fab44f155a || >=8b90a9f819dc2a06baae4ec1a64d875e53b824ec <0cfa78c050662784fc8e3ab26dbfd1dc632b2082 || >=8b90a9f819dc2a06baae4ec1a64d875e53b824ec <d82ba05263c69fa2437fe93e4e561cc40f4c03af || ceb8bd6c69c1680fd9b45e7f16d7170c9c7513a5 || >=6.6.93 <6.6.144 || >=6.1.141 <6.2 | 82c17e13d404f686e164590483fd6c1abaa675d0, 591f1ac217428a6d2b32a8ac14aac0fab44f155a, 0cfa78c050662784fc8e3ab26dbfd1dc632b2082, d82ba05263c69fa2437fe93e4e561cc40f4c03af, 6.6.144, 6.2 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Jul 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.