Vulnerability-Lookup

GHSA-PXXC-GX8X-H7J2

Vulnerability from github – Published: 2026-09-24 18:31 – Updated: 2026-09-24 18:31

Details

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix to zero post-EOF data when extending file size

generic/794 4s ... - output mismatch (see /share/git/fstests/results//generic/794.out.bad) --- tests/generic/794.out 2026-06-12 08:46:32.766426241 +0800 +++ /share/git/fstests/results//generic/794.out.bad 2026-07-05 18:32:55.000000000 +0800 @@ -1,4 +1,16 @@ QA output created by 794 append_write +FAIL: non-zero data in gap [4080,4096) after shutdown+remount +000000 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a >ZZZZZZZZZZZZZZZZ< +* +001000 truncate_up ... (Run 'diff -u /share/git/fstests/tests/generic/794.out /share/git/fstests/results//generic/794.out.bad' to see the entire diff) Ran: generic/794 Failures: generic/794 Failed 1 of 1 tests

Steps of generic/794: 1. write 4096 bytes to file w/ 0x5a 2. use fiemap to get PBA of first block in file 3. truncate file to 4080 4. umount; write 4096 bytes to file w/ 0x5a directly via PBA; mount 5. extend filesize via a) append 4096 from offset 4096, or b) truncate 8192, or c) fallocate 4096 from offset 4096 6. verify the gap is zeroed in memory [4080,4096) 7. sync range 4096 from offset 4096; shutdown -f (flush meta before shutdown) 8. umount; mount; verify [4080,4096) is zeroed or not.

When extending file size (e.g. via truncate, fallocate, or write) across an unaligned EOF boundary, we need to ensure that post-EOF data in the partial page is zeroed out in pagecache and marked dirty, then writeback the cache to persist zeroed data before committing inode w/ updated i_size.

This help to prevent stale disk data beyond the previous EOF from being exposed after remounting or crash recovery.

Since f2fs is a LFS filesystem, we only support direct write via PBA in pinfile, and pinfile has section-aligned filesize, so in Android, there should no problem, but for other usage in different environment, let's fix this w/ fsync_mode=strict mount option.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-93235"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-24T16:17:19Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to zero post-EOF data when extending file size\n\ngeneric/794  4s ... - output mismatch (see /share/git/fstests/results//generic/794.out.bad)\n    --- tests/generic/794.out   2026-06-12 08:46:32.766426241 +0800\n    +++ /share/git/fstests/results//generic/794.out.bad 2026-07-05 18:32:55.000000000 +0800\n    @@ -1,4 +1,16 @@\n     QA output created by 794\n     append_write\n    +FAIL: non-zero data in gap [4080,4096) after shutdown+remount\n    +000000 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  \u003eZZZZZZZZZZZZZZZZ\u003c\n    +*\n    +001000\n     truncate_up\n    ...\n    (Run \u0027diff -u /share/git/fstests/tests/generic/794.out /share/git/fstests/results//generic/794.out.bad\u0027  to see the entire diff)\nRan: generic/794\nFailures: generic/794\nFailed 1 of 1 tests\n\nSteps of generic/794:\n1. write 4096 bytes to file w/ 0x5a\n2. use fiemap to get PBA of first block in file\n3. truncate file to 4080\n4. umount; write 4096 bytes to file w/ 0x5a directly via PBA; mount\n5. extend filesize via\n   a) append 4096 from offset 4096, or\n   b) truncate 8192, or\n   c) fallocate 4096 from offset 4096\n6. verify the gap is zeroed in memory [4080,4096)\n7. sync range 4096 from offset 4096; shutdown -f (flush meta before shutdown)\n8. umount; mount; verify [4080,4096) is zeroed or not.\n\nWhen extending file size (e.g. via truncate, fallocate, or write) across an\nunaligned EOF boundary, we need to ensure that post-EOF data in the partial\npage is zeroed out in pagecache and marked dirty, then writeback the cache to\npersist zeroed data before committing inode w/ updated i_size.\n\nThis help to prevent stale disk data beyond the previous EOF from being exposed\nafter remounting or crash recovery.\n\nSince f2fs is a LFS filesystem, we only support direct write via PBA in pinfile,\nand pinfile has section-aligned filesize, so in Android, there should no problem,\nbut for other usage in different environment, let\u0027s fix this w/ fsync_mode=strict\nmount option.",
  "id": "GHSA-pxxc-gx8x-h7j2",
  "modified": "2026-09-24T18:31:23Z",
  "published": "2026-09-24T18:31:23Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93235"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/32c7f11a24268ba8d3bb50ea7f54d33f698cd253"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/5eced87b7d19dbc76ebdddaf322046f9ac582fcb"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/6882d458d2e403f6ba7b45542dd31a6b7531eb2e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/91ec55ddc097ccddd25ffb95a3d079b2ef362372"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c42608c09b6b5d5967bf211c255914c068c2cde1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-93235 (GCVE-0-2026-93235)

