CVE-2026-63815: f2fs: bound i_inline_xattr_size for non-inline-xattr inodes
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 16bc237ce3c483b75575abea53cfb639745311ed, 2a9f9791653ba5ed3fb45bbffa8d63a7cd5cf706, 378acf3cf19b6af6cba55e8dd1154c4e1504bae8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 16bc237ce3c483b75575abea53cfb639745311ed, 2a9f9791653ba5ed3fb45bbffa8d63a7cd5cf706, 378acf3cf19b6af6cba55e8dd1154c4e1504bae8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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_xattr_size drives MAX_INLINE_DATA() and NR_INLINE_DENTRY() negative, so make_dentry_ptr_inline() sets d->max (int) to a negative value. The inline directory walk then compares an unsigned long bit_pos against that negative d->max, which is promoted to a huge unsigned bound, and reads far past the inline area: while (bit_pos < d->max) /* fs/f2fs/dir.c */ ... test_bit_le(bit_pos, d->bitmap) / d->dentry[bit_pos] ... Mounting a crafted image and reading such a directory triggers an out-of-bounds read in f2fs_fill_dentries(); the same underflow also corrupts ADDRS_PER_INODE for regular files. Validate i_inline_xattr_size against MAX_INLINE_XATTR_SIZE whenever the flexible_inline_xattr feature is enabled -- i.e. whenever the value is loaded from disk and consumed -- and keep the lower MIN_INLINE_XATTR_SIZE bound gated on inodes that actually carry an inline xattr, so legitimate inodes with i_inline_xattr_size == 0 are still accepted.
- Published
- Jul 19, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-125
Report tools
Action score
33
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.15affected
- 6afc662e68b5f988282ff20afd58a89b1c279dca and later · before 3c8d6b4093aea40a20596f452289e7c22d84e6d5affected · git
- 6afc662e68b5f988282ff20afd58a89b1c279dca and later · before a08ee30dcbeff6b97df75c38c2589603ddde53a6affected · git
- 6afc662e68b5f988282ff20afd58a89b1c279dca and later · before c3e05522daae4e7348a1ea81eeb321d25aa0fd3baffected · git
- 6afc662e68b5f988282ff20afd58a89b1c279dca and later · before 76e1a05cf6d4051931d7fa4ead51a05786a62918affected · git
- 6afc662e68b5f988282ff20afd58a89b1c279dca and later · before 2a9f9791653ba5ed3fb45bbffa8d63a7cd5cf706affected · git
- 6afc662e68b5f988282ff20afd58a89b1c279dca and later · before 4ce2d52f680c1d8bfdad7cce05b815ea7ca9790daffected · git
- 6afc662e68b5f988282ff20afd58a89b1c279dca and later · before 16bc237ce3c483b75575abea53cfb639745311edaffected · git
- 6afc662e68b5f988282ff20afd58a89b1c279dca and later · before 378acf3cf19b6af6cba55e8dd1154c4e1504bae8affected · git
- before 4.15not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.15 and later · before 5.10.261
- linux linux kernel5.11 and later · before 5.15.212
- linux linux kernel5.16 and later · before 6.1.178
- linux linux kernel6.2 and later · before 6.6.145
- linux linux kernel6.7 and later · before 6.12.96
- linux linux kernel6.13 and later · before 6.18.39
- linux linux kernel6.19 and later · before 7.1.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.3-1 | 7.1.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-63813Jul 19, 2026 · Revert "f2fs: remove non-uptodate folio from the page cache in move_data_block"31Monitor
- ← EarlierCVE-2026-63814Jul 19, 2026 · f2fs: validate ACL entry sizes in f2fs_acl_from_disk()31Monitor
- Later →CVE-2026-63816Jul 19, 2026 · f2fs: atomic: fix UAF issue on f2fs_inode_info.atomic_inode31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 16bc237ce3c483b75575abea53cfb639745311ed | Vendor (CNA) |
| Linux Linux | 2a9f9791653ba5ed3fb45bbffa8d63a7cd5cf706 | Vendor (CNA) |
| Linux Linux | 378acf3cf19b6af6cba55e8dd1154c4e1504bae8 | Vendor (CNA) |
| Linux Linux | 3c8d6b4093aea40a20596f452289e7c22d84e6d5 | Vendor (CNA) |
| Linux Linux | 4ce2d52f680c1d8bfdad7cce05b815ea7ca9790d | Vendor (CNA) |
| Linux Linux | 76e1a05cf6d4051931d7fa4ead51a05786a62918 | Vendor (CNA) |
| Linux Linux | a08ee30dcbeff6b97df75c38c2589603ddde53a6 | Vendor (CNA) |
| Linux Linux | c3e05522daae4e7348a1ea81eeb321d25aa0fd3b | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0576 · Jul 20, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2a9f9791653ba5ed3fb45bbffa8d63a7cd5cf706
- git.kernel.org/stable/c/378acf3cf19b6af6cba55e8dd1154c4e1504bae8
- git.kernel.org/stable/c/3c8d6b4093aea40a20596f452289e7c22d84e6d5
- git.kernel.org/stable/c/4ce2d52f680c1d8bfdad7cce05b815ea7ca9790d
- git.kernel.org/stable/c/76e1a05cf6d4051931d7fa4ead51a05786a62918
- git.kernel.org/stable/c/a08ee30dcbeff6b97df75c38c2589603ddde53a6
- git.kernel.org/stable/c/c3e05522daae4e7348a1ea81eeb321d25aa0fd3b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.