CVE-2026-53361

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-04. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this weekElevated
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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
7.1
EG Score
7.1(medium)
EG Risk
52(Track)
EG Risk 52/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

July 4, 2026

Last Modified

August 19, 2026

Advisory Details (4)

Auto-updated Jul 18, 2026
No patch confirmed yet.
generic

af_unix: Set gc_in_progress to true in unix_gc(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d82ba05263c69fa2437fe93e4e561cc40f4c03af
generic

af_unix: Set gc_in_progress to true in unix_gc(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0cfa78c050662784fc8e3ab26dbfd1dc632b2082
generic

af_unix: Set gc_in_progress to true in unix_gc(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/591f1ac217428a6d2b32a8ac14aac0fab44f155a
generic

af_unix: Set gc_in_progress to true in unix_gc(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/82c17e13d404f686e164590483fd6c1abaa675d0

Vendor Advisories for CVE-2026-53361(3)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-09-18ubuntu
redhatkernel-0:6.12.0-211.55.1.el10_22026-09-15redhat
redhatkernel-0:6.12.0-55.102.1.el10_02026-09-02redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)6.1.187-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.3-1—

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 16× in last 7d / 74× 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.

Showing the most recent 100 of 377 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 06:10 UTCEG score recompute
  3. 2026-09-18 06:10 UTCVendor advisory
  4. 2026-09-18 06:10 UTCGHSA enrichment
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-13 23:59 UTCEG score recompute
  8. 2026-09-13 23:59 UTCVendor advisory
  9. 2026-09-13 23:59 UTCGHSA enrichment
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-13 08:51 UTCEG score recompute
  12. 2026-09-13 08:51 UTCVendor advisory
  13. 2026-09-13 08:51 UTCGHSA enrichment
  14. 2026-09-12 13:46 UTCEG score recompute
  15. 2026-09-12 13:46 UTCVendor advisory
  16. 2026-09-12 13:46 UTCGHSA enrichment
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-10 09:35 UTCEPSS rescore
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 16:01 UTCEPSS rescore
  21. 2026-09-06 14:15 UTCEG score recompute
  22. 2026-09-06 14:15 UTCVendor advisory
  23. 2026-09-06 14:15 UTCGHSA enrichment
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-05 23:35 UTCEG score recompute
Show 75 more
  1. 2026-09-05 23:35 UTCVendor advisory
  2. 2026-09-05 23:35 UTCGHSA enrichment
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-08-31 00:27 UTCEG score recompute
  8. 2026-08-31 00:27 UTCVendor advisory
  9. 2026-08-31 00:27 UTCGHSA enrichment
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 11:14 UTCEG score recompute
  12. 2026-08-30 11:14 UTCVendor advisory
  13. 2026-08-30 11:14 UTCGHSA enrichment
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 22:09 UTCEG score recompute
  17. 2026-08-27 22:09 UTCVendor advisory
  18. 2026-08-27 22:09 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-27 03:12 UTCVendor advisory
  21. 2026-08-27 03:12 UTCGHSA enrichment
  22. 2026-08-26 13:59 UTCEG score recompute
  23. 2026-08-26 13:59 UTCVendor advisory
  24. 2026-08-26 13:59 UTCGHSA enrichment
  25. 2026-08-25 13:49 UTCEPSS rescore
  26. 2026-08-25 12:12 UTCVendor advisory
  27. 2026-08-25 12:12 UTCGHSA enrichment
  28. 2026-08-24 20:50 UTCEG score recompute
  29. 2026-08-24 20:50 UTCVendor advisory
  30. 2026-08-24 20:50 UTCGHSA enrichment
  31. 2026-08-24 04:27 UTCVendor advisory
  32. 2026-08-24 04:27 UTCGHSA enrichment
  33. 2026-08-23 15:13 UTCVendor advisory
  34. 2026-08-23 15:13 UTCGHSA enrichment
  35. 2026-08-23 02:01 UTCEG score recompute
  36. 2026-08-23 02:01 UTCVendor advisory
  37. 2026-08-23 02:01 UTCGHSA enrichment
  38. 2026-08-23 00:19 UTCEPSS rescore
  39. 2026-08-22 12:24 UTCEG score recompute
  40. 2026-08-22 12:24 UTCVendor advisory
  41. 2026-08-22 12:24 UTCGHSA enrichment
  42. 2026-08-21 23:49 UTCEPSS rescore
  43. 2026-08-21 22:40 UTCGHSA enrichment
  44. 2026-08-21 09:28 UTCEG score recompute
  45. 2026-08-21 09:28 UTCVendor advisory
  46. 2026-08-21 09:28 UTCGHSA enrichment
  47. 2026-08-20 22:55 UTCEPSS rescore
  48. 2026-08-20 20:15 UTCVendor advisory
  49. 2026-08-20 20:15 UTCGHSA enrichment
  50. 2026-08-20 07:02 UTCVendor advisory
  51. 2026-08-20 07:02 UTCGHSA enrichment
  52. 2026-08-19 17:50 UTCEG score recompute
  53. 2026-08-19 17:50 UTCVendor advisory
  54. 2026-08-19 17:50 UTCGHSA enrichment
  55. 2026-08-19 17:13 UTCEG score recompute
  56. 2026-08-19 17:13 UTCVendor advisory
  57. 2026-08-19 17:13 UTCGHSA enrichment
  58. 2026-08-19 17:04 UTCEPSS rescore
  59. 2026-08-19 10:17 UTCVendor advisory
  60. 2026-08-19 10:17 UTCGHSA enrichment
  61. 2026-08-18 20:50 UTCEG score recompute
  62. 2026-08-18 20:50 UTCVendor advisory
  63. 2026-08-18 20:50 UTCGHSA enrichment
  64. 2026-08-18 13:48 UTCEPSS rescore
  65. 2026-08-18 06:18 UTCGHSA enrichment
  66. 2026-08-17 16:49 UTCEG score recompute
  67. 2026-08-17 16:49 UTCVendor advisory
  68. 2026-08-17 16:49 UTCGHSA enrichment
  69. 2026-08-17 13:47 UTCEPSS rescore
  70. 2026-08-17 03:02 UTCEG score recompute
  71. 2026-08-17 03:02 UTCVendor advisory
  72. 2026-08-17 03:02 UTCGHSA enrichment
  73. 2026-08-16 14:56 UTCEPSS rescore
  74. 2026-08-16 13:49 UTCEG score recompute
  75. 2026-08-16 13:49 UTCVendor advisory

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCsgkdev/bad_garbage
    First seen Aug 10, 2026

    CVE-2026-53361 AF_UNIX GC vs MSG_PEEK use-after-free container escape

    Open source ↗

Frequently asked(5)

What is CVE-2026-53361?
CVE-2026-53361 is a high 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, with the most recent update on August 19, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 90.7% of all scored CVEs.
What is the CVSS score of CVE-2026-53361?
CVE-2026-53361 has a CVSS v3 base score of 7.1 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by 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