NetSight

Security Dashboard

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

Reset
604 matching advisories · page 9 of 21Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2022-50439 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8173: Enable IRQ when pdata is ready If the device does not come straight… linux · linux_kernel 2025-10-01 high8.4 CVE-2025-39882 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: fix potential OF node use-after-free The for_each_child_of_node() helper drop… linux · linux_kernel 2025-09-23 medium5.5 CVE-2023-53425 In the Linux kernel, the following vulnerability has been resolved: media: platform: mediatek: vpu: fix NULL ptr dereference If pdev is NULL, then it is still … linux · linux_kernel 2025-09-18 medium5.5 CVE-2023-53424 In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: fix of_iomap memory leak Smatch reports: drivers/clk/mediatek/clk-mtk.c:583 … linux · linux_kernel 2025-09-18 medium5.5 CVE-2023-53389 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: dp: Only trigger DRM HPD events if bridge is attached The MediaTek DisplayPor… linux · linux_kernel 2025-09-18 high7.8 CVE-2023-53388 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Clean dangling pointer on bind error path mtk_drm_bind() can fail, in which c… linux · linux_kernel 2025-09-18 medium5.5 CVE-2022-50392 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8183: fix refcount leak in mt8183_mt6358_ts3a227_max98357_dev_probe() The… linux · linux_kernel 2025-09-18 medium5.5 CVE-2022-50383 In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Can't set dst buffer to done when lat decode error Core thread wil… linux · linux_kernel 2025-09-18 medium5.5 CVE-2023-53325 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: dp: Change logging to dev for mtk_dp_aux_transfer() Change logging from drm_{… linux · linux_kernel 2025-09-16 medium5.5 CVE-2025-39807 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Add error handling for old state CRTC in atomic_disable Introduce error handl… linux · linux_kernel 2025-09-16 high7.8 CVE-2023-53274 In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: mt8183: Add back SSPM related clocks This reverts commit 860690a93ef23b567f7… linux · linux_kernel 2025-09-16 medium5.5 CVE-2022-50236 In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Fix crash on isr after kexec() If the system is rebooted via isr(), the IRQ… linux · linux_kernel 2025-09-15 high8.8 CVE-2025-20708 In Modem, there is a possible out of bounds write due to an incorrect bounds check. mediatek · nr15, mediatek · nr16, mediatek · nr17 +1 2025-09-01 high8.0 CVE-2025-20704 In Modem, there is a possible out of bounds write due to a missing bounds check. mediatek · nr17, mediatek · nr17r 2025-09-01 medium6.5 CVE-2025-20703 In Modem, there is a possible out of bounds read due to an incorrect bounds check. mediatek · nr15, mediatek · nr16, mediatek · nr17 +1 2025-09-01 high7.1 CVE-2025-38662 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8365-dai-i2s: pass correct size to mt8365_dai_set_priv Given mt8365_dai_s… linux · linux_kernel 2025-08-22 medium5.5 CVE-2025-38299 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8195: Set ETDM1/2 IN/OUT to COMP_DUMMY() ETDM2_IN_BE and ETDM1_OUT_BE are… linux · linux_kernel 2025-07-10 medium5.5 CVE-2025-38266 In the Linux kernel, the following vulnerability has been resolved: pinctrl: mediatek: eint: Fix invalid pointer dereference for v1 platforms Commit 3ef9f710ef… linux · linux_kernel 2025-07-10 medium6.5 CVE-2025-20695 In Bluetooth FW, there is a possible system crash due to an uncaught exception. mediatek · software_development_kit, google · android, openwrt · openwrt 2025-07-08 medium6.5 CVE-2025-20694 In Bluetooth FW, there is a possible system crash due to an uncaught exception. mediatek · software_development_kit, google · android, openwrt · openwrt 2025-07-08 medium6.5 CVE-2025-20693 In wlan STA driver, there is a possible out of bounds read due to an incorrect bounds check. linuxfoundation · yocto, mediatek · software_development_kit, google · android +1 2025-07-08 medium5.5 CVE-2025-20692 In wlan AP driver, there is a possible out of bounds read due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-07-08 medium5.5 CVE-2025-20691 In wlan AP driver, there is a possible out of bounds read due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-07-08 medium5.5 CVE-2025-20690 In wlan AP driver, there is a possible out of bounds read due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-07-08 medium5.5 CVE-2025-20689 In wlan AP driver, there is a possible out of bounds read due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-07-08 medium5.5 CVE-2025-20688 In wlan AP driver, there is a possible out of bounds read due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-07-08 medium5.5 CVE-2025-20687 In Bluetooth driver, there is a possible out of bounds read due to an incorrect bounds check. mediatek · nbiot_sdk 2025-07-08 high8.8 CVE-2025-20686 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-07-08 high8.8 CVE-2025-20685 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-07-08 critical9.8 CVE-2025-20684 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit 2025-07-08

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.