linux

mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git synced 2025-01-23 08:35:19 -05:00

No description

Find a file

Daniel Borkmann a2ea07465c bpf: Fix missing prog untrack in release_maps Commit `da765a2f59` ("bpf: Add poke dependency tracking for prog array maps") wrongly assumed that in case of prog load errors, we're cleaning up all program tracking via bpf_free_used_maps(). However, it can happen that we're still at the point where we didn't copy map pointers into the prog's aux section such that env->prog->aux->used_maps is still zero, running into a UAF. In such case, the verifier has similar release_maps() helper that drops references to used maps from its env. Consolidate the release code into __bpf_free_used_maps() and call it from all sides to fix it. Fixes: `da765a2f59` ("bpf: Add poke dependency tracking for prog array maps") Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Signed-off-by: Alexei Starovoitov <ast@kernel.org> Acked-by: Yonghong Song <yhs@fb.com> Link: https://lore.kernel.org/bpf/1c2909484ca524ae9f55109b06f22b6213e76376.1576514756.git.daniel@iogearbox.net		2019-12-16 10:59:29 -08:00
arch	bpf, mips: Limit to 33 tail calls	2019-12-11 13:57:22 +01:00
block
certs
crypto
Documentation
drivers	qede: Fix multicast mac configuration	2019-12-12 11:08:36 -08:00
fs
include	bpf: Fix missing prog untrack in release_maps	2019-12-16 10:59:29 -08:00
init
ipc
kernel	bpf: Fix missing prog untrack in release_maps	2019-12-16 10:59:29 -08:00
lib
LICENSES
mm
net	bpf: Clear skb->tstamp in bpf_redirect when necessary	2019-12-13 15:21:48 -08:00
samples	samples: bpf: fix syscall_tp due to unused syscall	2019-12-11 15:28:06 -08:00
scripts
security
sound
tools	selftests/bpf: Test function_graph tracer and bpf trampoline together	2019-12-11 15:19:29 -08:00
usr
virt
.clang-format
.cocciconfig
.get_maintainer.ignore
.gitattributes
.gitignore
.mailmap
COPYING
CREDITS
Kbuild
Kconfig
MAINTAINERS
Makefile
README

README

Linux kernel
============

There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.

In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``.  The formatted documentation can also be read online at:

    https://www.kernel.org/doc/html/latest/

There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.

Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.