Vulnerability-Lookup

CVE-2026-53368 (GCVE-0-2026-53368)

Vulnerability from cvelistv5 – Published: 2026-07-19 09:10 – Updated: 2026-08-05 12:35

Title

f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage

Summary

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 & write & fsync 'file A' 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, "fsck --dry-run" 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->node_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->node_write lock.

Severity

7.1 (High)


                        
                          CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 6992 records in the last 180 days details

References

3 references

URL	Tags
https://git.kernel.org/stable/c/bedb710b63ae1bd61…
https://git.kernel.org/stable/c/b28a83ea4934215b5…
https://git.kernel.org/stable/c/019f9dda7f66e55eb…

Impacted products

2 products

Vendor	Product	Version	CPE status
Linux	Linux	Affected: 88bd02c9472a166b706284a34a84f1243322d782 , < bedb710b63ae1bd617e65d0a8cf6cea1200b3753 (git) Affected: 88bd02c9472a166b706284a34a84f1243322d782 , < b28a83ea4934215b5de906c3ee4fbfbc651573e0 (git) Affected: 88bd02c9472a166b706284a34a84f1243322d782 , < 019f9dda7f66e55eb94cd32e1d3fff5835f73fbc (git)	guessed
Linux	Linux	Affected: 3.18 Unaffected: 0 , < 3.18 (semver) Unaffected: 6.18.30 , ≤ 6.18.* (semver) Unaffected: 7.0.7 , ≤ 7.0.* (semver) Unaffected: 7.1 , ≤ * (original_commit_for_fix)	guessed

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/f2fs/node.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "bedb710b63ae1bd617e65d0a8cf6cea1200b3753",
              "status": "affected",
              "version": "88bd02c9472a166b706284a34a84f1243322d782",
              "versionType": "git"
            },
            {
              "lessThan": "b28a83ea4934215b5de906c3ee4fbfbc651573e0",
              "status": "affected",
              "version": "88bd02c9472a166b706284a34a84f1243322d782",
              "versionType": "git"
            },
            {
              "lessThan": "019f9dda7f66e55eb94cd32e1d3fff5835f73fbc",
              "status": "affected",
              "version": "88bd02c9472a166b706284a34a84f1243322d782",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/f2fs/node.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "3.18"
            },
            {
              "lessThan": "3.18",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.30",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.0.*",
              "status": "unaffected",
              "version": "7.0.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.30",
                  "versionStartIncluding": "3.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.7",
                  "versionStartIncluding": "3.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1",
                  "versionStartIncluding": "3.18",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage\n\nf2fs_need_dentry_mark() reads nat_entry flags without mutual exclusion\nwith the checkpoint path, which can result in an incorrect inode block\nmarking state. The scenario is as follows:\n\ncreate \u0026 write \u0026 fsync \u0027file A\u0027                 write checkpoint\n- f2fs_do_sync_file // inline inode\n - f2fs_write_inode // inode folio is dirty\n                                                - f2fs_write_checkpoint\n                                                 - f2fs_flush_merged_writes\n                                                 - f2fs_sync_node_pages\n - f2fs_fsync_node_pages // no dirty node\n - f2fs_need_inode_block_update // return true\n - f2fs_fsync_node_pages // inode dirtied\n  - f2fs_need_dentry_mark //return true\n                                                 - f2fs_flush_nat_entries\n                                                - f2fs_write_checkpoint end\n  - __write_node_folio // inode with DENT_BIT_SHIFT set\n  SPO, \"fsck --dry-run\" find inode has already checkpointed but still\n  with DENT_BIT_SHIFT set\n\nThe state observed by f2fs_need_dentry_mark() can differ from the state\nobserved in __write_node_folio() after acquiring sbi-\u003enode_write. The\nroot cause is that the semantics of IS_CHECKPOINTED and\nHAS_FSYNCED_INODE are only guaranteed after the checkpoint write has\nfully completed.\n\nThis patch moves set_dentry_mark() into __write_node_folio() and\nprotects it with the sbi-\u003enode_write lock."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.1,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The bug is reached via local filesystem syscalls (fsync/fdatasync on a writable file) on an F2FS mount. F2FS is primarily deployed on local flash storage (Android /data, ChromeOS, embedded), not as a network-facing attack surface.\nAC:L - An attacker controls both sides of the race by concurrently fsyncing an inline inode while triggering a checkpoint (e.g., via sync(2), heavy writeback, or background checkpoint/GC threads). No conditions outside attacker influence are required beyond routine concurrent I/O.\nPR:L - Exploitation requires only unprivileged write access to files on the F2FS filesystem plus the ability to issue fsync/sync syscalls. No CAP_SYS_ADMIN, mount privileges, or init-namespace root are needed.\nUI:N - No victim interaction is required; the attacker performs the write and fsync operations on files they can already modify.\nS:U - The impact is confined to F2FS on-disk metadata and recovery semantics within the same kernel/filesystem security boundary. There is no VM escape, sandbox breakout, or cross-authority boundary crossing.\nC:N - The bug causes incorrect setting of the DENT_BIT_SHIFT recovery flag on a node block. It does not read kernel memory, leak pointers, or disclose data beyond what the attacker already wrote.\nI:H - The race writes incorrect dentry recovery metadata to disk (checkpointed inode still marked with DENT_BIT_SHIFT), producing fsck-detectable filesystem inconsistency and potentially breaking roll-forward recovery of fsynced data after sudden power-off.\nA:H - Corrupted recovery metadata can cause mount-time recovery failures (as seen in the related atomic-write variant returning -EINVAL from f2fs_recover_inode_page) and fsck-detected inconsistency after power loss, degrading filesystem availability on F2FS-backed systems such as Android devices."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:35:15.297Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/bedb710b63ae1bd617e65d0a8cf6cea1200b3753"
        },
        {
          "url": "https://git.kernel.org/stable/c/b28a83ea4934215b5de906c3ee4fbfbc651573e0"
        },
        {
          "url": "https://git.kernel.org/stable/c/019f9dda7f66e55eb94cd32e1d3fff5835f73fbc"
        }
      ],
      "title": "f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-53368",
    "datePublished": "2026-07-19T09:10:29.573Z",
    "dateReserved": "2026-06-09T07:44:35.400Z",
    "dateUpdated": "2026-08-05T12:35:15.297Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-53368",
      "date": "2026-10-20",
      "epss": "0.00169",
      "percentile": "0.05898"
    },
    "microsoft_vex": {
      "current_release_date": "2026-08-13T00:16:39.000Z",
      "cve": "CVE-2026-53368",
      "id": "msrc_CVE-2026-53368",
      "initial_release_date": "2026-07-20T01:03:16.000Z",
      "product_status:known_affected": "1",
      "product_status:known_not_affected": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-53368.json",
      "version": "3"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "fs/f2fs/node.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "bedb710b63ae1bd617e65d0a8cf6cea1200b3753",
                    "status": "affected",
                    "version": "88bd02c9472a166b706284a34a84f1243322d782",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "b28a83ea4934215b5de906c3ee4fbfbc651573e0",
                    "status": "affected",
                    "version": "88bd02c9472a166b706284a34a84f1243322d782",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "019f9dda7f66e55eb94cd32e1d3fff5835f73fbc",
                    "status": "affected",
                    "version": "88bd02c9472a166b706284a34a84f1243322d782",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "fs/f2fs/node.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "3.18"
                  },
                  {
                    "lessThan": "3.18",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.18.*",
                    "status": "unaffected",
                    "version": "6.18.30",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "7.0.*",
                    "status": "unaffected",
                    "version": "7.0.7",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "7.1",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "1D338BAC-AB8F-4767-B816-F8E37E140F88",
                    "versionEndExcluding": "6.18.30",
                    "versionStartIncluding": "3.18",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "D0893CA7-9AE6-4DFE-AC75-48967D73AD8E",
                    "versionEndExcluding": "7.0.7",
                    "versionStartIncluding": "6.19",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage\n\nf2fs_need_dentry_mark() reads nat_entry flags without mutual exclusion\nwith the checkpoint path, which can result in an incorrect inode block\nmarking state. The scenario is as follows:\n\ncreate \u0026 write \u0026 fsync \u0027file A\u0027                 write checkpoint\n- f2fs_do_sync_file // inline inode\n - f2fs_write_inode // inode folio is dirty\n                                                - f2fs_write_checkpoint\n                                                 - f2fs_flush_merged_writes\n                                                 - f2fs_sync_node_pages\n - f2fs_fsync_node_pages // no dirty node\n - f2fs_need_inode_block_update // return true\n - f2fs_fsync_node_pages // inode dirtied\n  - f2fs_need_dentry_mark //return true\n                                                 - f2fs_flush_nat_entries\n                                                - f2fs_write_checkpoint end\n  - __write_node_folio // inode with DENT_BIT_SHIFT set\n  SPO, \"fsck --dry-run\" find inode has already checkpointed but still\n  with DENT_BIT_SHIFT set\n\nThe state observed by f2fs_need_dentry_mark() can differ from the state\nobserved in __write_node_folio() after acquiring sbi-\u003enode_write. The\nroot cause is that the semantics of IS_CHECKPOINTED and\nHAS_FSYNCED_INODE are only guaranteed after the checkpoint write has\nfully completed.\n\nThis patch moves set_dentry_mark() into __write_node_folio() and\nprotects it with the sbi-\u003enode_write lock."
          }
        ],
        "id": "CVE-2026-53368",
        "lastModified": "2026-07-29T16:55:46.613",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "LOCAL",
                "availabilityImpact": "HIGH",
                "baseScore": 7.1,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "NONE",
                "integrityImpact": "HIGH",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 1.8,
              "impactScore": 5.2,
              "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
              "type": "Secondary"
            }
          ]
        },
        "published": "2026-07-19T09:17:01.903",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/019f9dda7f66e55eb94cd32e1d3fff5835f73fbc"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/b28a83ea4934215b5de906c3ee4fbfbc651573e0"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/bedb710b63ae1bd617e65d0a8cf6cea1200b3753"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Analyzed",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "NVD-CWE-noinfo"
              }
            ],
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-10-15T14:44:17+00:00",
      "cve": "CVE-2026-53368",
      "id": "CVE-2026-53368",
      "initial_release_date": "2026-07-19T00:00:00+00:00",
      "product_status:known_not_affected": "275",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53368.json",
      "version": "3"
    }
  }
}

UBUNTU-CVE-2026-53368 (CVE-2026-53368)

Vulnerability from osv_ubuntu – Published: 2026-07-20 00:00 – Updated: 2026-10-17 09:45 – Source website

Details

Severity

7.1 (High)


                    
                      CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

N/A (UNKNOWN)

low

References

URL

Type

	https://ubuntu.com/security/CVE-2026-53368	REPORT
	https://www.cve.org/CVERecord?id=CVE-2026-53368	REPORT
	https://git.kernel.org/linus/019f9dda7f66e55eb94c…	REPORT
	https://ubuntu.com/security/notices/USN-8593-1	ADVISORY
	https://ubuntu.com/security/notices/USN-8603-1	ADVISORY
	https://ubuntu.com/security/notices/USN-8618-1	ADVISORY
	https://ubuntu.com/security/notices/USN-8663-1	ADVISORY
	https://ubuntu.com/security/notices/USN-8664-1	ADVISORY
	https://ubuntu.com/security/notices/USN-8728-1	ADVISORY
	https://ubuntu.com/security/notices/USN-8781-1	ADVISORY
	https://ubuntu.com/security/notices/USN-8728-2	ADVISORY
	https://ubuntu.com/security/notices/USN-8728-3	ADVISORY

JSON

To clipboard

Loading 1.0 MB of JSON…

WID-SEC-W-2026-2403

Vulnerability from csaf_certbund - Published: 2026-07-19 22:00 - Updated: 2026-08-31 22:00

Summary

Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Severity

Mittel

Scope

432 vulnerabilities in this advisory, including CVE-2026-53368.

CVE-2026-53368

Known affected: 10 products

Open the full advisory

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

CVE-2026-53368 (GCVE-0-2026-53368)

UBUNTU-CVE-2026-53368 (CVE-2026-53368)

WID-SEC-W-2026-2403

Tags

Sightings

Nomenclature

Vulnerability timeline

Related by attack behaviour