UBUNTU-CVE-2024-47700
In the Linux kernel, the following vulnerability has been resolved: ext4: check stripe size compatibility on remount as well We disable stripe size in __ext4_fill_super if it is not a multiple of the cluster ratio however this check is missed when trying to remount. This can leave us with cases where stripe < cluster_ratio after remount:set making EXT4_B2C(sbi->s_stripe) become 0 that can cause some unforeseen bugs like divide by 0. Fix that by adding the check in remount path as well.
02 / AFFECTED SOFTWARE
Affected packages
29 explicit affected versions
10 explicit affected versions
11 explicit affected versions
12 explicit affected versions
16 explicit affected versions
1 explicit affected versions
12 explicit affected versions
7 explicit affected versions
26 explicit affected versions
37 explicit affected versions
10 explicit affected versions
10 explicit affected versions
10 explicit affected versions
13 explicit affected versions
13 explicit affected versions
4 explicit affected versions
37 explicit affected versions
13 explicit affected versions
8 explicit affected versions
4 explicit affected versions
8 explicit affected versions
19 explicit affected versions
23 explicit affected versions
7 explicit affected versions
10 explicit affected versions
33 explicit affected versions
16 explicit affected versions
13 explicit affected versions
14 explicit affected versions
12 explicit affected versions
38 explicit affected versions
51 explicit affected versions
13 explicit affected versions
10 explicit affected versions
17 explicit affected versions
10 explicit affected versions
13 explicit affected versions
11 explicit affected versions
1 explicit affected versions
10 explicit affected versions
8 explicit affected versions
17 explicit affected versions
13 explicit affected versions
21 explicit affected versions
6 explicit affected versions
13 explicit affected versions
12 explicit affected versions
7 explicit affected versions
14 explicit affected versions
18 explicit affected versions
11 explicit affected versions
12 explicit affected versions
17 explicit affected versions
26 explicit affected versions
1 explicit affected versions
18 explicit affected versions
23 explicit affected versions
7 explicit affected versions
14 explicit affected versions
5 explicit affected versions
22 explicit affected versions
15 explicit affected versions
12 explicit affected versions
3 explicit affected versions
17 explicit affected versions
26 explicit affected versions
12 explicit affected versions
21 explicit affected versions
44 explicit affected versions
10 explicit affected versions
4 explicit affected versions
4 explicit affected versions
16 explicit affected versions
9 explicit affected versions
12 explicit affected versions
13 explicit affected versions
7 explicit affected versions
19 explicit affected versions
13 explicit affected versions
7 explicit affected versions
10 explicit affected versions
14 explicit affected versions
11 explicit affected versions
18 explicit affected versions
3 explicit affected versions
16 explicit affected versions
43 explicit affected versions
11 explicit affected versions
20 explicit affected versions
20 explicit affected versions
35 explicit affected versions
12 explicit affected versions
13 explicit affected versions
6 explicit affected versions
12 explicit affected versions
50 explicit affected versions
11 explicit affected versions
12 explicit affected versions
27 explicit affected versions
12 explicit affected versions
7 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: ext4: check stripe size compatibility on remount as well We disable stripe size in __ext4_fill_super if it is not a multiple of the cluster ratio however this check is missed when trying to remount. This can leave us with cases where stripe < cluster_ratio after remount:set making EXT4_B2C(sbi->s_stripe) become 0 that can cause some unforeseen bugs like divide by 0. Fix that by adding the check in remount path as well.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/ee85e0938aa8f9846d21e4d302c3cf6a2a75110d
- https://git.kernel.org/stable/c/297615e992bbb30a55c158141086be6505d5d722
- https://git.kernel.org/stable/c/a31b712f75445d52fc0451dc54fd7b16a552cb7c
- https://git.kernel.org/stable/c/ee85e0938aa8f9846d21e4d302c3cf6a2a75110d
- https://git.kernel.org/stable/c/faeff8b1ee2eaa5969c8e994d66c3337298cefed
- https://ubuntu.com/security/CVE-2024-47700
- https://ubuntu.com/security/notices/USN-7276-1
- https://ubuntu.com/security/notices/USN-7277-1
- https://ubuntu.com/security/notices/USN-7301-1
- https://ubuntu.com/security/notices/USN-7303-1
- https://ubuntu.com/security/notices/USN-7303-2
- https://ubuntu.com/security/notices/USN-7303-3
- https://ubuntu.com/security/notices/USN-7304-1
- https://ubuntu.com/security/notices/USN-7310-1
- https://ubuntu.com/security/notices/USN-7311-1
- https://ubuntu.com/security/notices/USN-7384-1
- https://ubuntu.com/security/notices/USN-7384-2
- https://ubuntu.com/security/notices/USN-7385-1
- https://ubuntu.com/security/notices/USN-7386-1
- https://ubuntu.com/security/notices/USN-7403-1
- https://www.cve.org/CVERecord?id=CVE-2024-47700