Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-49349

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: ext4: fix use-after-free in ext4_rename_dir_prepare We got issue as follows: EXT4-fs (loop0): mounted filesystem without journal.

Published Feb 26, 2025CWE-416EPSS 0.29%

Overview

CVE-2022-49349 is a high-severity vulnerability. It was published on February 26, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

ext4: fix use-after-free in ext4_rename_dir_prepare

We got issue as follows:

EXT4-fs (loop0): mounted filesystem without journal. Opts: ,errors=continue

ext4_get_first_dir_block: bh->b_data=0xffff88810bee6000 len=34478

ext4_get_first_dir_block: *parent_de=0xffff88810beee6ae bh->b_data=0xffff88810bee6000

ext4_rename_dir_prepare: [1] parent_de=0xffff88810beee6ae

==================================================================

BUG: KASAN: use-after-free in ext4_rename_dir_prepare+0x152/0x220

Read of size 4 at addr ffff88810beee6ae by task rep/1895

CPU: 13 PID: 1895 Comm: rep Not tainted 5.10.0+ #241

Call Trace:

dump_stack+0xbe/0xf9

print_address_description.constprop.0+0x1e/0x220

kasan_report.cold+0x37/0x7f

ext4_rename_dir_prepare+0x152/0x220

ext4_rename+0xf44/0x1ad0

ext4_rename2+0x11c/0x170

vfs_rename+0xa84/0x1440

do_renameat2+0x683/0x8f0

__x64_sys_renameat+0x53/0x60

do_syscall_64+0x33/0x40

entry_SYSCALL_

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/0be698ecbe4471fcad80e81ec6a05001421041b3Refgit.kernel.org/stable/c/0ff38b99fa075ddd246487a28cb9af049f4ceef1Refgit.kernel.org/stable/c/10801095224de0d0ab06ae60698680c1f883a3aeRefgit.kernel.org/stable/c/1a3a15bf6f9963d755270cbdb282863b84839195Refgit.kernel.org/stable/c/364380c00912bed9b5d99eb485018360b0ecf64fRefgit.kernel.org/stable/c/4a2bea60cf7ff957b3eda0b17750d483876a02faRefgit.kernel.org/stable/c/97f802a652a749422dede32071d29a53cf4bd034Refgit.kernel.org/stable/c/dd887f83ea54aea5b780a84527e23ab95f777fedRefgit.kernel.org/stable/c/eaecf7ebfd5dd09038a80b14be46b844f54cfc5c

How CyberStrike helps

Frequently asked questions

What is CVE-2022-49349?

CVE-2022-49349 is a high-severity vulnerability. It was published on February 26, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2022-49349?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2022-49349?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-49349?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-49349 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2022

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999