In the Linux kernel, the following vulnerability has been resolved: f2fs: bound i_inline_xattr_size for non-inline-xattr inodes When the flexible_inline_xattr feature is enabled, do_read_inode() loads the on-disk i_inline_xattr_size unconditionally: if (f2fs_sb_has_flexible_inline_xattr(sbi)) fi->i_inline_xattr_size = le16_to_cpu(ri->i_inline_xattr_size); but sanity_check_inode() only range-checks it when the inode also has the FI_INLINE_XATTR flag set. An inode that carries an inline dentry or inline data but not FI_INLINE_XATTR -- the normal layout for an inline directory -- therefore keeps a fully attacker-controlled i_inline_xattr_size from a crafted image. get_inline_xattr_addrs() returns that value with no flag gating, so it feeds the inode geometry: MAX_INLINE_DATA() = 4 * (CUR_ADDRS_PER_INODE - i_inline_xattr_size - 1) NR_INLINE_DENTRY() = MAX_INLINE_DATA() * BITS_PER_BYTE / (...) addrs_per_page() = CUR_ADDRS_PER_INODE - i_inline_xattr_size A large i_inline_xat
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-63815 is a validation bypass vulnerability in the Linux kernel's F2FS filesystem implementation that occurs when the flexible_inline_xattr feature is enabled. The vulnerability exists because do_read_inode() unconditionally loads the on-disk i_inline_xattr_size value without proper bounds checking, while sanity_check_inode() only validates this value when the FI_INLINE_XATTR flag is set. This allows inodes without the inline extended attributes flag to carry arbitrary inline attribute size values, potentially leading to memory corruption, information disclosure, or privilege escalation. The vulnerability affects Linux systems running vulnerable kernel versions with F2FS enabled and the flexible_inline_xattr feature active, impacting both direct users and those running containerized or virtualized environments on affected hosts.
Casky's platform, leveraging Claude AI's extended reasoning capabilities across 754 mapped security skills, would detect attack patterns associated with this vulnerability by analyzing kernel memory access anomalies and filesystem metadata inconsistencies. While MITRE ATT&ACK technique mappings are not yet available for this specific CVE, practitioners using Casky would identify suspicious patterns including: unauthorized memory access attempts targeting inode structures, unusual filesystem metadata modifications, and potential exploitation attempts that leverage the validation bypass to corrupt kernel memory. Security teams would see findings related to local privilege escalation attempts, memory safety violations, and filesystem integrity issues—enabling them to correlate these indicators with vulnerable kernel versions and implement targeted mitigations before exploitation occurs.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-63815. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation