NetSight

Security Dashboard

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

Reset
4,323 matching advisories · page 6 of 145Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2025-38478 In the Linux kernel, the following vulnerability has been resolved: comedi: Fix initialization of data for instructions that write to subdevice Some Comedi sub… linux · linux_kernel, debian · debian_linux 2025-07-28 high7.8 CVE-2025-38477 In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_qfq: Fix race condition on qfq_aggregate A race condition can occur when 'ag… linux · linux_kernel, debian · debian_linux 2025-07-28 high7.8 CVE-2025-38470 In the Linux kernel, the following vulnerability has been resolved: net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime Assuming the … linux · linux_kernel, debian · debian_linux 2025-07-28 high7.8 CVE-2025-38466 In the Linux kernel, the following vulnerability has been resolved: perf: Revert to requiring CAP_SYS_ADMIN for uprobes Jann reports that uprobes can be used d… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38464 In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_conn_close(). linux · linux_kernel, debian · debian_linux 2025-07-25 high7.0 CVE-2025-38461 In the Linux kernel, the following vulnerability has been resolved: vsock: Fix transport_* TOCTOU Transport assignment may race with module unload. linux · linux_kernel, debian · debian_linux 2025-07-25 high7.0 CVE-2025-38460 In the Linux kernel, the following vulnerability has been resolved: atm: clip: Fix potential null-ptr-deref in to_atmarpd(). linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38459 In the Linux kernel, the following vulnerability has been resolved: atm: clip: Fix infinite recursive call of clip_push(). linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38456 In the Linux kernel, the following vulnerability has been resolved: ipmi:msghandler: Fix potential memory corruption in ipmi_create_user() The "intf" list iter… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38455 In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight Reject migrati… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.1 CVE-2025-38445 In the Linux kernel, the following vulnerability has been resolved: md/raid1: Fix stack memory use after return in raid1_reshape In the raid1_reshape function,… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38443 In the Linux kernel, the following vulnerability has been resolved: nbd: fix uaf in nbd_genl_connect() error path There is a use-after-free issue in nbd: block… linux · linux_kernel, debian · debian_linux 2025-07-25 high8.8 CVE-2025-38437 In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix potential use-after-free in oplock/lease break ack If ksmbd_iov_pin_rsp return e… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38428 In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - check record size in ims_pcu_flash_firmware() The "len" variable comes fro… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38425 In the Linux kernel, the following vulnerability has been resolved: i2c: tegra: check msg length in SMBUS block read For SMBUS block read, do not continue to r… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38424 In the Linux kernel, the following vulnerability has been resolved: perf: Fix sample vs do_exit() Baisheng Gao reported an ARM64 crash, which Mark decoded as b… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38422 In the Linux kernel, the following vulnerability has been resolved: net: lan743x: Modify the EEPROM and OTP size for PCI1xxxx devices Maximum OTP and EEPROM si… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38416 In the Linux kernel, the following vulnerability has been resolved: NFC: nci: uart: Set tty->disc_data only in success path Setting tty->disc_data before openi… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38415 In the Linux kernel, the following vulnerability has been resolved: Squashfs: check return result of sb_min_blocksize Syzkaller reports an "UBSAN: shift-out-of… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38412 In the Linux kernel, the following vulnerability has been resolved: platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks After retrie… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38403 In the Linux kernel, the following vulnerability has been resolved: vsock/vmci: Clear the vmci transport packet properly when initializing it In vmci_transport… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38401 In the Linux kernel, the following vulnerability has been resolved: mtk-sd: Prevent memory corruption from DMA map failure If msdc_prepare_data() fails to map … linux · linux_kernel, debian · debian_linux 2025-07-25 high7.5 CVE-2025-38399 In the Linux kernel, the following vulnerability has been resolved: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() The function … linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38396 In the Linux kernel, the following vulnerability has been resolved: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass Export anon_inode_ma… linux · linux_kernel, debian · debian_linux 2025-07-25 high8.4 CVE-2025-38395 In the Linux kernel, the following vulnerability has been resolved: regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods drvdata::gpiods is suppose… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.5 CVE-2025-38393 In the Linux kernel, the following vulnerability has been resolved: NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN We found a few different systems hung up… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38389 In the Linux kernel, the following vulnerability has been resolved: drm/i915/gt: Fix timeline left held on VMA alloc error The following error has been reporte… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38386 In the Linux kernel, the following vulnerability has been resolved: ACPICA: Refuse to evaluate a method if arguments are missing As reported in [1], a platform… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38385 In the Linux kernel, the following vulnerability has been resolved: net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect Remove redundant netif… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38382 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix iteration of extrefs during log replay At __inode_add_ref() when processing extr… linux · linux_kernel, debian · debian_linux 2025-07-25

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.