ceph: fix crash after fscrypt_encrypt_pagecache_blocks() error
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4a918f04cf97b2436a8dfe5cb51bb33f8e8831f4, Kernel 249e0a47cdb46bb9eae65511c569044bd8698d7d and Kernel dd1616ecbea920d228c56729461ed223cc501425.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.15, >=0f2b2b7cacf888229cec19126e6791b11fb35f32 <4a918f04cf97b2436a8dfe5cb51bb33f8e8831f4, >=ce80b76dd32764cc914975777e058d4fae4f0ea0 <249e0a47cdb46bb9eae65511c569044bd8698d7d, >=ce80b76dd32764cc914975777e058d4fae4f0ea0 <dd1616ecbea920d228c56729461ed223cc501425 | 4a918f04cf97b2436a8dfe5cb51bb33f8e8831f4, 249e0a47cdb46bb9eae65511c569044bd8698d7d, dd1616ecbea920d228c56729461ed223cc501425 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket