Vulnerabilities
All
My stack
Known exploited
Public exploit
Critical (9+)
Likely exploited (EPSS ≥ 50%)
Changed, 24 h
New, 24 h
Sort:
risk
modified
published
CVSS
EPSS
| CVE | CVSS | EPSS | Vendor, product | Description | Modified |
|---|---|---|---|---|---|
| CVE-2025-58289 | 5.5 medium | 0.00% | huawei, harmonyos | Vulnerability of improper exception handling in the print module. Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58293 | 5.5 medium | 0.00% | huawei, harmonyos | Vulnerability of improper exception handling in the print module. Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58300 | 5.5 medium | 0.00% | huawei, harmonyos | Buffer overflow vulnerability in the device management module. Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58301 | 5.5 medium | 0.00% | huawei, harmonyos | Buffer overflow vulnerability in the device management module. Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58294 | 5.5 medium | 0.00% | huawei, harmonyos | Permission control vulnerability in the print module. Impact: Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2025-58307 | 5.5 medium | 0.00% | huawei, harmonyos | UAF vulnerability in the screen recording framework module. Impact: Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58310 | 5.5 medium | 0.00% | huawei, harmonyos | Permission control vulnerability in the distributed component. Impact: Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2025-58312 | 5.5 medium | 0.00% | huawei, harmonyos | Permission control vulnerability in the App Lock module. Impact: Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58315 | 5.5 medium | 0.00% | huawei, harmonyos | Permission control vulnerability in the Wi-Fi module. Impact: Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2025-58316 | 5.5 medium | 0.00% | huawei, harmonyos | DoS vulnerability in the video-related system service module. Impact: Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-64311 | 5.5 medium | 0.00% | huawei, harmonyos | Permission control vulnerability in the Notepad module. Impact: Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2025-64313 | 5.5 medium | 0.00% | huawei, harmonyos | Denial of service (DoS) vulnerability in the office service. Impact: Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58304 | 5.5 medium | 0.00% | huawei, harmonyos | Permission control vulnerability in the file management module. Impact: Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2025-58305 | 5.5 medium | 0.00% | huawei, harmonyos | Identity authentication bypass vulnerability in the Gallery app. Impact: Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2026-34866 | 5.1 medium | 0.00% | huawei, harmonyos | Out-of-bounds write vulnerability in the WEB module.Impact: Successful exploitation of this vulnerability will affect availability and confidentiality. | Mon 26 Oct |
| CVE-2026-34849 | 4.7 medium | 0.00% | huawei, harmonyos | UAF vulnerability in the screen management module. Impact: Successful exploitation of this vulnerability may affect availability. | Mon 26 Oct |
| CVE-2026-34861 | 4.7 medium | 0.00% | huawei, harmonyos | Race condition vulnerability in the thermal management module. Impact: Successful exploitation of this vulnerability may affect availability. | Mon 26 Oct |
| CVE-2026-34862 | 4.7 medium | 0.00% | huawei, harmonyos | Race condition vulnerability in the power consumption statistics module. Impact: Successful exploitation of this vulnerability may affect availability. | Mon 26 Oct |
| CVE-2026-31466 | 4.7 medium | 0.00% | linux, linux_kernel | In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: fix folio isn't locked in softleaf_to_folio() On arm64 server, we found folio that get from migration entry isn't locked in softleaf_to_folio(). This issue triggers when mTHP splitting and zap_nonpresent_ptes() races, and the root cause is lack of memory barrier in softleaf_to_folio(). The race is as follows: CPU0 CPU1 deferred_split_scan() zap_nonpresent_ptes() lock folio split_folio() unmap_folio() change ptes to migration entries __split_folio_to_order() softleaf_to_folio() set flags(including PG_locked) for tail pages folio = pfn_folio(softleaf_to_pfn(entry)) smp_wmb() VM_WARN_ON_ONCE(!folio_test_locked(folio)) prep_compound_page() for tail pages In __split_folio_to_order(), smp_wmb() guarantees page flags of tail pages are visible before the tail page becomes non-compound. smp_wmb() should be paired with smp_rmb() in softleaf_to_folio(), which is missed. As a result, if zap_nonpresent_ptes() accesses migration entry that stores tail pfn, softleaf_to_folio() may see the updated compound_head of tail page before page->flags. This issue will trigger VM_WARN_ON_ONCE() in pfn_swap_entry_folio() because of the race between folio split and zap_nonpresent_ptes() leading to a folio incorrectly undergoing modification without a folio lock being held. This is a BUG_ON() before commit 93976a20345b ("mm: eliminate further swapops predicates"), which in merged in v6.19-rc1. To fix it, add missing smp_rmb() if the softleaf entry is migration entry in softleaf_to_folio() and softleaf_to_page(). [[email protected]: update function name and comments] | 15 Oct |
| CVE-2026-34858 | 4.1 medium | 0.00% | huawei, harmonyos | UAF vulnerability in the communication module. Impact: Successful exploitation of this vulnerability may affect availability. | Mon 26 Oct |
| CVE-2026-65200 | 3.5 low | 0.00% | no CPE yet | The openUBMC device-management process parses PLDM-over-MCTP and NCSI-over-MCTP responses from on-bus devices, and three response parsers in the shared transport libraries subtract a fixed header or reserved-field size from a device-supplied response length without a lower-bound check. An undersized response wraps the unsigned length difference to a very large value, and the parser then reads far past the response buffer. The affected code sits in the base (non-vendor) PLDM control class and the Huawei NCSI driver, so it is reachable for any PLDM endpoint or Huawei NIC on the internal management bus, unlike the vendor-specific wangxun parser tracked separately. | 16 Oct |
| CVE-2025-58308 | 3.3 low | 0.00% | huawei, harmonyos | Vulnerability of improper criterion security check in the call module. Impact: Successful exploitation of this vulnerability may cause features to perform abnormally. | 8 Oct |
| CVE-2026-80773 | unscored | 0.00% | no CPE yet | In the Linux kernel, the following vulnerability has been resolved: HID: huawei: fix missing hid_is_usb() check to_usb_interface() can only be used on a hid_device whose parent is really USB; uhid can create devices that identify as being on BUS_USB, but don't actually have a USB parent. Fix the use of to_usb_interface() without a hid_is_usb() check. I have verified that it is currently possible to trigger a kernel splat due to this bug in an ASAN build, and that this commit fixes the issue. | 19 Oct |
73 of 73 · Previous
Download these 73 as CSV · subscribe to this list.
EPSS scores: 2026-10-27. NVD cursor: 2026-10-28 20:19. The News page shows only notable CVEs (KEV, your stack, new criticals, EPSS over 50%, or active exploitation per SSVC); this table has all of them.