CVE-2022-50059: ceph: don't leak snap_rwsem in handle_cap_grant
In the Linux kernel, the following vulnerability has been resolved:
ceph: don't leak snap_rwsem in handle_cap_grant
When handle_cap_grant is called on an IMPORT op, then the snap_rwsem is
held and the function is expected to release it before returning. It
currently fails to do that in all cases which could lead to a deadlock.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50059 is a Linux kernel Ceph client bug that can leave an internal lock unreleased during a capability import operation. The stated impact is a possible deadlock, which is primarily an availability risk for systems using Ceph-backed filesystems or services.
Executive priority
Treat this as a targeted availability issue, not a broad internet-facing emergency based on current evidence. Patch Ceph-dependent Linux systems through the normal urgent maintenance path, especially where storage interruption would affect revenue or operations.
Technical view
The flaw is in Ceph handle_cap_grant handling. On an IMPORT operation, snap_rwsem is held and should be released before return. The vulnerable logic does not release it in all paths, creating a deadlock condition. The CVE record lists no CVSS score or CWE.
Likely exposure
Exposure is most relevant to Linux systems using the kernel Ceph client. The source bundle lists Linux kernel versions including 5.8, 5.10.138, 5.15.63, 5.19.4, and 6.0 as affected, but does not provide distribution-specific package status.
Exploitation context
No active exploitation is indicated. The CVE is not marked in KEV, and the supplied sources do not describe public exploitation. The known condition is a Ceph capability import path that can trigger a kernel deadlock.
Researcher notes
The public record confirms a lock-release bug and stable kernel fix references, but lacks CVSS, CWE, exploitability analysis, and distribution package mapping. Further assessment should focus on affected kernel lineage, Ceph client usage, and whether vendor backports include the fix.
Mitigation direction
Identify systems using Ceph or CephFS with affected Linux kernels.
Apply vendor kernel updates containing the referenced stable fixes.
Prioritize storage clients supporting production or customer-facing services.
Check Linux distribution advisories for exact fixed package versions.
Monitor for Ceph client hangs until updated.
Validation and detection
Inventory kernel versions on Ceph client systems.
Confirm whether Ceph filesystem functionality is enabled or mounted.
Compare installed kernels with vendor advisories and referenced stable commits.
Review kernel or service telemetry for deadlock-related hangs.
Document remaining affected systems and patch ownership.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-50059 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:02 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.