{
  "cveId": "CVE-2026-53368",
  "url": "https://patchblox.com/security/cve/CVE-2026-53368",
  "summary": "CVE-2026-53368 is fixed in linux on 1 platform, first by DEBIAN-CVE-2026-53368, released July 20, 2026. It is not reported as exploited. Patch Radar priority: High.",
  "title": "f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage  f2fs_need_dentry_mark() reads nat_entry flags without mutual exclusion with the checkpoint path, which can result in an incorrect inode block marking state. The scenario is as follows:  create \u0026 write \u0026 fsync \u0027file A\u0027                 write checkpoint - f2fs_do_sync_file // inline inode  - f2fs_write_inode // inode folio is dirty                                                 - f2fs_write_checkpoint                                                  - f2fs_flush_merged_writes                                                  - f2fs_sync_node_pages  - f2fs_fsync_node_pages // no dirty node  - f2fs_need_inode_block_update // return true  - f2fs_fsync_node_pages // inode dirtied   - f2fs_need_dentry_mark //return true                                                  - f2fs_flush_nat_entries                                                 - f2fs_write_checkpoint end   - __write_node_folio // inode with DENT_BIT_SHIFT set   SPO, \u0022fsck --dry-run\u0022 find inode has already checkpointed but still   with DENT_BIT_SHIFT set  The state observed by f2fs_need_dentry_mark() can differ from the state observed in __write_node_folio() after acquiring sbi-\u003Enode_write. The root cause is that the semantics of IS_CHECKPOINTED and HAS_FSYNCED_INODE are only guaranteed after the checkpoint write has fully completed.  This patch moves set_dentry_mark() into __write_node_folio() and protects it with the sbi-\u003Enode_write lock.",
  "published": "2026-07-19T09:17:01Z",
  "severity": "Important",
  "cvss": 7.1,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
  "epss": 0.00171,
  "epssPercentile": 0.06502,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "vendorAdvisory": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-53368",
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.12.115-2",
      "fix": "DEBIAN-CVE-2026-53368",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-53368",
      "released": "2026-07-20T12:58:36Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.0.7-1",
      "fix": "DEBIAN-CVE-2026-53368",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-53368",
      "released": "2026-07-20T12:58:36Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T06:59:42Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}