What is CVE-2022-49361?

CVE-2022-49361 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, affecting Linux kernel versions from 3.8 onward and patched in 5.10.121, 5.15.46, 5.17.14 and others. CVE-2022-49361 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2022-49361?

CVE-2022-49361 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2022-49361?

Yes, CVE-2022-49361 has been patched. Fixed versions include 5.10.121, 5.15.46, 5.17.14 and others. If you are running Linux kernel 3.8 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2022-49361 actively exploited?

CVE-2022-49361 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2022-49361

Medium

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().

Package Linux Kernel

Published 2025-02-26

Last modified 2025-10-21

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected versions

Linux kernel versions 3.8 and later are affected. Fixed in 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19 and their respective stable series.

Affected from

≥ 3.8

Fixed in

✓ 5.10.121 5.10.x ✓ 5.15.46 5.15.x ✓ 5.17.14 5.17.x ✓ 5.18.3 5.18.x ✓ 5.19

References

The following references provide additional information about CVE-2022-49361 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Kernel patch commit
https://git.kernel.org/stable/c/11c1cd032df85df3c096a57a7f27d57819956e4a
Patch
Kernel patch commit
https://git.kernel.org/stable/c/198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8
Patch
Kernel patch commit
https://git.kernel.org/stable/c/677a82b44ebf263d4f9a0cfbd576a6ade797a07b
Patch

5 patch commits total View all on NVD

Details

CVE ID CVE-2022-49361

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2025-02-26

Modified 2025-10-21

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2022-49361?

CVE-2022-49361 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 3.8 onward and has been patched in 5.10.121, 5.15.46, 5.17.14 and others. CVE-2022-49361 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2022-49361?

CVE-2022-49361 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2022-49361?

Yes — CVE-2022-49361 has been patched. Fixed versions include 5.10.121, 5.15.46, 5.17.14 and others. If you are running Linux kernel 3.8 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2022-49361 actively exploited?

No — CVE-2022-49361 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.