LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux F2FS writeback flaw can reuse an invalid cached I/O object after a checkpoint error, causing a use-after-free and kernel failure. Exploitation requires local, low-privileged access according to CVSS. Systems not using F2FS are unlikely to encounter the vulnerable path. Potential impact is high, but the supplied sources do not establish real-world exploitation.

Executive priority

Treat as a high-priority maintenance issue for systems actively using F2FS, especially multi-user hosts or platforms running untrusted local workloads. Schedule vendor-kernel updates promptly. Internet-facing status alone does not increase exposure because the supplied CVSS vector is local. Do not claim compromise without evidence; focus on identifying F2FS usage and confirming fix inclusion.

Technical view

After cp_error is set, f2fs_write_single_data_page() may call f2fs_submit_merged_ipu_write() with an invalid cached bio. Missing validation can submit a bio belonging to another I/O context, causing use-after-free during writeback. The referenced Linux stable commits add the required validity check. CVSS 3.1 is 7.8: local, low complexity, low privileges, no user interaction, with high potential impact.

Likely exposure

Prioritize Linux hosts that use or mount F2FS and permit local untrusted users or workloads. The supplied affected-version data is ambiguous, so exposure should be determined by checking the running kernel against vendor advisories and the referenced stable fixes. Hosts without F2FS usage have substantially lower practical exposure.

Exploitation context

CISA KEV status is false in the supplied bundle, and no cited source reports active exploitation or a public exploit. The documented trigger arose during an xfstest writeback scenario after an F2FS checkpoint error. CVSS indicates a local attacker with low privileges could potentially reach the flaw, but practical exploitability is not established here.

Researcher notes

The source demonstrates a kernel BUG and attributes it to an invalid cached IPU bio submitted across I/O contexts. The fix adds bio validity checking. Although CVSS assigns high confidentiality, integrity, and availability impacts, the bundle does not document a proven privilege-escalation technique, data disclosure, or weaponized exploit. Exact vulnerable ranges require vendor or commit-level verification.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable referenced F2FS fix.
  • Confirm fix inclusion with the operating-system vendor because the supplied version mapping is ambiguous.
  • Where updating is delayed, reduce untrusted local access to systems actively using F2FS.
  • Follow vendor guidance for any supported temporary mitigation; none is specified in the bundle.

Validation and detection

  • Inventory running kernel builds and identify systems mounting or otherwise using F2FS.
  • Compare each kernel build against its vendor advisory and the applicable stable fix commit.
  • Verify the updated kernel is running after maintenance, not merely installed.
  • Review kernel logs for F2FS writeback failures, checkpoint errors, or folio_end_writeback crashes.
  • Run approved regression tests covering F2FS writeback and checkpoint-error handling in a non-production environment.
Prepared
Confidence
high
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53537 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-53537Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0b20fcec8651569935a10afe03fedc0b812d044e, 0b20fcec8651569935a10afe03fedc0b812d044e, 0b20fcec8651569935a10afe03fedc0b812d044e, 0b20fcec8651569935a10afe03fedc0b812d044e, 0b20fcec8651569935a10afe03fedc0b812d044e, 0b20fcec8651569935a10afe03fedc0b812d044eunaffected
LinuxLinux5.5, 0, 5.10.180, 5.15.111, 6.1.28, 6.2.15, 6.3.2, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.