Loading vulnerability…
CVE-2025-39927 is a race condition in the Linux kernel's Ceph client. Concurrent directory operations, such as rename, can make the cached request parent inode, req->r_parent, stale between request initiation and metadata server reply processing. Insufficient validation allows client-side state changes to be applied to an incorrect directory inode. When the parent pointer is corrected without transferring its associated CEPH_CAP_PIN reference, the old parent retains an unreleased reference and the new parent lacks a required reference, creating a risk of reference underflow in ceph_mdsc_release_request().
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A race condition in the Linux kernel's Ceph client can leave the cached parent inode stale during concurrent operations, causing state changes to be applied to incorrect directory inodes. Incorrect handling of the associated CEPH_CAP_PIN reference also causes reference leaks and risks reference underflow. The advisory assigns CVSS v3 severity 4.7, indicating a local, high-complexity attack requiring low privileges with high availability impact.
Unknown; this CVE is listed in the advisory without a corresponding technical description in the provided content.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.