CVE-2026-63815
f2fs inode parsing flaw enables out-of-bounds reads when mounting crafted images
Is CVE-2026-63815 being exploited?
Not confirmed. CVE-2026-63815 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-63815?
CVE-2026-63815 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-63815?
Yes. A fix has been recorded for CVE-2026-63815. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63815 affect?
CVE-2026-63815 affects Linux kernel (f2fs), Systems with flexible_inline_xattr enabled, Hosts mounting f2fs images (VMs/containers). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63815?
Apply vendor kernel updates and avoid mounting untrusted f2fs images
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Mounting crafted f2fs images causes OOB reads and inode geometry corruption, enabling info leak, crashes, or potential privilege escalation.
Patch when possible
- affected>= 6afc662e68b5f988282ff20afd58a89b1c279dca and < 3c8d6b4093aea40a20596f452289e7c22d84e6d5
- affected>= 6afc662e68b5f988282ff20afd58a89b1c279dca and < a08ee30dcbeff6b97df75c38c2589603ddde53a6
- affected>= 6afc662e68b5f988282ff20afd58a89b1c279dca and < c3e05522daae4e7348a1ea81eeb321d25aa0fd3b
- affected>= 6afc662e68b5f988282ff20afd58a89b1c279dca and < 76e1a05cf6d4051931d7fa4ead51a05786a62918
- affected>= 6afc662e68b5f988282ff20afd58a89b1c279dca and < 2a9f9791653ba5ed3fb45bbffa8d63a7cd5cf706
- affected>= 6afc662e68b5f988282ff20afd58a89b1c279dca and < 4ce2d52f680c1d8bfdad7cce05b815ea7ca9790d
- affected>= 6afc662e68b5f988282ff20afd58a89b1c279dca and < 16bc237ce3c483b75575abea53cfb639745311ed
- affected>= 6afc662e68b5f988282ff20afd58a89b1c279dca and < 378acf3cf19b6af6cba55e8dd1154c4e1504bae8
- affected4.15
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.