CVE-2026-53361: af_unix: Set gc_in_progress to true in unix_gc().
Noroxi assessment
Priority: Monitor (action score 28/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0cfa78c050662784fc8e3ab26dbfd1dc632b2082, 20aa894d475bd8086b25c1113ec4ca70f70c7a98, 591f1ac217428a6d2b32a8ac14aac0fab44f155a; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.144.1-1.
Low priority for now. Upgrade to Linux Linux 0cfa78c050662784fc8e3ab26dbfd1dc632b2082, 20aa894d475bd8086b25c1113ec4ca70f70c7a98, 591f1ac217428a6d2b32a8ac14aac0fab44f155a; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.144.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Jul 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-362
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.1.141 and later · before 6.2
- linux linux kernel6.6.93 and later · before 6.6.144
- linux linux kernel6.9 and later · before 6.12.95
- linux linux kernel6.13 and later · before 6.18.38
- linux linux kernel6.19 and later · before 7.1
- linux linux kernel7.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.9affected
- ceb8bd6c69c1680fd9b45e7f16d7170c9c7513a5 and later · before 20aa894d475bd8086b25c1113ec4ca70f70c7a98affected · git
- 328840c93bd6a4871dd10908d01b41eab83eb8e2 and later · before 82c17e13d404f686e164590483fd6c1abaa675d0affected · git
- 8b90a9f819dc2a06baae4ec1a64d875e53b824ec and later · before 591f1ac217428a6d2b32a8ac14aac0fab44f155aaffected · git
- 8b90a9f819dc2a06baae4ec1a64d875e53b824ec and later · before 0cfa78c050662784fc8e3ab26dbfd1dc632b2082affected · git
- 8b90a9f819dc2a06baae4ec1a64d875e53b824ec and later · before d82ba05263c69fa2437fe93e4e561cc40f4c03afaffected · git
- 6.1.141 and later · before 6.1.183affected · semver
- 6.6.93 and later · before 6.6.144affected · semver
- before 6.9not affected · semver
- 6.1.183 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.55.1.el10_2 | 6.12.0-211.55.1.el10_2 |
| AlmaLinux:10 | kernel | before 6.12.0-211.47.1.el10_2 | 6.12.0-211.47.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.55.1.el10_2 | 6.12.0-211.55.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.47.1.el10_2 | 6.12.0-211.47.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.47.1.el10_2 | 6.12.0-211.47.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.55.1.el10_2 | 6.12.0-211.55.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.55.1.el10_2 | 6.12.0-211.55.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.47.1.el10_2 | 6.12.0-211.47.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.55.1.el10_2 | 6.12.0-211.55.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.47.1.el10_2 | 6.12.0-211.47.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.47.1.el10_2 | 6.12.0-211.47.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.55.1.el10_2 | 6.12.0-211.55.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.55.1.el10_2 | 6.12.0-211.55.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.47.1.el10_2 | 6.12.0-211.47.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.47.1.el10_2 | 6.12.0-211.47.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.55.1.el10_2 | 6.12.0-211.55.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.55.1.el10_2 | 6.12.0-211.55.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.47.1.el10_2 | 6.12.0-211.47.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.55.1.el10_2 | 6.12.0-211.55.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.47.1.el10_2 | 6.12.0-211.47.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.47.1.el10_2 | 6.12.0-211.47.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.55.1.el10_2 | 6.12.0-211.55.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.55.1.el10_2 | 6.12.0-211.55.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.47.1.el10_2 | 6.12.0-211.47.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-53359Jul 4, 2026 · KVM: x86: Fix shadow paging use-after-free due to unexpected role35Monitor
- ← EarlierCVE-2026-53360Jul 4, 2026 · KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use35Monitor
- Later →CVE-2026-53362Jul 4, 2026 · ipv6: account for fraggap on the paged allocation pathKEV61This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0cfa78c050662784fc8e3ab26dbfd1dc632b2082 | Vendor (CNA) |
| Linux Linux | 20aa894d475bd8086b25c1113ec4ca70f70c7a98 | Vendor (CNA) |
| Linux Linux | 591f1ac217428a6d2b32a8ac14aac0fab44f155a | Vendor (CNA) |
| Linux Linux | 6.1.183 | Vendor (CNA) |
| Linux Linux | 6.6.144 | Vendor (CNA) |
| Linux Linux | 82c17e13d404f686e164590483fd6c1abaa675d0 | Vendor (CNA) |
| Linux Linux | d82ba05263c69fa2437fe93e4e561cc40f4c03af | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.144.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 6.12.0-211.47.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.47.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.47.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.47.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.47.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.47.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.47.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.47.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.47.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.47.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.47.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.47.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-55.102.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-55.102.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-55.102.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-55.102.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-55.102.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-55.102.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-55.102.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-55.102.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-55.102.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package registry (OSV) |
+4
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:27 | 2026-08-10 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+36 d
- TodayNov 4, 2026+123 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.