Skip to main content
VulnerabilityPublished Updated

CVE-2025-39878: Linux kernel · ceph: fix crash after fscrypt_encrypt_pagecache_blocks() error

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium · fixed in dd1616ecbea920d228c56729461ed223cc501425 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 11:20 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-01-14.

Patch
Available – fixed in dd1616ecbea920d228c56729461ed223cc501425, 249e0a47cdb46bb9eae65511c569044bd8698d7d, 4a918f04cf97b2436a8dfe5cb51bb33f8e8831f4
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to dd1616ecbea920d228c56729461ed223cc501425, 249e0a47cdb46bb9eae65511c569044bd8698d7d or 4a918f04cf97b2436a8dfe5cb51bb33f8e8831f4.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ce80b76dd32764cc914975777e058d4fae4f0ea0, < dd1616ecbea920d228c56729461ed223cc501425
Fixed in
  • dd1616ecbea920d228c56729461ed223cc501425
LinuxLinuxAffected
  • ≥ ce80b76dd32764cc914975777e058d4fae4f0ea0, < 249e0a47cdb46bb9eae65511c569044bd8698d7d
Fixed in
  • 249e0a47cdb46bb9eae65511c569044bd8698d7d
LinuxLinuxAffected
  • ≥ 0f2b2b7cacf888229cec19126e6791b11fb35f32, < 4a918f04cf97b2436a8dfe5cb51bb33f8e8831f4
Fixed in
  • 4a918f04cf97b2436a8dfe5cb51bb33f8e8831f4
LinuxLinuxAffected
  • =6.15
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: ceph: fix crash after fscrypt_encrypt_pagecache_blocks() error The function move_dirty_folio_in_page_array() was created by commit ce80b76dd327 ("ceph: introduce ceph_process_folio_batch() method") by moving code from ceph_writepages_start() to this function. This new function is supposed to return an error code which is checked by the caller (now ceph_process_folio_batch()), and on error, the caller invokes redirty_page_for_writepage() and then breaks from the loop. However, the refactoring commit has gone wrong, and it by accident, it always returns 0 (= success) because it first NULLs the pointer and then returns PTR_ERR(NULL) which is always 0. This means errors are silently ignored, leaving NULL entries in the page array, which may later crash the kernel. The simple solution is to call PTR_ERR() before clearing the pointer.

References

Community reviews

Loading reviews…