# CVE-2022-49349: linux: In the Linux kernel, the following vulnerability has been resolved: ext4: fix use-after-free in ext4_rename_dir_prep... CVE-2022-49349 is fixed in 27 products on 1 platform, first by RHSA-2022:7683, released November 8, 2022. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2022-49349 - Priority: High - CVSS: 7.8 (high) - EPSS: 0.0029 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Nov 8, 2022 ## 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_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f45a6fc41c9 RSP: 002b:00007ffc5a470218 EFLAGS: 00000246 ORIG_RAX: 0000000000000108 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f45a6fc41c9 RDX: 0000000000000005 RSI: 0000000020000180 RDI: 0000000000000005 RBP: 00007ffc5a470240 R08: 00007ffc5a470160 R09: 0000000020000080 R10: 00000000200001c0 R11: 0000000000000246 R12: 0000000000400bb0 R13: 00007ffc5a470320 R14: 0000000000000000 R15: 0000000000000000 The buggy address belongs to the page: page:00000000440015ce refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x10beee flags: 0x200000000000000() raw: 0200000000000000 ffffea00043ff4c8 ffffea0004325608 0000000000000000 raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff88810beee580: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88810beee600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff88810beee680: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff88810beee700: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88810beee780: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== Disabling lock debugging due to kernel taint ext4_rename_dir_prepare: [2] parent_de->inode=3537895424 ext4_rename_dir_prepare: [3] dir=0xffff888124170140 ext4_rename_dir_prepare: [4] ino=2 ext4_rename_dir_prepare: ent->dir->i_ino=2 parent=-757071872 Reason is first directory entry which 'rec_len' is 34478, then will get illegal parent entry. Now, we do not check directory entry after read directory block in 'ext4_get_first_dir_block'. To solve this issue, check directory entry in 'ext4_get_first_dir_block'. [ Trigger an ext4_error() instead of just warning if the directory is missing a '.' or '..' entry. Also make sure we return an error code if the file system is corrupted. -TYT ] ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | bpftool RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-abi-stablelists RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-abi-stablelists RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-core RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-core RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-debug RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-debug RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-debug-core RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-debug-core RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-debug-devel RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-debug-devel RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-debug-devel-matched RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-debug-modules RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-debug-modules RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-debug-modules-extra RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-debug-modules-extra RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-devel RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-devel RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-devel-matched RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-doc RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-doc RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-modules RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-modules RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-modules-extra RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-modules-extra RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-tools RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-tools RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-tools-libs RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-tools-libs RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-tools-libs-devel RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-tools-libs-devel RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-zfcpdump RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-zfcpdump RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-zfcpdump-core RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-zfcpdump-core RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-zfcpdump-devel RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-zfcpdump-devel RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-zfcpdump-devel-matched RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-zfcpdump-modules RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-zfcpdump-modules RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | kernel-zfcpdump-modules-extra RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | kernel-zfcpdump-modules-extra RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | linux Debian 12.15 (bookworm) | 5.18.5-1 | [DEBIAN-CVE-2022-49349](https://patchblox.com/security/data/fix/linux/debian-cve-2022-49349.md) | Feb 26, 2025 | | Linux | linux Debian 13.5 (trixie) | 5.18.5-1 | [DEBIAN-CVE-2022-49349](https://patchblox.com/security/data/fix/linux/debian-cve-2022-49349.md) | Feb 26, 2025 | | Linux | linux Debian 14 | 5.18.5-1 | [DEBIAN-CVE-2022-49349](https://patchblox.com/security/data/fix/linux/debian-cve-2022-49349.md) | Feb 26, 2025 | | Linux | perf RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | perf RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | | Linux | python3-perf RHEL 8 | 0:4.18.0-425.3.1.el8 | [RHSA-2022:7683](https://patchblox.com/security/data/fix/linux/rhsa-2022-7683.md) | Nov 8, 2022 | | Linux | python3-perf RHEL 9 | 0:5.14.0-162.6.1.el9_1 | [RHSA-2022:8267](https://patchblox.com/security/data/fix/linux/rhsa-2022-8267.md) | Nov 15, 2022 | --- Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.