Vulnerability from cvelistv5 – Published: 2026-09-24 15:33 – Updated: 2026-09-25 12:42

Title

f2fs: fix to zero post-EOF data when extending file size

Summary

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to zero post-EOF data when extending file size generic/794 4s ... - output mismatch (see /share/git/fstests/results//generic/794.out.bad) --- tests/generic/794.out 2026-06-12 08:46:32.766426241 +0800 +++ /share/git/fstests/results//generic/794.out.bad 2026-07-05 18:32:55.000000000 +0800 @@ -1,4 +1,16 @@ QA output created by 794 append_write +FAIL: non-zero data in gap [4080,4096) after shutdown+remount +000000 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a >ZZZZZZZZZZZZZZZZ< +* +001000 truncate_up ... (Run 'diff -u /share/git/fstests/tests/generic/794.out /share/git/fstests/results//generic/794.out.bad' to see the entire diff) Ran: generic/794 Failures: generic/794 Failed 1 of 1 tests Steps of generic/794: 1. write 4096 bytes to file w/ 0x5a 2. use fiemap to get PBA of first block in file 3. truncate file to 4080 4. umount; write 4096 bytes to file w/ 0x5a directly via PBA; mount 5. extend filesize via a) append 4096 from offset 4096, or b) truncate 8192, or c) fallocate 4096 from offset 4096 6. verify the gap is zeroed in memory [4080,4096) 7. sync range 4096 from offset 4096; shutdown -f (flush meta before shutdown) 8. umount; mount; verify [4080,4096) is zeroed or not. When extending file size (e.g. via truncate, fallocate, or write) across an unaligned EOF boundary, we need to ensure that post-EOF data in the partial page is zeroed out in pagecache and marked dirty, then writeback the cache to persist zeroed data before committing inode w/ updated i_size. This help to prevent stale disk data beyond the previous EOF from being exposed after remounting or crash recovery. Since f2fs is a LFS filesystem, we only support direct write via PBA in pinfile, and pinfile has section-aligned filesize, so in Android, there should no problem, but for other usage in different environment, let's fix this w/ fsync_mode=strict mount option.

Severity

No CVSS data available.

Assigner

Linux mitre root

References

5 references

URL	Tags
https://git.kernel.org/stable/c/6882d458d2e403f6b…
https://git.kernel.org/stable/c/32c7f11a24268ba8d…
https://git.kernel.org/stable/c/91ec55ddc097ccddd…
https://git.kernel.org/stable/c/c42608c09b6b5d596…
https://git.kernel.org/stable/c/5eced87b7d19dbc76…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a , < 6882d458d2e403f6ba7b45542dd31a6b7531eb2e (git) Affected: fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a , < 32c7f11a24268ba8d3bb50ea7f54d33f698cd253 (git) Affected: fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a , < 91ec55ddc097ccddd25ffb95a3d079b2ef362372 (git) Affected: fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a , < c42608c09b6b5d5967bf211c255914c068c2cde1 (git) Affected: fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a , < 5eced87b7d19dbc76ebdddaf322046f9ac582fcb (git)
Linux	Linux	Affected: 3.8 Unaffected: 0 , < 3.8 (semver) Unaffected: 6.6.157 , ≤ 6.6.* (semver) Unaffected: 6.12.110 , ≤ 6.12.* (semver) Unaffected: 6.18.51 , ≤ 6.18.* (semver) Unaffected: 7.2.5 , ≤ 7.2.* (semver) Unaffected: 7.3-rc1 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/f2fs/file.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "6882d458d2e403f6ba7b45542dd31a6b7531eb2e",
              "status": "affected",
              "version": "fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a",
              "versionType": "git"
            },
            {
              "lessThan": "32c7f11a24268ba8d3bb50ea7f54d33f698cd253",
              "status": "affected",
              "version": "fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a",
              "versionType": "git"
            },
            {
              "lessThan": "91ec55ddc097ccddd25ffb95a3d079b2ef362372",
              "status": "affected",
              "version": "fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a",
              "versionType": "git"
            },
            {
              "lessThan": "c42608c09b6b5d5967bf211c255914c068c2cde1",
              "status": "affected",
              "version": "fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a",
              "versionType": "git"
            },
            {
              "lessThan": "5eced87b7d19dbc76ebdddaf322046f9ac582fcb",
              "status": "affected",
              "version": "fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/f2fs/file.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "3.8"
            },
            {
              "lessThan": "3.8",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.157",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.110",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.51",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.157",
                  "versionStartIncluding": "3.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.110",
                  "versionStartIncluding": "3.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.51",
                  "versionStartIncluding": "3.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.5",
                  "versionStartIncluding": "3.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3-rc1",
                  "versionStartIncluding": "3.8",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to zero post-EOF data when extending file size\n\ngeneric/794  4s ... - output mismatch (see /share/git/fstests/results//generic/794.out.bad)\n    --- tests/generic/794.out   2026-06-12 08:46:32.766426241 +0800\n    +++ /share/git/fstests/results//generic/794.out.bad 2026-07-05 18:32:55.000000000 +0800\n    @@ -1,4 +1,16 @@\n     QA output created by 794\n     append_write\n    +FAIL: non-zero data in gap [4080,4096) after shutdown+remount\n    +000000 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  \u003eZZZZZZZZZZZZZZZZ\u003c\n    +*\n    +001000\n     truncate_up\n    ...\n    (Run \u0027diff -u /share/git/fstests/tests/generic/794.out /share/git/fstests/results//generic/794.out.bad\u0027  to see the entire diff)\nRan: generic/794\nFailures: generic/794\nFailed 1 of 1 tests\n\nSteps of generic/794:\n1. write 4096 bytes to file w/ 0x5a\n2. use fiemap to get PBA of first block in file\n3. truncate file to 4080\n4. umount; write 4096 bytes to file w/ 0x5a directly via PBA; mount\n5. extend filesize via\n   a) append 4096 from offset 4096, or\n   b) truncate 8192, or\n   c) fallocate 4096 from offset 4096\n6. verify the gap is zeroed in memory [4080,4096)\n7. sync range 4096 from offset 4096; shutdown -f (flush meta before shutdown)\n8. umount; mount; verify [4080,4096) is zeroed or not.\n\nWhen extending file size (e.g. via truncate, fallocate, or write) across an\nunaligned EOF boundary, we need to ensure that post-EOF data in the partial\npage is zeroed out in pagecache and marked dirty, then writeback the cache to\npersist zeroed data before committing inode w/ updated i_size.\n\nThis help to prevent stale disk data beyond the previous EOF from being exposed\nafter remounting or crash recovery.\n\nSince f2fs is a LFS filesystem, we only support direct write via PBA in pinfile,\nand pinfile has section-aligned filesize, so in Android, there should no problem,\nbut for other usage in different environment, let\u0027s fix this w/ fsync_mode=strict\nmount option."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-25T12:42:38.125Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/6882d458d2e403f6ba7b45542dd31a6b7531eb2e"
        },
        {
          "url": "https://git.kernel.org/stable/c/32c7f11a24268ba8d3bb50ea7f54d33f698cd253"
        },
        {
          "url": "https://git.kernel.org/stable/c/91ec55ddc097ccddd25ffb95a3d079b2ef362372"
        },
        {
          "url": "https://git.kernel.org/stable/c/c42608c09b6b5d5967bf211c255914c068c2cde1"
        },
        {
          "url": "https://git.kernel.org/stable/c/5eced87b7d19dbc76ebdddaf322046f9ac582fcb"
        }
      ],
      "title": "f2fs: fix to zero post-EOF data when extending file size",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-93235",
    "datePublished": "2026-09-24T15:33:33.241Z",
    "dateReserved": "2026-09-17T16:02:15.095Z",
    "dateUpdated": "2026-09-25T12:42:38.125Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

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.

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

GHSA-PXXC-GX8X-H7J2

CVE-2026-93235 (GCVE-0-2026-93235)

Tags

Sightings

Nomenclature

Related by attack behaviour