f2fs: fix to do sanity check for inline inode
Summary
| CVE | CVE-2022-49361 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2025-02-26 07:01:12 UTC |
| Updated | 2026-08-15 13:17:20 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check for inline inode Yanming reported a kernel bug in Bugzilla kernel [1], which can be reproduced. The bug message is: The kernel message is shown below: kernel BUG at fs/inode.c:611! Call Trace: evict+0x282/0x4e0 __dentry_kill+0x2b2/0x4d0 dput+0x2dd/0x720 do_renameat2+0x596/0x970 __x64_sys_rename+0x78/0x90 do_syscall_64+0x3b/0x90 [1] https://bugzilla.kernel.org/show_bug.cgi?id=215895 The bug is due to fuzzed inode has both inline_data and encrypted flags. During f2fs_evict_inode(), as the inode was deleted by rename(), it will cause inline data conversion due to conflicting flags. The page cache will be polluted and the panic will be triggered in clear_inode(). Try fixing the bug by doing more sanity checks for inline data inode in sanity_check_inode(). |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Problem Types: NVD-CWE-noinfo
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected fcc85a4d86b5018f08717160c89c0eb50afd1dca efdefbe8b7564602ab446474788225a1f2a323b5 git | Not specified |
| CNA | Linux | Linux | affected fcc85a4d86b5018f08717160c89c0eb50afd1dca 7cfe2d43becaf76e562b9617d2c2d9b445f86761 git | Not specified |
| CNA | Linux | Linux | affected fcc85a4d86b5018f08717160c89c0eb50afd1dca 11c1cd032df85df3c096a57a7f27d57819956e4a git | Not specified |
| CNA | Linux | Linux | affected fcc85a4d86b5018f08717160c89c0eb50afd1dca 198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8 git | Not specified |
| CNA | Linux | Linux | affected fcc85a4d86b5018f08717160c89c0eb50afd1dca 677a82b44ebf263d4f9a0cfbd576a6ade797a07b git | Not specified |
| CNA | Linux | Linux | affected 4.2 | Not specified |
| CNA | Linux | Linux | unaffected 4.2 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.121 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.46 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.17.14 5.17.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.18.3 5.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.19 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/efdefbe8b7564602ab446474788225a1f2a323b5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/7cfe2d43becaf76e562b9617d2c2d9b445f86761 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/677a82b44ebf263d4f9a0cfbd576a6ade797a07b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/11c1cd032df85df3c096a57a7f27d57819956e4a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.