CVE-2022-49361

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2022-49361
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49361.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2022-49361
Downstream
Published
2025-02-26T02:11:08.881Z
Modified
2026-04-02T08:27:31.211123Z
Summary
f2fs: fix to do sanity check for inline inode
Details

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 __dentrykill+0x2b2/0x4d0 dput+0x2dd/0x720 dorenameat2+0x596/0x970 __x64sysrename+0x78/0x90 dosyscall64+0x3b/0x90

[1] https://bugzilla.kernel.org/show_bug.cgi?id=215895

The bug is due to fuzzed inode has both inlinedata and encrypted flags. During f2fsevictinode(), 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 clearinode().

Try fixing the bug by doing more sanity checks for inline data inode in sanitycheckinode().

Database specific 
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49361.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
98e4da8ca301e062d79ae168c67e56f3c3de3ce4
Fixed
efdefbe8b7564602ab446474788225a1f2a323b5
Fixed
7cfe2d43becaf76e562b9617d2c2d9b445f86761
Fixed
11c1cd032df85df3c096a57a7f27d57819956e4a
Fixed
198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8
Fixed
677a82b44ebf263d4f9a0cfbd576a6ade797a07b

Database specific

source 
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49361.json"