LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26871: f2fs: fix NULL pointer dereference in f2fs_submit_page_write()

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix NULL pointer dereference in f2fs_submit_page_write() BUG: kernel NULL pointer dereference, address: 0000000000000014 RIP: 0010:f2fs_submit_page_write+0x6cf/0x780 [f2fs] Call Trace: <TASK> ? show_regs+0x6e/0x80 ? __die+0x29/0x70 ? page_fault_oops+0x154/0x4a0 ? prb_read_valid+0x20/0x30 ? __irq_work_queue_local+0x39/0xd0 ? irq_work_queue+0x36/0x70 ? do_user_addr_fault+0x314/0x6c0 ? exc_page_fault+0x7d/0x190 ? asm_exc_page_fault+0x2b/0x30 ? f2fs_submit_page_write+0x6cf/0x780 [f2fs] ? f2fs_submit_page_write+0x736/0x780 [f2fs] do_write_page+0x50/0x170 [f2fs] f2fs_outplace_write_data+0x61/0xb0 [f2fs] f2fs_do_write_data_page+0x3f8/0x660 [f2fs] f2fs_write_single_data_page+0x5bb/0x7a0 [f2fs] f2fs_write_cache_pages+0x3da/0xbe0 [f2fs] ... It is possible that other threads have added this fio to io->bio and submitted the io->bio before entering f2fs_submit_page_write(). At this point io->bio = NULL. If is_end_zone_blkaddr(sbi, fio->new_blkaddr) of this fio is true, then an NULL pointer dereference error occurs at bio_get(io->bio). The original code for determining zone end was after "out:", which would have missed some fio who is zone end. I've moved this code before "skip:" to make sure it's done for each fio.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-26871 is a Linux kernel F2FS crash bug. Under a write-path race, the kernel can dereference a null bio pointer, likely causing a kernel oops or system instability. Sources do not provide CVSS, exploitation evidence, or attacker prerequisites, so urgency depends on whether affected kernels use F2FS.

Executive priority

Treat this as a targeted kernel stability issue, not a confirmed widespread exploitation emergency. Patch affected F2FS-capable Linux systems through normal high-priority maintenance, with faster handling for production systems where crashes affect availability.

Technical view

The flaw is a NULL pointer dereference in f2fs_submit_page_write(). A concurrent submission can leave io->bio as NULL before zone-end handling calls bio_get(io->bio). Kernel stable commits move zone-end determination earlier so each fio is handled safely.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions with F2FS in use. The supplied record lists Linux kernel versions including 6.5, 6.6.23, 6.7.11, 6.8.2, and 6.9 as affected, but version range detail is incomplete.

Exploitation context

No cited source reports active exploitation, and KEV is false. The record describes a kernel crash condition in F2FS write handling, not a remote attack path. Public details do not establish required privileges, trigger reliability, or broader impact beyond a NULL pointer dereference.

Researcher notes

The source data lacks CVSS, CWE, exploit status, and precise distribution package mapping. Analysis should focus on commit lineage, affected stable branches, and whether local workloads exercise F2FS write paths, especially zone-end block handling.

Mitigation direction

  • Update affected Linux kernels through vendor-supported packages or stable releases containing the referenced fixes.
  • Prioritize hosts using F2FS filesystems or F2FS-capable storage workflows.
  • Check distribution advisories for exact fixed kernel package versions.
  • If immediate patching is impossible, follow vendor guidance for temporary mitigations.
  • Avoid direct wrangler or deployment implications; this is a kernel maintenance issue.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, containers hosts, and endpoint fleets.
  • Identify systems with mounted F2FS filesystems or loaded F2FS kernel support.
  • Confirm patched kernels include one of the cited stable fix commits.
  • Review kernel logs for F2FS NULL pointer dereference or related oops messages.
  • Track vendor advisory status until fixed packages are confirmed installed.
Prepared
Confidence
medium
Sources
6

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-2024-26871 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
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe067dc3c6b9c419bac43c6a0be2d85f44681f863, e067dc3c6b9c419bac43c6a0be2d85f44681f863, e067dc3c6b9c419bac43c6a0be2d85f44681f863, e067dc3c6b9c419bac43c6a0be2d85f44681f863unaffected
LinuxLinux6.5, 0, 6.6.23, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

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