In PolicyKit (aka polkit) 0.115, the “start time” protection mechanism can be bypassed because fork() is not atomic, and therefore authorization decisions are improperly cached. This is related to lack of uid checking in polkitbackend/polkitbackendinteractiveauthority.c.
lists.opensuse.org/opensuse-security-announce/2019-08/msg00049.html
www.securityfocus.com/bid/106537
access.redhat.com/errata/RHSA-2019:0230
access.redhat.com/errata/RHSA-2019:0420
access.redhat.com/errata/RHSA-2019:0832
access.redhat.com/errata/RHSA-2019:2699
access.redhat.com/errata/RHSA-2019:2978
bugs.chromium.org/p/project-zero/issues/detail?id=1692
git.kernel.org/linus/7b55851367136b1efd84d98fea81ba57a98304cf
gitlab.freedesktop.org/polkit/polkit/commit/c898fdf4b1aafaa04f8ada9d73d77c8bb76e2f81
gitlab.freedesktop.org/polkit/polkit/merge_requests/19
lists.debian.org/debian-lts-announce/2019/01/msg00021.html
lists.debian.org/debian-lts-announce/2019/05/msg00041.html
lists.debian.org/debian-lts-announce/2019/05/msg00042.html
support.f5.com/csp/article/K22715344
usn.ubuntu.com/3901-1/
usn.ubuntu.com/3901-2/
usn.ubuntu.com/3903-1/
usn.ubuntu.com/3903-2/
usn.ubuntu.com/3908-1/
usn.ubuntu.com/3908-2/
usn.ubuntu.com/3910-1/
usn.ubuntu.com/3910-2/
usn.ubuntu.com/3934-1/
usn.ubuntu.com/3934-2/