Vulnerability-Lookup

GHSA-F8RH-5CG2-MCJ8

Vulnerability from github – Published: 2025-10-04 18:31 – Updated: 2026-02-10 00:30

Details

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

f2fs: fix to avoid use-after-free for cached IPU bio

xfstest generic/019 reports a bug:

kernel BUG at mm/filemap.c:1619! RIP: 0010:folio_end_writeback+0x8a/0x90 Call Trace: end_page_writeback+0x1c/0x60 f2fs_write_end_io+0x199/0x420 bio_endio+0x104/0x180 submit_bio_noacct+0xa5/0x510 submit_bio+0x48/0x80 f2fs_submit_write_bio+0x35/0x300 f2fs_submit_merged_ipu_write+0x2a0/0x2b0 f2fs_write_single_data_page+0x838/0x8b0 f2fs_write_cache_pages+0x379/0xa30 f2fs_write_data_pages+0x30c/0x340 do_writepages+0xd8/0x1b0 __writeback_single_inode+0x44/0x370 writeback_sb_inodes+0x233/0x4d0 __writeback_inodes_wb+0x56/0xf0 wb_writeback+0x1dd/0x2d0 wb_workfn+0x367/0x4a0 process_one_work+0x21d/0x430 worker_thread+0x4e/0x3c0 kthread+0x103/0x130 ret_from_fork+0x2c/0x50

The root cause is: after cp_error is set, f2fs_submit_merged_ipu_write() in f2fs_write_single_data_page() tries to flush IPU bio in cache, however f2fs_submit_merged_ipu_write() missed to check validity of @bio parameter, result in submitting random cached bio which belong to other IO context, then it will cause use-after-free issue, fix it by adding additional validity check.

Severity

7.8 (High)


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

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2023-53537"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-416"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-10-04T16:15:48Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid use-after-free for cached IPU bio\n\nxfstest generic/019 reports a bug:\n\nkernel BUG at mm/filemap.c:1619!\nRIP: 0010:folio_end_writeback+0x8a/0x90\nCall Trace:\n end_page_writeback+0x1c/0x60\n f2fs_write_end_io+0x199/0x420\n bio_endio+0x104/0x180\n submit_bio_noacct+0xa5/0x510\n submit_bio+0x48/0x80\n f2fs_submit_write_bio+0x35/0x300\n f2fs_submit_merged_ipu_write+0x2a0/0x2b0\n f2fs_write_single_data_page+0x838/0x8b0\n f2fs_write_cache_pages+0x379/0xa30\n f2fs_write_data_pages+0x30c/0x340\n do_writepages+0xd8/0x1b0\n __writeback_single_inode+0x44/0x370\n writeback_sb_inodes+0x233/0x4d0\n __writeback_inodes_wb+0x56/0xf0\n wb_writeback+0x1dd/0x2d0\n wb_workfn+0x367/0x4a0\n process_one_work+0x21d/0x430\n worker_thread+0x4e/0x3c0\n kthread+0x103/0x130\n ret_from_fork+0x2c/0x50\n\nThe root cause is: after cp_error is set, f2fs_submit_merged_ipu_write()\nin f2fs_write_single_data_page() tries to flush IPU bio in cache, however\nf2fs_submit_merged_ipu_write() missed to check validity of @bio parameter,\nresult in submitting random cached bio which belong to other IO context,\nthen it will cause use-after-free issue, fix it by adding additional\nvalidity check.",
  "id": "GHSA-f8rh-5cg2-mcj8",
  "modified": "2026-02-10T00:30:27Z",
  "published": "2025-10-04T18:31:14Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-53537"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/5cdb422c839134273866208dad5360835ddb9794"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7d058f0ab161437369ad6e45a4b67c2886e71373"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/97ec6f1788cc6bee3f8c89cb908e1a2a1cd859bb"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9a7f63283af6befc0f91d549f4f6917dff7479a9"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/af4ce124d7bd74cb839bbdaccffbb416771a56b5"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b2f423fda64fb49213aa0ed5056079cf295a5df2"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2023-53537 (GCVE-0-2023-53537)

Vulnerability from cvelistv5 – Published: 2025-10-04 15:16 – Updated: 2026-08-05 09:14

Title

f2fs: fix to avoid use-after-free for cached IPU bio

Summary

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid use-after-free for cached IPU bio xfstest generic/019 reports a bug: kernel BUG at mm/filemap.c:1619! RIP: 0010:folio_end_writeback+0x8a/0x90 Call Trace: end_page_writeback+0x1c/0x60 f2fs_write_end_io+0x199/0x420 bio_endio+0x104/0x180 submit_bio_noacct+0xa5/0x510 submit_bio+0x48/0x80 f2fs_submit_write_bio+0x35/0x300 f2fs_submit_merged_ipu_write+0x2a0/0x2b0 f2fs_write_single_data_page+0x838/0x8b0 f2fs_write_cache_pages+0x379/0xa30 f2fs_write_data_pages+0x30c/0x340 do_writepages+0xd8/0x1b0 __writeback_single_inode+0x44/0x370 writeback_sb_inodes+0x233/0x4d0 __writeback_inodes_wb+0x56/0xf0 wb_writeback+0x1dd/0x2d0 wb_workfn+0x367/0x4a0 process_one_work+0x21d/0x430 worker_thread+0x4e/0x3c0 kthread+0x103/0x130 ret_from_fork+0x2c/0x50 The root cause is: after cp_error is set, f2fs_submit_merged_ipu_write() in f2fs_write_single_data_page() tries to flush IPU bio in cache, however f2fs_submit_merged_ipu_write() missed to check validity of @bio parameter, result in submitting random cached bio which belong to other IO context, then it will cause use-after-free issue, fix it by adding additional validity check.

Severity

7.8 (High)


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

Assigner

Linux mitre root

References

6 references

URL	Tags
https://git.kernel.org/stable/c/b2f423fda64fb4921…
https://git.kernel.org/stable/c/9a7f63283af6befc0…
https://git.kernel.org/stable/c/7d058f0ab16143736…
https://git.kernel.org/stable/c/97ec6f1788cc6bee3…
https://git.kernel.org/stable/c/af4ce124d7bd74cb8…
https://git.kernel.org/stable/c/5cdb422c839134273…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 0b20fcec8651569935a10afe03fedc0b812d044e , < b2f423fda64fb49213aa0ed5056079cf295a5df2 (git) Affected: 0b20fcec8651569935a10afe03fedc0b812d044e , < 9a7f63283af6befc0f91d549f4f6917dff7479a9 (git) Affected: 0b20fcec8651569935a10afe03fedc0b812d044e , < 7d058f0ab161437369ad6e45a4b67c2886e71373 (git) Affected: 0b20fcec8651569935a10afe03fedc0b812d044e , < 97ec6f1788cc6bee3f8c89cb908e1a2a1cd859bb (git) Affected: 0b20fcec8651569935a10afe03fedc0b812d044e , < af4ce124d7bd74cb839bbdaccffbb416771a56b5 (git) Affected: 0b20fcec8651569935a10afe03fedc0b812d044e , < 5cdb422c839134273866208dad5360835ddb9794 (git)
Linux	Linux	Affected: 5.5 Unaffected: 0 , < 5.5 (semver) Unaffected: 5.10.180 , ≤ 5.10.* (semver) Unaffected: 5.15.111 , ≤ 5.15.* (semver) Unaffected: 6.1.28 , ≤ 6.1.* (semver) Unaffected: 6.2.15 , ≤ 6.2.* (semver) Unaffected: 6.3.2 , ≤ 6.3.* (semver) Unaffected: 6.4 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/f2fs/data.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "b2f423fda64fb49213aa0ed5056079cf295a5df2",
              "status": "affected",
              "version": "0b20fcec8651569935a10afe03fedc0b812d044e",
              "versionType": "git"
            },
            {
              "lessThan": "9a7f63283af6befc0f91d549f4f6917dff7479a9",
              "status": "affected",
              "version": "0b20fcec8651569935a10afe03fedc0b812d044e",
              "versionType": "git"
            },
            {
              "lessThan": "7d058f0ab161437369ad6e45a4b67c2886e71373",
              "status": "affected",
              "version": "0b20fcec8651569935a10afe03fedc0b812d044e",
              "versionType": "git"
            },
            {
              "lessThan": "97ec6f1788cc6bee3f8c89cb908e1a2a1cd859bb",
              "status": "affected",
              "version": "0b20fcec8651569935a10afe03fedc0b812d044e",
              "versionType": "git"
            },
            {
              "lessThan": "af4ce124d7bd74cb839bbdaccffbb416771a56b5",
              "status": "affected",
              "version": "0b20fcec8651569935a10afe03fedc0b812d044e",
              "versionType": "git"
            },
            {
              "lessThan": "5cdb422c839134273866208dad5360835ddb9794",
              "status": "affected",
              "version": "0b20fcec8651569935a10afe03fedc0b812d044e",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/f2fs/data.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.5"
            },
            {
              "lessThan": "5.5",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.10.*",
              "status": "unaffected",
              "version": "5.10.180",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.111",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.28",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.2.*",
              "status": "unaffected",
              "version": "6.2.15",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.3.*",
              "status": "unaffected",
              "version": "6.3.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.4",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.10.180",
                  "versionStartIncluding": "5.5",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.111",
                  "versionStartIncluding": "5.5",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.28",
                  "versionStartIncluding": "5.5",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.2.15",
                  "versionStartIncluding": "5.5",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.3.2",
                  "versionStartIncluding": "5.5",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.4",
                  "versionStartIncluding": "5.5",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid use-after-free for cached IPU bio\n\nxfstest generic/019 reports a bug:\n\nkernel BUG at mm/filemap.c:1619!\nRIP: 0010:folio_end_writeback+0x8a/0x90\nCall Trace:\n end_page_writeback+0x1c/0x60\n f2fs_write_end_io+0x199/0x420\n bio_endio+0x104/0x180\n submit_bio_noacct+0xa5/0x510\n submit_bio+0x48/0x80\n f2fs_submit_write_bio+0x35/0x300\n f2fs_submit_merged_ipu_write+0x2a0/0x2b0\n f2fs_write_single_data_page+0x838/0x8b0\n f2fs_write_cache_pages+0x379/0xa30\n f2fs_write_data_pages+0x30c/0x340\n do_writepages+0xd8/0x1b0\n __writeback_single_inode+0x44/0x370\n writeback_sb_inodes+0x233/0x4d0\n __writeback_inodes_wb+0x56/0xf0\n wb_writeback+0x1dd/0x2d0\n wb_workfn+0x367/0x4a0\n process_one_work+0x21d/0x430\n worker_thread+0x4e/0x3c0\n kthread+0x103/0x130\n ret_from_fork+0x2c/0x50\n\nThe root cause is: after cp_error is set, f2fs_submit_merged_ipu_write()\nin f2fs_write_single_data_page() tries to flush IPU bio in cache, however\nf2fs_submit_merged_ipu_write() missed to check validity of @bio parameter,\nresult in submitting random cached bio which belong to other IO context,\nthen it will cause use-after-free issue, fix it by adding additional\nvalidity check."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The vulnerable code is the f2fs data writeback path, reached through ordinary local filesystem activity (write/fsync/msync on an f2fs mount, plus the kernel flusher and reclaim threads); no network protocol data is involved.\nAC:L - Once the filesystem is in the cp_error state, the defect is essentially deterministic rather than a race \u2014 the stale bio_entry left behind by f2fs_inplace_write_data()\u0027s drop_bio path is picked up by the very next unguarded f2fs_submit_merged_ipu_write() call, which is how a stock xfstest (generic/019) reproduces it; the attacker fully controls the dirty-page/IPU workload on both sides of the cross-thread variant by spawning concurrent writers with small fsync batches.\nPR:L - Any unprivileged local user or Android app with write access to an f2fs mount can drive the IPU writeback path; there is no capability check anywhere between write()/fsync() and f2fs_submit_merged_ipu_write().\nUI:N - The flush is performed by the kernel\u0027s own writeback/reclaim kworkers and by the attacker\u0027s own file writes; no victim action is required.\nS:U - The corrupted struct bio, page-writeback state, and sbi page counters all live within the kernel\u0027s own security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The bio is submitted and completed twice and its refcount driven to zero while other contexts still hold the pointer, giving a use-after-free on a bioset slab object whose bi_private/bi_end_io/bi_io_vec are dereferenced afterwards \u2014 a freed-object read primitive that leaks kernel data once the slot is reclaimed by attacker-sprayed content.\nI:H - Re-submitting a freed/completed bio makes the block layer act on attacker-groomable heap contents (bi_end_io is called as a function pointer, bio_vec entries are DMA\u0027d to disk), and the cross-context steal lets add_ipu_page()/bio_add_page() write into a bio after it was freed \u2014 a controllable write and control-flow hijack primitive.\nA:H - The confirmed immediate effect is a kernel BUG_ON panic in folio_end_writeback() (mm/filemap.c:1619) from double end_page_writeback(); the duplicated dec_page_count() also underflows the writeback counters, which hangs sync/umount waiters forever."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T09:14:41.501Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/b2f423fda64fb49213aa0ed5056079cf295a5df2"
        },
        {
          "url": "https://git.kernel.org/stable/c/9a7f63283af6befc0f91d549f4f6917dff7479a9"
        },
        {
          "url": "https://git.kernel.org/stable/c/7d058f0ab161437369ad6e45a4b67c2886e71373"
        },
        {
          "url": "https://git.kernel.org/stable/c/97ec6f1788cc6bee3f8c89cb908e1a2a1cd859bb"
        },
        {
          "url": "https://git.kernel.org/stable/c/af4ce124d7bd74cb839bbdaccffbb416771a56b5"
        },
        {
          "url": "https://git.kernel.org/stable/c/5cdb422c839134273866208dad5360835ddb9794"
        }
      ],
      "title": "f2fs: fix to avoid use-after-free for cached IPU bio",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2023-53537",
    "datePublished": "2025-10-04T15:16:48.006Z",
    "dateReserved": "2025-10-04T15:14:15.919Z",
    "dateUpdated": "2026-08-05T09:14:41.501Z",
    "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.

Detection rules are retrieved from Rulezet.

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.