Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-53361af_unix: Set gc_in_progress to true in unix_gc().

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

Timeline

  1. ID reserved

    By Linux

  2. · 25 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53361, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVDNVD · Modified3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS (exploitation in 30 days)
0.26% · top 82% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected ceb8bd6c69c1680fd9b45e7f16d7170c9c7513a5 – < 20aa894d475bd8086b25c1113ec4ca70f70c7a98
    • affected 328840c93bd6a4871dd10908d01b41eab83eb8e2 – < 82c17e13d404f686e164590483fd6c1abaa675d0
    • affected 8b90a9f819dc2a06baae4ec1a64d875e53b824ec – < 591f1ac217428a6d2b32a8ac14aac0fab44f155a
    • affected 8b90a9f819dc2a06baae4ec1a64d875e53b824ec – < 0cfa78c050662784fc8e3ab26dbfd1dc632b2082
    • affected 8b90a9f819dc2a06baae4ec1a64d875e53b824ec – < d82ba05263c69fa2437fe93e4e561cc40f4c03af
    • affected 6.1.141 – < 6.1.183
    • affected 6.6.93 – < 6.6.144
  • Linux · Linux

    • affected 6.9
    • unaffected < 6.9
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.144 – ≤ 6.6.*
    • unaffected 6.12.95 – ≤ 6.12.*
    • unaffected 6.18.38 – ≤ 6.18.*
    • unaffected 7.1 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53361 badge
[![CVE-2026-53361](https://cveledger.app/badge/CVE-2026-53361.svg)](https://cveledger.app/cve/CVE-2026-53361)

Record last updated .