linux: In the Linux kernel, the following vulnerability has been resolved: bpf: Defer the free of inner map when necessary...
CVE-2023-52447 is fixed in 22 products on 1 platform, first by ALAS2023-2024-519, released February 15, 2024. It is not reported as exploited. Patch Radar priority: Routine.
In the Linux kernel, the following vulnerability has been resolved: bpf: Defer the free of inner map when necessary When updating or deleting an inner map in map array or map htab, the map may still be accessed by non-sleepable program or sleepable program. However bpf_map_fd_put_ptr() decreases the ref-counter of the inner map directly through bpf_map_put(), if the ref-counter is the last one (which is true for most cases), the inner map will be freed by ops->map_free() in a kworker. But for now, most .map_free() callbacks don't use synchronize_rcu() or its variants to wait for the elapse of a RCU grace period, so after the invocation of ops->map_free completes, the bpf program which is accessing the inner map may incur use-after-free problem. Fix the free of inner map by invoking bpf_map_free_deferred() after both one RCU grace period and one tasks trace RCU grace period if the inner map has been removed from the outer map before. The deferment is accomplished by using call_rcu() or call_rcu_tasks_trace() when releasing the last ref-counter of bpf map. The newly-added rcu_head field in bpf_map shares the same storage space with work field to reduce the size of bpf_map.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| bpftool-debuginfo · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-debuginfo · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-debuginfo-common-aarch64 · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-debuginfo-common-x86_64 · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-devel · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-headers · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-libbpf · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-libbpf-devel · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-libbpf-static · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-livepatch-6.1.75-99.163 · amzn 2023 | 1.0-0.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-modules-extra · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-modules-extra-common · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-tools · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-tools-debuginfo · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| kernel-tools-devel · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| linux · Debian 12.15 (bookworm) | 6.1.76-1 | DEBIAN-CVE-2023-52447 | Feb 22, 2024 |
| linux · Debian 13.5 (trixie) | 6.6.15-1 | DEBIAN-CVE-2023-52447 | Feb 22, 2024 |
| linux · Debian 14 | 6.6.15-1 | DEBIAN-CVE-2023-52447 | Feb 22, 2024 |
| perf · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| perf-debuginfo · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| python3-perf · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
| python3-perf-debuginfo · amzn 2023 | 6.1.75-99.163.amzn2023 | ALAS2023-2024-519 | Feb 15, 2024 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.