CVEvulnerability
CVE-2026-53361
7.1 HIGH
Official page ↗
- Status
- Modified
- Published
- 2026-07-04
- Last modified
- 2026-10-19
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.1 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
- Weaknesses
- CWE-362
Description
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 configurations
• linux linux kernel (>= 6.1.141 < 6.2)
• linux linux kernel (>= 6.6.93 < 6.6.144)
• linux linux kernel (>= 6.9 < 6.12.95)
• linux linux kernel (>= 6.13 < 6.18.38)
• linux linux kernel (>= 6.19 < 7.1)
• linux linux kernel 7.1
Related
Weakness · CWE (1)
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization weakness
References
- https://git.kernel.org/stable/c/0cfa78c050662784fc8e3ab26dbfd1dc632b2082 Patch
- https://git.kernel.org/stable/c/20aa894d475bd8086b25c1113ec4ca70f70c7a98 git.kernel.org
- https://git.kernel.org/stable/c/591f1ac217428a6d2b32a8ac14aac0fab44f155a Patch
- https://git.kernel.org/stable/c/82c17e13d404f686e164590483fd6c1abaa675d0 Patch
- https://git.kernel.org/stable/c/d82ba05263c69fa2437fe93e4e561cc40f4c03af Patch