| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-56720: bpf, sockmap: Several fixes to bpf_msg_pop_data |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| bpf, sockmap: Several fixes to bpf_msg_pop_data |
| |
| Several fixes to bpf_msg_pop_data, |
| 1. In sk_msg_shift_left, we should put_page |
| 2. if (len == 0), return early is better |
| 3. pop the entire sk_msg (last == msg->sg.size) should be supported |
| 4. Fix for the value of variable "a" |
| 5. In sk_msg_shift_left, after shifting, i has already pointed to the next |
| element. Addtional sk_msg_iter_var_next may result in BUG. |
| |
| The Linux kernel CVE team has assigned CVE-2024-56720 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.0 with commit 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and fixed in 5.4.287 with commit d3f5763b3062514a234114e97bbde74d8d702449 |
| Issue introduced in 5.0 with commit 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and fixed in 5.10.231 with commit d26d977633d1d0b8bf9407278189bd0a8d973323 |
| Issue introduced in 5.0 with commit 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and fixed in 5.15.174 with commit e1f54c61c4c9a5244eb8159dce60d248f7d97b32 |
| Issue introduced in 5.0 with commit 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and fixed in 6.1.120 with commit f58d3aa457e77a3d9b3df2ab081dcf9950f6029f |
| Issue introduced in 5.0 with commit 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and fixed in 6.6.64 with commit 98c7ea7d11f2588e8197db042e0291e4ac8f8346 |
| Issue introduced in 5.0 with commit 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and fixed in 6.11.11 with commit 785180bed9879680d8e5c5e1b54c8ae8d948f4c8 |
| Issue introduced in 5.0 with commit 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and fixed in 6.12.2 with commit 275a9f3ef8fabb0cb282a62b9e164dedba7284c5 |
| Issue introduced in 5.0 with commit 7246d8ed4dcce23f7509949a77be15fa9f0e3d28 and fixed in 6.13 with commit 5d609ba262475db450ba69b8e8a557bd768ac07a |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2024-56720 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| net/core/filter.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/d3f5763b3062514a234114e97bbde74d8d702449 |
| https://git.kernel.org/stable/c/d26d977633d1d0b8bf9407278189bd0a8d973323 |
| https://git.kernel.org/stable/c/e1f54c61c4c9a5244eb8159dce60d248f7d97b32 |
| https://git.kernel.org/stable/c/f58d3aa457e77a3d9b3df2ab081dcf9950f6029f |
| https://git.kernel.org/stable/c/98c7ea7d11f2588e8197db042e0291e4ac8f8346 |
| https://git.kernel.org/stable/c/785180bed9879680d8e5c5e1b54c8ae8d948f4c8 |
| https://git.kernel.org/stable/c/275a9f3ef8fabb0cb282a62b9e164dedba7284c5 |
| https://git.kernel.org/stable/c/5d609ba262475db450ba69b8e8a557bd768ac07a |
