If used a PGP key but then a failure occurred, TB would keep the
decrypted key in memory - on Ubuntu we enable Yama ptrace restrictions
(ptrace_scope) - so this means processes can only ptrace their
descendents by default and hence even other user-level processes cannot
dump the memory of another process to say extract this private key
RCE when processing untrusted YAML - due to incomplete fix for previous
CVE-2020-1747 - that CVE not specifically patched in Ubuntu as either the
versions of pyyaml were too old to be affected or were based on upstream
releases that had already patched it
Plus CAN ISOTP race condition - discovered by a Norbert Slusarek (high
school student in Germany) - local privilege escalation
Introduced via recent broadcast mode support (normally a CAN socket
registers a particular CAN ID to receive and only gets those frames -
was only in 5.11 kernel so only affected hirsute) - this support has
been removed from the hirsute kernel until a proper fix comes from
upstream
File forwarding issue which could allow an attacker to get access to
files that are not normally provided by the permissions granted to an app
Use special tokens in the Exec line of the desktop file for an app could
trick flatpak runtime into providing access to a file as though this had
been explicitly granted by the user
snapd generates desktop files so less likely to be affected by this
sort of issue - less untrusted input in general (but perhaps also less
flexible)