# CVE-2026-31465: linux: In the Linux kernel, the following vulnerability has been resolved: writeback: don't block sync for filesystems with... CVE-2026-31465 is fixed in 19 products on 1 platform, first by DEBIAN-CVE-2026-31465, released May 15, 2026. It is not reported as exploited. Patch Radar priority: Routine. - Web page: https://patchblox.com/security/cve/CVE-2026-31465 - Priority: Routine - CVSS: 5.5 (medium) - EPSS: 0.0012 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Apr 22, 2026 ## Description In the Linux kernel, the following vulnerability has been resolved: writeback: don't block sync for filesystems with no data integrity guarantees Add a SB_I_NO_DATA_INTEGRITY superblock flag for filesystems that cannot guarantee data persistence on sync (eg fuse). For superblocks with this flag set, sync kicks off writeback of dirty inodes but does not wait for the flusher threads to complete the writeback. This replaces the per-inode AS_NO_DATA_INTEGRITY mapping flag added in commit f9a49aa302a0 ("fs/writeback: skip AS_NO_DATA_INTEGRITY mappings in wait_sb_inodes()"). The flag belongs at the superblock level because data integrity is a filesystem-wide property, not a per-inode one. Having this flag at the superblock level also allows us to skip having to iterate every dirty inode in wait_sb_inodes() only to skip each inode individually. Prior to this commit, mappings with no data integrity guarantees skipped waiting on writeback completion but still waited on the flusher threads to finish initiating the writeback. Waiting on the flusher threads is unnecessary. This commit kicks off writeback but does not wait on the flusher threads. This change properly addresses a recent report [1] for a suspend-to-RAM hang seen on fuse-overlayfs that was caused by waiting on the flusher threads to finish: Workqueue: pm_fs_sync pm_fs_sync_work_fn Call Trace: __schedule+0x457/0x1720 schedule+0x27/0xd0 wb_wait_for_completion+0x97/0xe0 sync_inodes_sb+0xf8/0x2e0 __iterate_supers+0xdc/0x160 ksys_sync+0x43/0xb0 pm_fs_sync_work_fn+0x17/0xa0 process_one_work+0x193/0x350 worker_thread+0x1a1/0x310 kthread+0xfc/0x240 ret_from_fork+0x243/0x280 ret_from_fork_asm+0x1a/0x30 On fuse this is problematic because there are paths that may cause the flusher thread to block (eg if systemd freezes the user session cgroups first, which freezes the fuse daemon, before invoking the kernel suspend. The kernel suspend triggers ->write_node() which on fuse issues a synchronous setattr request, which cannot be processed since the daemon is frozen. Or if the daemon is buggy and cannot properly complete writeback, initiating writeback on a dirty folio already under writeback leads to writeback_get_folio() -> folio_prepare_writeback() -> unconditional wait on writeback to finish, which will cause a hang). This commit restores fuse to its prior behavior before tmp folios were removed, where sync was essentially a no-op. [1] https://lore.kernel.org/linux-fsdevel/CAJnrk1a-asuvfrbKXbEwwDSctvemF+6zfhdnuzO65Pt8HsFSRw@mail.gmail.com/T/#m632c4648e9cafc4239299887109ebd880ac6c5c1 ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool6.18 amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel-livepatch-6.18.25-52.107 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18 amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-devel amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-headers amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-tools amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | linux Debian 14 | 6.19.11-1 | [DEBIAN-CVE-2026-31465](https://patchblox.com/security/data/fix/linux/debian-cve-2026-31465.md) | May 15, 2026 | | Linux | perf6.18 amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | python3-perf6.18 amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 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.