Back to CVE records
High 7.8Published Oct 1, 2025

CVE-2025-39927ceph: fix race condition validating r_parent before applying state

Updated under an hour ago ()

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

In the Linux kernel, the following vulnerability has been resolved: ceph: fix race condition validating r_parent before applying state Add validation to ensure the cached parent directory inode matches the directory info in MDS replies. This prevents client-side race conditions where concurrent operations (e.g. rename) cause r_parent to become stale between request initiation and reply processing, which could lead to applying state changes to incorrect directory inodes. [ idryomov: folded a kerneldoc fixup and a follow-up fix from Alex to move CEPH_CAP_PIN reference when r_parent is updated: When the parent directory lock is not held, req->r_parent can become stale and is updated to point to the correct inode. However, the associated CEPH_CAP_PIN reference was not being adjusted. The CEPH_CAP_PIN is a reference on an inode that is tracked for accounting purposes. Moving this pin is important to keep the accounting balanced. When the pin was not moved from the old parent to the new one, it created two problems: The reference on the old, stale parent was never released, causing a reference leak. A reference for the new parent was never acquired, creating the risk of a reference underflow later in ceph_mdsc_release_request(). This patch corrects the logic by releasing the pin from the old parent and acquiring it for the new parent when r_parent is switched. This ensures reference accounting stays balanced. ]

CVSS
7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-362
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Modified
Record last updated
Oct 21, 2026
First seen by InfoSec Signals
Oct 19, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from 9030aaf9bf0a1eee47a154c316c789e959638b0f before dc5aad078abc416dd3d555c50f5308c16ba918a7; from 9030aaf9bf0a1eee47a154c316c789e959638b0f before db378e6f83ec705c6091c65d482d555edc2b0a72; 9030aaf9bf0a1eee47a154c316c789e959638b0f builds before 2bfe45987eb346e299d9f763f9cd05f77011519f; 9030aaf9bf0a1eee47a154c316c789e959638b0f builds before 15f519e9f883b316d86e2bb6b767a023aafd9d83
CNA record
linux linux_kernel
linux:linux_kernel
from 2.6.35 before 6.12.48; from 6.13 before 6.16.8; 2.6.34; 2.6.34; 2.6.34; 2.6.34; 2.6.34; 2.6.34; and 6 more ranges
NVD

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.