In the Linux kernel, the following vulnerability has been resolved: sunrpc: init gssp_lock before publishing proc entry… (CVE-2026-89540)
A race condition vulnerability in the Linux kernel's sunrpc module was resolved by ensuring proper initialization of a mutex before publishing a proc entry. The flaw allowed a write operation to lock an uninitialized mutex, potentially causing concurrency issues and resource leaks. The fix involved initializing the mutex earlier in the network namespace lifecycle, removing a race window.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel sunrpc module involved a race condition where the proc entry /proc/net/rpc/use-gss-proxy was published before the mutex sn->gssp_lock was initialized. This allowed a writer to attempt to lock an uninitialized mutex, leading to undefined behavior such as concurrent access to shared resources, potential shutdown of client handles in use, and resource leaks. The race window existed between proc_create_data() returning and mutex_init() being called. The fix moved mutex initialization to sunrpc_init_net(), ensuring the mutex is initialized before the proc entry is published, eliminating the race condition and removing the need for a lazy initialization helper.
Potential Impact
The vulnerability could lead to concurrency issues including locking an uninitialized mutex, which on debug kernels triggers an error and on production kernels can cause concurrent access to shared resources, shutdown of client handles while in use, and resource leaks. This could affect stability and reliability of the sunrpc subsystem but does not directly indicate privilege escalation or remote code execution.
Mitigation Recommendations
A fix is available and has been implemented by initializing the mutex sn->gssp_lock in sunrpc_init_net() before the proc entry is published. Users should update to a Linux kernel version that includes this fix. No additional mitigation steps are required as the fix removes the race condition entirely.
In the Linux kernel, the following vulnerability has been resolved: sunrpc: init gssp_lock before publishing proc entry… (CVE-2026-89540)
Description
A race condition vulnerability in the Linux kernel's sunrpc module was resolved by ensuring proper initialization of a mutex before publishing a proc entry. The flaw allowed a write operation to lock an uninitialized mutex, potentially causing concurrency issues and resource leaks. The fix involved initializing the mutex earlier in the network namespace lifecycle, removing a race window.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel sunrpc module involved a race condition where the proc entry /proc/net/rpc/use-gss-proxy was published before the mutex sn->gssp_lock was initialized. This allowed a writer to attempt to lock an uninitialized mutex, leading to undefined behavior such as concurrent access to shared resources, potential shutdown of client handles in use, and resource leaks. The race window existed between proc_create_data() returning and mutex_init() being called. The fix moved mutex initialization to sunrpc_init_net(), ensuring the mutex is initialized before the proc entry is published, eliminating the race condition and removing the need for a lazy initialization helper.
Potential Impact
The vulnerability could lead to concurrency issues including locking an uninitialized mutex, which on debug kernels triggers an error and on production kernels can cause concurrent access to shared resources, shutdown of client handles while in use, and resource leaks. This could affect stability and reliability of the sunrpc subsystem but does not directly indicate privilege escalation or remote code execution.
Mitigation Recommendations
A fix is available and has been implemented by initializing the mutex sn->gssp_lock in sunrpc_init_net() before the proc entry is published. Users should update to a Linux kernel version that includes this fix. No additional mitigation steps are required as the fix removes the race condition entirely.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-gwh2-5395-p8p6
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89540"]
Threat ID: 6aa4a01255bf5e2cf5a866be
Added to database: 09/12/2026, 00:42:58 UTC
Last enriched: 09/12/2026, 01:08:28 UTC
Last updated: 09/12/2026, 01:08:28 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.