UAF in nouveau driver when device is removed - external NVIDIA GPU? or
local user unbinding the driver?
UAF due to race condition in network packet scheduler
OOB write in NFS - user who had access to an NFS mount could possibly
exploit this
Buffer overflow in ST Micro NFC driver - failed to validate parameters
from NFC device - physically approximate attacker could possibly exploit
this but would need custom hw/sw
Similarly, Xilinx USB2 gadget driver failed to validate USB endpoints
KVM mishandled guest page table updates -> guest VM crash host OS
2 similar issues in CAN bus drivers - 8 Devices USB2CAN and Microchip CAN
Bus analyzer both had double-free on error paths - local attacker could
crash -> DoS
2 issues in handling of various message types (AIX + Cisco log messages
failed to properly validate contents and so could result in heap buffer overflow)
1 in handling of plain TCP socket comms - but this module is not enabled
in the default rsyslog configuration for Ubuntu
detects daemons that need to be restarted after libraries are upgraded
uses various regex’s to detect scripting languages - but since these were
not specific enough, it could allow a user to get their own script
executed in the context of the user which is running needrestart - which
could be root
Lots of great new bugs - expect to hear more about these in the coming weeks
Past episodes covering Ubuntu @ Pwn2Own over previous years Episode 111
and Episode 71 - in particular has a great interview with Steve and Marc
from our team who cover what it is like as a vendor