CVE-2026-53361
Last modified
CVE-2026-53361 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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() <---------------------------------------------' | ... EPSS estimates a 0.12% chance of exploitation in the next 30 days.
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().
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| 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 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53361?
How severe is CVE-2026-53361?
How do I fix CVE-2026-53361?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53355In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53356In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53357In the Linux kernel, the following vulnerability has been re…8
- CVE-2026-53358In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53359In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53360In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53362In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53363In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53364In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53365In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53366In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53367In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-53361?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST