LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23265: f2fs: fix to do sanity check on node footer in {read,write}_end_io

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on node footer in {read,write}_end_io -----------[ cut here ]------------ kernel BUG at fs/f2fs/data.c:358! Call Trace: <IRQ> blk_update_request+0x5eb/0xe70 block/blk-mq.c:987 blk_mq_end_request+0x3e/0x70 block/blk-mq.c:1149 blk_complete_reqs block/blk-mq.c:1224 [inline] blk_done_softirq+0x107/0x160 block/blk-mq.c:1229 handle_softirqs+0x283/0x870 kernel/softirq.c:579 __do_softirq kernel/softirq.c:613 [inline] invoke_softirq kernel/softirq.c:453 [inline] __irq_exit_rcu+0xca/0x1f0 kernel/softirq.c:680 irq_exit_rcu+0x9/0x30 kernel/softirq.c:696 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1050 [inline] sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1050 </IRQ> In f2fs_write_end_io(), it detects there is inconsistency in between node page index (nid) and footer.nid of node page. If footer of node page is corrupted in fuzzed image, then we load corrupted node page w/ async method, e.g. f2fs_ra_node_pages() or f2fs_ra_node_page(), in where we won't do sanity check on node footer, once node page becomes dirty, we will encounter this bug after node page writeback.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23265 is a Linux kernel F2FS issue where a corrupted filesystem node footer can trigger a kernel BUG during asynchronous node I/O and later writeback. The public record describes a fuzzed image scenario. Business impact is most likely availability loss on affected Linux systems that use F2FS.

Executive priority

Treat this as a kernel availability issue with incomplete severity data. Schedule remediation through normal kernel patching, but raise priority for systems that use F2FS or handle untrusted filesystem media.

Technical view

F2FS did not sanity-check node footers in read/write end I/O paths. If a corrupted node page is loaded asynchronously and later becomes dirty, f2fs_write_end_io() can detect a node ID mismatch and hit a kernel BUG in fs/f2fs/data.c. Stable kernel fixes add the missing validation.

Likely exposure

Exposure appears limited to Linux systems using F2FS and kernels within the affected ranges cited by the CVE data. The provided sources do not identify affected distributions, cloud images, devices, or default configurations.

Exploitation context

CISA KEV status is false in the source bundle, and no cited source claims active exploitation. The described trigger involves a corrupted or fuzzed F2FS image reaching asynchronous node loading and writeback, suggesting a local or filesystem-handling availability risk.

Researcher notes

The evidence supports a corrupted F2FS node-footer sanity-check flaw fixed in stable commits. No CVSS, CWE, exploitability assessment, or distribution-specific matrix is provided. Avoid expanding scope beyond Linux F2FS until vendor advisories confirm downstream impact.

Mitigation direction

  • Apply vendor or stable-kernel updates containing the referenced F2FS fixes.
  • Check your Linux distribution advisory for packaged kernel availability.
  • Restrict mounting of untrusted F2FS images where operationally possible.
  • Prioritize systems that automatically process removable or user-supplied filesystems.

Validation and detection

  • Inventory Linux hosts and identify where F2FS is mounted or supported.
  • Compare running kernel versions against vendor advisories and fixed stable commits.
  • Review kernel logs for F2FS BUG or node footer mismatch symptoms.
  • Confirm patched kernels include one of the referenced stable fixes.
Prepared
Confidence
medium
Sources
5

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-2026-23265 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

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
LinuxLinuxe05df3b115e7308afbca652769b54e4549fcc723, e05df3b115e7308afbca652769b54e4549fcc723, e05df3b115e7308afbca652769b54e4549fcc723unaffected
LinuxLinux3.8, 0, 6.18.13, 6.19.3, 7.0affected
Weakness

CWE details

No CWE listed

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