CVE-2026-53361

NONECVSS 0.0Trending — 4 sources updated this week
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
—
EG Score
0.0(none)
EPSS
6.8%
KEV
Not listed

Published

July 4, 2026

Last Modified

July 4, 2026

References (4)

Vendor Advisories for CVE-2026-53361(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-04 12:27 UTCNVD update
  6. 2026-07-04 12:17 UTCEG score recompute
  7. 2026-07-04 12:16 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-53361?
CVE-2026-53361 is a none vulnerability published on July 4, 2026. In the Linux kernel, the following vulnerability has been resolved: afunix: Set gcinprogress to true in unixgc(). Igor Ushakov reported that unixgc() could run with gcin_progress being false if the work is scheduled while running: Thread 1 Thread 2 Thread 3 -------- -------- --------…
When was CVE-2026-53361 disclosed?
CVE-2026-53361 was first published in the National Vulnerability Database on July 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53361 actively exploited?
CVE-2026-53361 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2026-53361?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53361, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53361

Explore →

Is Your Infrastructure Affected by CVE-2026-53361?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs