Overview
About vulnerability
In the Linux kernel, the following vulnerability has been resolved:
ext4: fix OOB read when checking dotdot dir
Mounting a corrupted filesystem with directory which contains ‘.’ dir entry with rec_len == block size results in out-of-bounds read (later on, when the corrupted directory is removed).
ext4_empty_dir() assumes every ext4 directory contains at least ‘.’ and ‘..’ as directory entries in the first data block. It first loads the ‘.’ dir entry, performs sanity checks by calling ext4_check_dir_entry() and then uses its rec_len member to compute the location of ‘..’ dir entry (in ext4_next_entry). It assumes the ‘..’ dir entry fits into the same data block.
If the rec_len of ‘.’ is precisely one block (4KB), it slips through the sanity checks (it is considered the last directory entry in the data block) and leaves “struct ext4_dir_entry_2 *de” point exactly past the memory slot allocated to the data block. The following call to ext4_check_dir_entry() on new value of de then dereferences this pointer which results in out-of-bounds mem access.
Fix this by extending __ext4_check_dir_entry() to check for ‘.’ dir entries that reach the end of data block. Make sure to ignore the phony dir entries for checksum (by checking name_len for non-zero).
Note: This is reported by KASAN as use-after-free in case another structure was recently freed from the slot past the bound, but it is really an OOB read.
This issue was found by syzkaller tool.
Call Trace:
[ 38.594108] BUG: KASAN: slab-use-after-free in __ext4_check_dir_entry+0x67e/0x710
[ 38.594649] Read of size 2 at addr ffff88802b41a004 by task syz-executor/5375
[ 38.595158]
[ 38.595288] CPU: 0 UID: 0 PID: 5375 Comm: syz-executor Not tainted 6.14.0-rc7 #1
[ 38.595298] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014
[ 38.595304] Call Trace:
[ 38.595308]
Details
- Affected product:
- AlmaLinux 9.2 ESU , Amazon Linux 2 ELS , CentOS 6 ELS , CentOS 7 ELS , CentOS 8.4 ELS , CentOS 8.5 ELS , CentOS Stream 8 ELS , CloudLinux 6 ELS , CloudLinux 7 ELS , Debian 10 ELS , Oracle Linux 6 ELS , Oracle Linux 7 ELS , RHEL 7 ELS , TuxCare 9.6 ESU , Ubuntu 16.04 ELS , Ubuntu 18.04 ELS , Ubuntu 20.04 ELS
- Affected packages:
- kernel @ 2.6.32 (+18 more)
Fixes
KernelCare state
Live-patch status from KernelCare for each operating system.
| Operating system | Status | Covered kernels |
|---|---|---|
| AlmaLinux 9 | Released |
55 kernels
|
| Amazon Linux 2023 | Planned | — |
| CentOS 7 ELS | Released |
16 kernels
|
| Debian 11 | Released |
34 kernels
|
| Debian 11 cloud | Released |
14 kernels
|
| Debian 12 | Released |
24 kernels
|
| Oracle Linux 7 UEK 6 | Released |
112 kernels
|
| Oracle Linux 8 UEK 6 | Released |
127 kernels
|
| Oracle Linux 9 | Released |
61 kernels
|
| Proxmox VE 7 5.15 | Released |
47 kernels
|
| RHEL 10 | Will Not Fix | — |
| RHEL 9 | Released |
55 kernels
|
| Rocky Linux 9 | Released |
51 kernels
|
| Ubuntu 16.04 AWS HWE ESM | Will Not Fix | — |
| Ubuntu 16.04 Azure ESM | Will Not Fix | — |
| Ubuntu 16.04 GCP ESM | Will Not Fix | — |
| Ubuntu 16.04 HWE ESM | Will Not Fix | — |
| Ubuntu 18.04 | Will Not Fix | — |
| Ubuntu 18.04 AWS | Will Not Fix | — |
| Ubuntu 18.04 AWS Focal | Released |
56 kernels
|
| Ubuntu 18.04 Azure | Will Not Fix | — |
| Ubuntu 18.04 GCP | Will Not Fix | — |
| Ubuntu 18.04 HWE Focal | Released |
69 kernels
|
| Ubuntu 20.04 | Released |
127 kernels
|
| Ubuntu 20.04 AWS | Released |
109 kernels
|
| Ubuntu 20.04 Azure | Released |
100 kernels
|
| Ubuntu 20.04 GCP | Ready For Release | — |
| Ubuntu 20.04 HWE AWS | Released |
57 kernels
|
| Ubuntu 20.04 HWE Azure | Released |
40 kernels
|
| Ubuntu 22.04 | Released |
75 kernels
|
| Ubuntu 22.04 AWS | Released |
66 kernels
|
| Ubuntu 22.04 Azure | Released |
62 kernels
|
| Ubuntu 24.04 | Released |
31 kernels
|
| Ubuntu 24.04 AWS | Ready For Release | — |