NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
604 matching advisories · page 11 of 21Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2025-21827 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface() The documentation fo… linux · linux_kernel 2025-03-06 medium6.5 CVE-2025-20649 In Bluetooth Stack SW, there is a possible information disclosure due to a missing permission check. mediatek · software_development_kit, openwrt · openwrt 2025-03-03 medium6.5 CVE-2025-20647 In Modem, there is a possible system crash due to a missing bounds check. mediatek · nr12a, mediatek · nr13, mediatek · nr15 +1 2025-03-03 critical9.8 CVE-2025-20646 In wlan AP FW, there is a possible out of bounds write due to improper input validation. mediatek · software_development_kit 2025-03-03 medium6.5 CVE-2025-20644 In Modem, there is a possible memory corruption due to incorrect error handling. mediatek · nr15, mediatek · nr16 2025-03-03 medium5.5 CVE-2022-49517 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: Fix missing of_node_put in mt2701_wm8960_machine_probe This node pointer is… linux · linux_kernel 2025-02-26 medium5.5 CVE-2022-49514 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: Fix error handling in mt8173_max98090_dev_probe Call of_node_put(platform_n… linux · linux_kernel 2025-02-26 medium5.5 CVE-2022-49506 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Add vblank register/unregister callback functions We encountered a kernel pan… linux · linux_kernel 2025-02-26 medium5.5 CVE-2022-49496 In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: prevent kernel crash when rmmod mtk-vcodec-dec.ko If the driver su… linux · linux_kernel 2025-02-26 medium5.5 CVE-2022-49454 In the Linux kernel, the following vulnerability has been resolved: PCI: mediatek: Fix refcount leak in mtk_pcie_subsys_powerup() The of_find_compatible_node()… linux · linux_kernel 2025-02-26 medium5.5 CVE-2022-49427 In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Remove clk_disable in mtk_iommu_remove After the commit b34ea31fe013 ("iomm… linux · linux_kernel 2025-02-26 medium5.5 CVE-2022-49424 In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Fix NULL pointer dereference when printing dev_name When larbdev is NULL (i… linux · linux_kernel 2025-02-26 medium5.5 CVE-2022-49244 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8192-mt6359: Fix error handling in mt8192_mt6359_dev_probe The device_nod… linux · linux_kernel 2025-02-26 medium5.5 CVE-2022-49240 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8195: Fix error handling in mt8195_mt6359_rt1019_rt5682_dev_probe The dev… linux · linux_kernel 2025-02-26 medium5.5 CVE-2022-49161 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: Fix error handling in mt8183_da7219_max98357_dev_probe The device_node poin… linux · linux_kernel 2025-02-26 medium5.5 CVE-2022-49108 In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: Fix memory leaks on probe Handle the error branches to free memory where req… linux · linux_kernel 2025-02-26 high7.5 CVE-2025-20637 In network HW, there is a possible system hang due to an uncaught exception. mediatek · software_development_kit 2025-02-03 critical9.8 CVE-2025-20634 In Modem, there is a possible out of bounds write due to a missing bounds check. mediatek · nr16, mediatek · nr17, mediatek · nr17r 2025-02-03 high8.8 CVE-2025-20633 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit 2025-02-03 high7.8 CVE-2025-20632 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit 2025-02-03 high7.8 CVE-2025-20631 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit 2025-02-03 medium5.3 CVE-2024-20147 In Bluetooth FW, there is a possible reachable assertion due to improper exception handling. linuxfoundation · yocto, mediatek · software_development_kit, google · android +1 2025-02-03 high7.8 CVE-2024-57926 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Set private->all_drm_private[i]->drm to NULL if mtk_drm_bind returns err The … linux · linux_kernel 2025-01-19 high7.8 CVE-2024-56757 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: mediatek: add intf release flow when usb disconnect MediaTek claim an spe… linux · linux_kernel 2025-01-06 high8.8 CVE-2024-20154 In Modem, there is a possible out of bounds write due to a missing bounds check. mediatek · lr12a, mediatek · lr13, mediatek · nr16.r1.mp +2 2025-01-06 high7.5 CVE-2024-20153 In wlan STA, there is a possible way to trick a client to connect to an AP with spoofed SSID. linuxfoundation · yocto, mediatek · software_development_kit, google · android 2025-01-06 medium4.4 CVE-2024-20152 In wlan STA driver, there is a possible reachable assertion due to improper exception handling. linuxfoundation · yocto, mediatek · software_development_kit, google · android +1 2025-01-06 medium6.7 CVE-2024-20151 In Modem, there is a possible out of bounds write due to an incorrect bounds check. mediatek · nr16, mediatek · nr17 2025-01-06 high7.5 CVE-2024-20150 In Modem, there is a possible system crash due to a logic error. mediatek · lr12a, mediatek · lr13, mediatek · nr15 +2 2025-01-06 high7.5 CVE-2024-20149 In Modem, there is a possible system crash due to improper input validation. mediatek · lr12, mediatek · lr13, mediatek · nr15 +3 2025-01-06

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.