CVE-2022-49361 json
f2fs: fix to do sanity check for inline inode
published 2025-02-26 20 mo ago modified 2026-08-15 2 mo ago also EUVD-2022-54868
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 18%
- public exploits
- 0
- none known
Summary
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().
Patch / fix
- Linux Linux 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19
- linux Debian 14, Debian 13, Debian 12 5.18.5-1
debian advisories DEBIAN-CVE-2022-49361
- linux Ubuntu 22.04 LTS 5.15.0-47.51
- linux-aws Ubuntu 22.04 LTS 5.15.0-1019.23
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1017.23
- linux-gke Ubuntu 22.04 LTS 5.15.0-1015.18
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1013.15
- linux-kvm Ubuntu 22.04 LTS 5.15.0-1017.21
- linux-azure Ubuntu 22.04 LTS 5.15.0-1019.24
- linux-gkeop Ubuntu 22.04 LTS 5.15.0-1002.4
ubuntu advisories UBUNTU-CVE-2022-49361
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/efdefbe8b7564602ab446474788225a1f2a323b5 commit
- git.kernel.org/stable/c/7cfe2d43becaf76e562b9617d2c2d9b445f86761 commit
- git.kernel.org/stable/c/11c1cd032df85df3c096a57a7f27d57819956e4a commit
- git.kernel.org/stable/c/198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8 commit
- git.kernel.org/stable/c/677a82b44ebf263d4f9a0cfbd576a6ade797a07b commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-49361 updated
kernel: f2fs: fix to do sanity check for inline inode
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/efdefbe8b7564602ab446474788225a1f2a323b5
patch
-
git.kernel.org
/stable/c/7cfe2d43becaf76e562b9617d2c2d9b445f86761
patch
-
git.kernel.org
/stable/c/11c1cd032df85df3c096a57a7f27d57819956e4a
patch
-
git.kernel.org
/stable/c/198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8
patch
-
git.kernel.org
/stable/c/677a82b44ebf263d4f9a0cfbd576a6ade797a07b
patch
Sources
- CVE List CVE-2022-49361
- NVD CVE-2022-49361
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.