# CVE-2026-89646: linux: In the Linux kernel, the following vulnerability has been resolved: ceph: fix leaked inode reference on writeback ab... CVE-2026-89646 is fixed in 20 products on 1 platform, first by DEBIAN-CVE-2026-89646, released September 23, 2026. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2026-89646 - Priority: High - CVSS: 7.8 (high) - EPSS: 0.0017 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Sep 11, 2026 ## Description In the Linux kernel, the following vulnerability has been resolved: ceph: fix leaked inode reference on writeback abort at umount ceph_dirty_folio() takes a wrbuffer claim on each newly dirtied folio: it bumps i_wrbuffer_ref (taking an ihold() on the 0->1 transition) and attaches the snap_context to folio->private. That claim is released only by ceph_put_wrbuffer_cap_refs(), which for a submitted write runs from writepages_finish(). In ceph_submit_write(), if ceph_inc_osd_stopping_blocker() fails -- which happens during umount -- the request is aborted before submission: the already-collected folios are only redirtied and unlocked, so writepages_finish() never runs and the claim is leaked. redirty_page_for_writepage() -> folio_redirty_for_writepage() -> filemap_dirty_folio() sets PG_dirty directly and does not go through ->dirty_folio, so ceph_dirty_folio() is not re-entered to rebalance it. Because every subsequent writeback also fails the osd_stopping_blocker, i_wrbuffer_ref never returns to 0, the ihold() is never dropped, and the inode cannot be evicted: VFS: Busy inodes after unmount of ceph kernel BUG at fs/super.c:650! Release the orphaned claim in the abort path before redirtying, via ceph_undo_wrbuffer_claim(): detach the snap_context, drop the wrbuffer reference (letting i_wrbuffer_ref reach 0 and iput() the inode), and drop the snap_context reference -- i.e. do what writepages_finish() would have done for these never-submitted folios. Only the locked_pages entries are undone; folios still in the fbatch were never dirty-cleared by this call (folio_clear_dirty_for_io() is the ownership-transfer point, and a successful move NULLs the fbatch slot), so they hold no claim this call owns. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel-livepatch-6.18.51-120.162 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-devel amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-headers amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-tools amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | linux Debian 14 | 7.2.6-1 | [DEBIAN-CVE-2026-89646](https://patchblox.com/security/data/fix/linux/debian-cve-2026-89646.md) | Sep 23, 2026 | | Linux | microvm-kernel6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | perf6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | python3-perf6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | --- Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.