← Back to CVE intelligence
CVE intelligence

CVE-2026-53361

Vulnerability intelligence

Published Jul 4, 2026Sources checked Oct 28, 2026
7.1HIGHCVSS out of 10
What this means

Review the available evidence

CVE-2026-53361 and is rated High severity with a CVSS score of 7.1. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Ubuntu Security Notices guidance

Vendor revision: Sep 22, 2026

This update corrects flaws in the following subsystems: - Character device driver; - Networking core; - IPv6 networking; - Unix domain sockets; (CVE-2026-52938, CVE-2026-53325, CVE-2026-53361, CVE-2026-53362)

Microsoft Security Response Center guidance

Vendor revision: Jul 8, 2026

CBL-Mariner Releases

Vendor-listed releases

  • 6.6.144.1-1
CISA KEVNot listedBased on the latest collected catalog
EPSS0.2%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors0Source-linked actor relationships
Overview

What is CVE-2026-53361?

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().

Source: NVD