blob: d5c895c945235cb197e6461d189c1d0ef0e812e1 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
Description:
References:
https://bugzilla.redhat.com/show_bug.cgi?id=2044578
https://access.redhat.com/security/cve/CVE-2022-0500
Notes:
carnil> As of 2022-02-21 the RH bugzilla entry does not contain enough
carnil> information to determine which commit(s) in 5.17-rc1 are meant
carnil> to address the issue.
carnil> Fixed as well in 5.16.11 for 5.16.y.
carnil> Additionally we need to clarify the scope of CVE-2022-0500. The
carnil> list of commits cover as well
carnil> c25b2ae136039ffa820c26138ed4a5e5f3ab3841 which for older
carnil> version addressed "bpf: Fix out of bounds access from invalid
carnil> *_or_null type verification".
carnil> https://bugzilla.redhat.com/show_bug.cgi?id=2044578#c13 is
carnil> unaswered yet (as of 2022-02-23).
carnil> https://lore.kernel.org/stable/20220216225209.2196865-1-haoluo@google.com/
carnil> The fix for the specific CVE is patch 7/9 "bpf: Make
carnil> per_cpu_ptr return rdonly PTR_TO_MEM".
bwh> Commit 34d3a78c681 references several commits from 5.10 as
bwh> being fixed, so branches based on 5.10 are affected and older
bwh> branches are probably not.
Bugs:
upstream: released (5.17-rc1) [34d3a78c681e8e7844b43d1a2f4671a04249c821]
5.10-upstream-stable: needed
4.19-upstream-stable: N/A "Vulnerable code not present"
4.9-upstream-stable: N/A "Vulnerable code not present"
sid: released (5.16.10-1) [bugfix/all/bpf-make-per_cpu_ptr-return-rdonly-ptr_to_mem.patch]
5.10-bullseye-security: needed
4.19-buster-security: N/A "Vulnerable code not present"
4.9-stretch-security: N/A "Vulnerable code not present"
|
