writeback: don't block sync for filesystems with no data integrity guarantees

{
  "id": "d9789cfc8cc4e53191916f57dc9a1ecb6af8a56b3bc57cf7999c0497af7cc9cb",
  "url": "https://osv.dev/vulnerability/CVE-2026-31465",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "writeback: don't block sync for filesystems with no data integrity guarantees",
    "summary": "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",
    "evidence": "osv:CVE-2026-31465",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.18.21",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.19.11",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-31465",
      "aliases": [
        "CVE-2026-31465"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "0c58a97f919c24fe4245015f4375a39ff05665b6"
                },
                {
                  "fixed": "83800f8ef358ea2fc9b1ae4986b83f2bc24be927"
                },
                {
                  "fixed": "5c24a13d8a0466ca0446e58309e51f2606520164"
                },
                {
                  "fixed": "76f9377cd2ab7a9220c25d33940d9ca20d368172"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-31465.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.16.0"
                },
                {
                  "fixed": "6.18.21"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "6.19.11"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-31465.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:38.475800330Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/5c24a13d8a0466ca0446e58309e51f2606520164",
        "https://git.kernel.org/stable/c/76f9377cd2ab7a9220c25d33940d9ca20d368172",
        "https://git.kernel.org/stable/c/83800f8ef358ea2fc9b1ae4986b83f2bc24be927",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31465.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-31465",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31465.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-31465",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 505541,
  "published_at": "2026-04-22T13:53:55.614+00:00"
}