UBUNTU-CVE-2024-40996
In the Linux kernel, the following vulnerability has been resolved: bpf: Avoid splat in pskb_pull_reason syzkaller builds (CONFIG_DEBUG_NET=y) frequently trigger a debug hint in pskb_may_pull. We'd like to retain this debug check because it might hint at integer overflows and other issues (kernel code should pull headers, not huge value). In bpf case, this splat isn't interesting at all: such (nonsensical) bpf programs are typically generated by a fuzzer anyway. Do what Eric suggested and suppress such warning. For CONFIG_DEBUG_NET=n we don't need the extra check because pskb_may_pull will do the right thing: return an error without the WARN() backtrace.
02 / AFFECTED SOFTWARE
Affected packages
4 explicit affected versions
8 explicit affected versions
29 explicit affected versions
12 explicit affected versions
1 explicit affected versions
2 explicit affected versions
7 explicit affected versions
26 explicit affected versions
37 explicit affected versions
10 explicit affected versions
10 explicit affected versions
13 explicit affected versions
13 explicit affected versions
9 explicit affected versions
5 explicit affected versions
37 explicit affected versions
8 explicit affected versions
4 explicit affected versions
8 explicit affected versions
23 explicit affected versions
7 explicit affected versions
10 explicit affected versions
33 explicit affected versions
16 explicit affected versions
11 explicit affected versions
12 explicit affected versions
38 explicit affected versions
12 explicit affected versions
6 explicit affected versions
51 explicit affected versions
13 explicit affected versions
12 explicit affected versions
10 explicit affected versions
10 explicit affected versions
13 explicit affected versions
4 explicit affected versions
11 explicit affected versions
1 explicit affected versions
10 explicit affected versions
8 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
10 explicit affected versions
12 explicit affected versions
26 explicit affected versions
9 explicit affected versions
23 explicit affected versions
9 explicit affected versions
5 explicit affected versions
5 explicit affected versions
3 explicit affected versions
3 explicit affected versions
26 explicit affected versions
12 explicit affected versions
44 explicit affected versions
4 explicit affected versions
4 explicit affected versions
13 explicit affected versions
16 explicit affected versions
9 explicit affected versions
12 explicit affected versions
13 explicit affected versions
7 explicit affected versions
11 explicit affected versions
3 explicit affected versions
7 explicit affected versions
10 explicit affected versions
14 explicit affected versions
7 explicit affected versions
18 explicit affected versions
3 explicit affected versions
16 explicit affected versions
43 explicit affected versions
4 explicit affected versions
11 explicit affected versions
5 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
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: bpf: Avoid splat in pskb_pull_reason syzkaller builds (CONFIG_DEBUG_NET=y) frequently trigger a debug hint in pskb_may_pull. We'd like to retain this debug check because it might hint at integer overflows and other issues (kernel code should pull headers, not huge value). In bpf case, this splat isn't interesting at all: such (nonsensical) bpf programs are typically generated by a fuzzer anyway. Do what Eric suggested and suppress such warning. For CONFIG_DEBUG_NET=n we don't need the extra check because pskb_may_pull will do the right thing: return an error without the WARN() backtrace.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/2bbe3e5a2f4ef69d13be54f1cf895b4658287080
- https://git.kernel.org/stable/c/2bbe3e5a2f4ef69d13be54f1cf895b4658287080
- https://git.kernel.org/stable/c/5e90258303a358e88737afb5048bee9113beea3a
- https://git.kernel.org/stable/c/7f9644782c559635bd676c12c59389a34ed7c866
- https://git.kernel.org/stable/c/dacc15e9cb248d19e5fc63c54bef0b9b55007761
- https://ubuntu.com/security/CVE-2024-40996
- https://ubuntu.com/security/notices/USN-6999-1
- https://ubuntu.com/security/notices/USN-6999-2
- https://ubuntu.com/security/notices/USN-7004-1
- https://ubuntu.com/security/notices/USN-7005-1
- https://ubuntu.com/security/notices/USN-7005-2
- https://ubuntu.com/security/notices/USN-7008-1
- https://ubuntu.com/security/notices/USN-7029-1
- https://www.cve.org/CVERecord?id=CVE-2024-40996