Overview
About vulnerability
In the Linux kernel, the following vulnerability has been resolved:
ext4: check dot and dotdot of dx_root before making dir indexed
Syzbot reports a issue as follows:
BUG: unable to handle page fault for address: ffffed11022e24fe PGD 23ffee067 P4D 23ffee067 PUD 0 Oops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 0 PID: 5079 Comm: syz-executor306 Not tainted 6.10.0-rc5-g55027e689933 #0 Call Trace: <TASK> make_indexed_dir+0xdaf/0x13c0 fs/ext4/namei.c:2341 ext4_add_entry+0x222a/0x25d0 fs/ext4/namei.c:2451 ext4_rename fs/ext4/namei.c:3936 [inline] ext4_rename2+0x26e5/0x4370 fs/ext4/namei.c:4214 […]
The immediate cause of this problem is that there is only one valid dentry for the block to be split during do_split, so split==0 results in out of bounds accesses to the map triggering the issue.
do_split unsigned split dx_make_map count = 1 split = count/2 = 0; continued = hash2 == map[split - 1].hash; —> map[4294967295]
The maximum length of a filename is 255 and the minimum block size is 1024, so it is always guaranteed that the number of entries is greater than or equal to 2 when do_split() is called.
But syzbot’s crafted image has no dot and dotdot in dir, and the dentry distribution in dirblock is as follows:
bus dentry1 hole dentry2 free |xx–|xx————-|……………|xx————-|……………| 0 12 (8+248)=256 268 256 524 (8+256)=264 788 236 1024
So when renaming dentry1 increases its name_len length by 1, neither hole nor free is sufficient to hold the new dentry, and make_indexed_dir() is called.
In make_indexed_dir() it is assumed that the first two entries of the dirblock must be dot and dotdot, so bus and dentry1 are left in dx_root because they are treated as dot and dotdot, and only dentry2 is moved to the new leaf block. That’s why count is equal to 1.
Therefore add the ext4_check_dx_root() helper function to add more sanity checks to dot and dotdot before starting the conversion to avoid the above issue.
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:
- linux @ 5.4.0 (+18 more)
Fixes
KernelCare state
Live-patch status from KernelCare for each operating system.
| Operating system | Status | Covered kernels |
|---|---|---|
| AlmaLinux 9 | Released |
50 kernels
|
| AlmaLinux 9.2 ESU | Ready For Release | — |
| Amazon Linux 2 | Released |
93 kernels
|
| Amazon Linux 2023 | Planned | — |
| Amazon Linux 2 5.10 | Will Not Fix | — |
| Amazon Linux 2 5.4 | Will Not Fix | — |
| CentOS 7 ELS | Released |
19 kernels
|
| Debian 11 | Released |
32 kernels
|
| Debian 11 cloud | Released |
12 kernels
|
| Debian 12 | Will Not Fix | — |
| Oracle Linux 7 UEK 5 | Will Not Fix | — |
| Oracle Linux 7 UEK 6 | Released |
104 kernels
|
| Oracle Linux 8 UEK 6 | Released |
105 kernels
|
| Oracle Linux 8 UEK 7 | Released |
45 kernels
|
| Oracle Linux 9 | Released |
56 kernels
|
| Oracle Linux 9 UEK 7 | Released |
45 kernels
|
| Proxmox VE 7 5.15 | Released |
47 kernels
|
| RHEL 9 | Released |
50 kernels
|
| Rocky Linux 9 | Released |
49 kernels
|
| Ubuntu 18.04 Azure Focal | Will Not Fix | — |
| Ubuntu 18.04 HWE Focal | Will Not Fix | — |
| Ubuntu 20.04 | Planned | — |
| Ubuntu 20.04 AWS | Will Not Fix | — |
| Ubuntu 20.04 GCP | Planned | — |
| Ubuntu 20.04 HWE AWS | Released |
48 kernels
|
| Ubuntu 20.04 HWE Azure | Released |
31 kernels
|
| Ubuntu 22.04 | Released |
61 kernels
|
| Ubuntu 22.04 AWS | Released |
55 kernels
|
| Ubuntu 22.04 Azure | Released |
51 kernels
|
| Ubuntu 24.04 | Planned | — |