Read the docs
TI-2026-45378 Aliases CVE-2026-63812GHSA-7w3g-6v3x-44mp

f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node()

Priority LOW 33Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node() When __destroy_extent_node() sets the inode flag FI_NO_EXTENT, it does not reset the length of the largest extent to 0 and update the inode folio. Since modifications to the extent tree are disallowed afterward, the cached largest extent may become stale. This can trigger the following error in xfstests generic/388: F2FS-fs (dm-0): sanity_check_extent_cache: inode (ino=1761) extent info [220057, 57, 6] is incorrect, run fsck to fix In the f2fs_drop_inode path, __destroy_extent_node() does not need to guarantee that et->node_cnt is 0, because concurrency with writeback is expected in this path, and writeback may update the extent cache. This patch reverts commit ed78aeebef05 ("f2fs: fix node_cnt race between extent node destroy and writeback"), and remove the unnecessary zero check of et->node_cnt.

Why it matters now

EPSS 0.00126 2nd percentileScored 2026-11-07
Fix Fixed Linux (Linux): 6.6.144, 6.12.95, 6.18.38 +4

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
LinuxLinux6.6.140 to before 6.6.144; 6.12.88 to before 6.12.95; 6.18.30 to before 6.18.38; 6.1.191 to before 6.2; 7.0.7 to before 7.16.6.144, 6.12.95, 6.18.38, 6.2, 7.1Patch availableCNA
LinuxLinux7.1 and later6.6.144, 6.12.95, 6.18.38, 7.1.3, 7.2Patch availableCNA
  • Linux VendorLinux Affected 6.6.140 to before 6.6.144; 6.12.88 to before 6.12.95; 6.18.30 to before 6.18.38; 6.1.191 to before 6.2; 7.0.7 to before 7.1 Fixed in 6.6.144, 6.12.95, 6.18.38, 6.2, 7.1 Patch available CNA
  • Linux VendorLinux Affected 7.1 and later Fixed in 6.6.144, 6.12.95, 6.18.38, 7.1.3, 7.2 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*——Linux
  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* Versions — — ·Linux

Remediation

  • Fix · CNA Linux (Linux) Fixed in 6.6.144, 6.12.95, 6.18.38, 6.2, 7.1
  • Fix · CNA Linux (Linux) Fixed in 6.6.144, 6.12.95, 6.18.38, 7.1.3, 7.2

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

Not affected: 5 products
  • Red Hat Enterprise Linux 10
  • Red Hat Enterprise Linux 6
  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-63812
  2. 2026-10-03 Alias added: GHSA-7w3g-6v3x-44mp
  3. 2026-10-20 Affected versions changed · Red Hat
  4. 2026-10-30 Fix available: Linux/[email protected] · CNA

References

Other 5

  • TI-2025-26358 tls: fix handling of zero-length records on the rx_list KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-38352 netfilter: bridge: make ebt_snat ARP rewrite writable KEVCVSS 3.1HIGH 8.8
  • TI-2021-02452 Incorrect authorization in Ubuntu linux kernel KEVCVSS 3.1HIGH 8.8
  • TI-2013-05264 The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the… KEVCVSS 3.1HIGH 8.8
  • TI-2022-00125 Integer overflow in kernel KEVCVSS 3.1HIGH 8.4
  • TI-2013-01864 The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9… KEVCVSS 3.1HIGH 8.4
See all 21741 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences