Search Results (34191 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2023-36767 1 Microsoft 3 365 Apps, Office, Office Long Term Servicing Channel 2025-10-30 4.3 Medium
Microsoft Office Security Feature Bypass Vulnerability
CVE-2023-36801 1 Microsoft 5 Windows Server 2008, Windows Server 2012, Windows Server 2016 and 2 more 2025-10-30 5.3 Medium
DHCP Server Service Information Disclosure Vulnerability
CVE-2023-36804 1 Microsoft 12 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 9 more 2025-10-30 7.8 High
Windows GDI Elevation of Privilege Vulnerability
CVE-2023-36805 1 Microsoft 11 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 8 more 2025-10-30 7 High
Windows MSHTML Platform Security Feature Bypass Vulnerability
CVE-2023-38139 1 Microsoft 12 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 9 more 2025-10-30 7.8 High
Windows Kernel Elevation of Privilege Vulnerability
CVE-2023-38140 1 Microsoft 8 Windows 10 1607, Windows 10 1809, Windows 10 21h2 and 5 more 2025-10-30 5.5 Medium
Windows Kernel Information Disclosure Vulnerability
CVE-2023-38141 1 Microsoft 12 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 9 more 2025-10-30 7.8 High
Windows Kernel Elevation of Privilege Vulnerability
CVE-2023-38142 1 Microsoft 12 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 9 more 2025-10-30 7.8 High
Windows Kernel Elevation of Privilege Vulnerability
CVE-2023-38143 1 Microsoft 12 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 9 more 2025-10-30 7.8 High
Windows Common Log File System Driver Elevation of Privilege Vulnerability
CVE-2023-38144 1 Microsoft 12 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 9 more 2025-10-30 7.8 High
Windows Common Log File System Driver Elevation of Privilege Vulnerability
CVE-2023-38146 1 Microsoft 2 Windows 11 21h2, Windows 11 22h2 2025-10-30 8.8 High
Windows Themes Remote Code Execution Vulnerability
CVE-2023-38147 1 Microsoft 10 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 7 more 2025-10-30 8.8 High
Windows Miracast Wireless Display Remote Code Execution Vulnerability
CVE-2023-38148 1 Microsoft 4 Windows 10 21h2, Windows 10 22h2, Windows 11 21h2 and 1 more 2025-10-30 8.8 High
Internet Connection Sharing (ICS) Remote Code Execution Vulnerability
CVE-2023-38149 1 Microsoft 12 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 9 more 2025-10-30 7.5 High
Windows TCP/IP Denial of Service Vulnerability
CVE-2023-38150 1 Microsoft 2 Windows 11 21h2, Windows 11 22h2 2025-10-30 7.8 High
Windows Kernel Elevation of Privilege Vulnerability
CVE-2023-38156 1 Microsoft 1 Azure Hdinsights 2025-10-30 7.2 High
Azure HDInsight Apache Ambari JDBC Injection Elevation of Privilege Vulnerability
CVE-2023-38161 1 Microsoft 12 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 9 more 2025-10-30 7.8 High
Windows GDI Elevation of Privilege Vulnerability
CVE-2023-33136 1 Microsoft 1 Azure Devops Server 2025-10-30 8.8 High
Azure DevOps Server Remote Code Execution Vulnerability
CVE-2023-35355 1 Microsoft 7 Windows 10 1809, Windows 10 21h2, Windows 10 22h2 and 4 more 2025-10-30 7.8 High
Windows Cloud Files Mini Filter Driver Elevation of Privilege Vulnerability
CVE-2022-49744 1 Linux 1 Linux Kernel 2025-10-30 5.5 Medium
In the Linux kernel, the following vulnerability has been resolved: mm/uffd: fix pte marker when fork() without fork event Patch series "mm: Fixes on pte markers". Patch 1 resolves the syzkiller report from Pengfei. Patch 2 further harden pte markers when used with the recent swapin error markers. The major case is we should persist a swapin error marker after fork(), so child shouldn't read a corrupted page. This patch (of 2): When fork(), dst_vma is not guaranteed to have VM_UFFD_WP even if src may have it and has pte marker installed. The warning is improper along with the comment. The right thing is to inherit the pte marker when needed, or keep the dst pte empty. A vague guess is this happened by an accident when there's the prior patch to introduce src/dst vma into this helper during the uffd-wp feature got developed and I probably messed up in the rebase, since if we replace dst_vma with src_vma the warning & comment it all makes sense too. Hugetlb did exactly the right here (copy_hugetlb_page_range()). Fix the general path. Reproducer: https://github.com/xupengfe/syzkaller_logs/blob/main/221208_115556_copy_page_range/repro.c Bugzilla report: https://bugzilla.kernel.org/show_bug.cgi?id=216808