Answer in brief
CVE-2026-53368 records a High severity (CVSS 7.1) vulnerability in f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=88bd02c9472a166b706284a34a84f1243322d782 <bedb710b63ae1bd617e65d0a8cf6cea1200b3753 || >=88bd02c9472a166b706284a34a84f1243322d782 <b28a83ea4934215b5de906c3ee4fbfbc651573e0 || >=88bd02c9472a166b706284a34a84f1243322d782 <019f9dda7f66e55eb94cd32e1d3fff5835f73fbc | bedb710b63ae1bd617e65d0a8cf6cea1200b3753, b28a83ea4934215b5de906c3ee4fbfbc651573e0, 019f9dda7f66e55eb94cd32e1d3fff5835f73fbc |
| Linux/Linuxgeneric | 3.18 | Not reported |
| Linux/Linuxgeneric | >=88bd02c9472a166b706284a34a84f1243322d782 <270c519bca3a59b6140d176415aff16e4e06f9e3 || >=88bd02c9472a166b706284a34a84f1243322d782 <bedb710b63ae1bd617e65d0a8cf6cea1200b3753 || >=88bd02c9472a166b706284a34a84f1243322d782 <b28a83ea4934215b5de906c3ee4fbfbc651573e0 || >=88bd02c9472a166b706284a34a84f1243322d782 <019f9dda7f66e55eb94cd32e1d3fff5835f73fbc | 270c519bca3a59b6140d176415aff16e4e06f9e3, bedb710b63ae1bd617e65d0a8cf6cea1200b3753, b28a83ea4934215b5de906c3ee4fbfbc651573e0, 019f9dda7f66e55eb94cd32e1d3fff5835f73fbc |
| Linux/Linuxgeneric | >=88bd02c9472a166b706284a34a84f1243322d782 <bb1275802b482bc5854e434e212589fe253eab22 || >=88bd02c9472a166b706284a34a84f1243322d782 <270c519bca3a59b6140d176415aff16e4e06f9e3 || >=88bd02c9472a166b706284a34a84f1243322d782 <bedb710b63ae1bd617e65d0a8cf6cea1200b3753 || >=88bd02c9472a166b706284a34a84f1243322d782 <b28a83ea4934215b5de906c3ee4fbfbc651573e0 || >=88bd02c9472a166b706284a34a84f1243322d782 <019f9dda7f66e55eb94cd32e1d3fff5835f73fbc | bb1275802b482bc5854e434e212589fe253eab22, 270c519bca3a59b6140d176415aff16e4e06f9e3, bedb710b63ae1bd617e65d0a8cf6cea1200b3753, b28a83ea4934215b5de906c3ee4fbfbc651573e0, 019f9dda7f66e55eb94cd32e1d3fff5835f73fbc |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage f2fs_need_dentry_mark() reads nat_entry flags without mutual exclusion with the checkpoint path, which can result in an incorrect inode block marking state. The scenario is as follows: create & write & fsync 'file A' write checkpoint - f2fs_do_sync_file // inline inode - f2fs_write_inode // inode folio is dirty - f2fs_write_checkpoint - f2fs_flush_merged_writes - f2fs_sync_node_pages - f2fs_fsync_node_pages // no dirty node - f2fs_need_inode_block_update // return true - f2fs_fsync_node_pages // inode dirtied - f2fs_need_dentry_mark //return true - f2fs_flush_nat_entries - f2fs_write_checkpoint end - __write_node_folio // inode with DENT_BIT_SHIFT set SPO, "fsck --dry-run" find inode has already checkpointed but still with DENT_BIT_SHIFT set The state observed by f2fs_need_dentry_mark() can differ from the state observed in __write_node_folio() after acquiring sbi->node_write. The root cause is that the semantics of IS_CHECKPOINTED and HAS_FSYNCED_INODE are only guaranteed after the checkpoint write has fully completed. This patch moves set_dentry_mark() into __write_node_folio() and protects it with the sbi->node_write lock.
Quoted source text, attributed separately from HOL analysis.