Root code execution via crash-directory rename race
Published Jan 17, 2023 · Updated Nov 3, 2025
Local privilege escalation in Ceph 16.2.9 allows local users with access to the ceph account to execute code as root via ceph-crash.service. The root-run script scans ceph-owned crash directories, then a check-to-use race and a replaced posted-directory symlink make os.rename move an attacker file into a privileged path. Exploitation requires control of the ceph account and a target on the same filesystem as /var/lib/ceph, enabling later root execution.
Summary
What happened
Local privilege escalation in Ceph 16.2.9 allows local users with access to the ceph account to execute code as root via ceph-crash.service. The root-run script scans ceph-owned crash directories, then a check-to-use race and a replaced posted-directory symlink make os.rename move an attacker file into a privileged path. Exploitation requires control of the ceph account and a target on the same filesystem as /var/lib/ceph, enabling later root execution.
The record
- CVE
- CVE-2022-3650
- Published
- Jan 17, 2023
- Updated
- Nov 3, 2025
- Vendor
- Ceph
- Product
- Ceph
- Classifications
- CWE-842, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 17, 2023CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unknown
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- ceph_crash_exploit.pyproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo