HTTP Protocol Stack Remote Code Execution Vulnerability

Office for Android Spoofing Vulnerability

3D Builder Remote Code Execution Vulnerability

Microsoft Defender Elevation of Privilege Vulnerability

Windows Bluetooth Driver Elevation of Privilege Vulnerability

Windows Point-to-Point Protocol over Ethernet (PPPoE) Elevation of Privilege Vulnerability

Microsoft SQL Server Remote Code Execution Vulnerability

Service Fabric Explorer Spoofing Vulnerability

Azure Machine Learning Compute Instance Information Disclosure Vulnerability

Visual Studio Remote Code Execution Vulnerability

Microsoft Defender for IoT Elevation of Privilege Vulnerability

Print 3D Remote Code Execution Vulnerability

3D Builder Remote Code Execution Vulnerability

Windows Common Log File System Driver Elevation of Privilege Vulnerability

Microsoft ODBC and OLE DB Remote Code Execution Vulnerability

Microsoft Edge (Chromium-based) Remote Code Execution Vulnerability

Chromium: CVE-2023-2312 Use after free in Offline

An issue was discovered in the Linux kernel through 6.2.0-rc2. drivers/tty/vcc.c has a race condition and resultant use-after-free if a physically proximate attacker removes a VCC device while calling open() aka a race condition between vcc_open() and vcc_remove().

In the Linux kernel before 5.15.13 drivers/net/ethernet/mellanox/mlx5/core/steering/dr_domain.c misinterprets the mlx5_get_uars_page return value (expects it to be NULL in the error case whereas it is actually an error pointer).

In the Linux kernel before 6.2 mm/memory-tiers.c misinterprets the alloc_memory_type return value (expects it to be NULL in the error case whereas it is actually an error pointer). NOTE: this is disputed by third parties because there are no realistic cases in which a user can cause the alloc_memory_type error case to be reached.