NetSight

Security Dashboard

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

Reset
4,323 matching advisories · page 7 of 145Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2025-38377 In the Linux kernel, the following vulnerability has been resolved: rose: fix dangling neighbour pointers in rose_rt_device_down() There are two bugs in rose_r… linux · linux_kernel, debian · debian_linux 2025-07-25 high8.4 CVE-2025-38375 In the Linux kernel, the following vulnerability has been resolved: virtio-net: ensure the received length does not exceed allocated size In xdp_linearize_page… linux · linux_kernel, debian · debian_linux 2025-07-25 high7.8 CVE-2025-38352 Linux Kernel Time-of-Check Time-of-Use (TOCTOU) Race Condition VulnerabilityExploited linux · linux_kernel, debian · debian_linux 2025-07-22 high7.8 CVE-2025-38350 In the Linux kernel, the following vulnerability has been resolved: net/sched: Always pass notifications when child class becomes empty Certain classful qdiscs… linux · linux_kernel, debian · debian_linux 2025-07-19 high8.8 CVE-2025-6558 Google Chromium ANGLE and GPU Improper Input Validation VulnerabilityExploited google · chrome, debian · debian_linux, apple · safari +7 2025-07-15 high7.8 CVE-2025-38348 In the Linux kernel, the following vulnerability has been resolved: wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback() Robert Morris reported: |If … linux · linux_kernel, debian · debian_linux 2025-07-10 high7.8 CVE-2025-38346 In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix UAF when lookup kallsym after ftrace disabled The following issue happens with … linux · linux_kernel, debian · debian_linux 2025-07-10 high7.0 CVE-2025-38342 In the Linux kernel, the following vulnerability has been resolved: software node: Correct a OOB check in software_node_get_reference_args() software_node_get_… linux · linux_kernel, debian · debian_linux 2025-07-10 high7.5 CVE-2025-38331 In the Linux kernel, the following vulnerability has been resolved: net: ethernet: cortina: Use TOE/TSO on all TCP It is desireable to push the hardware accele… linux · linux_kernel, debian · debian_linux 2025-07-10 high7.8 CVE-2025-38323 In the Linux kernel, the following vulnerability has been resolved: net: atm: add lec_mutex syzbot found its way in net/atm/lec.c, and found an error path in l… linux · linux_kernel, debian · debian_linux 2025-07-10 high7.1 CVE-2025-38320 In the Linux kernel, the following vulnerability has been resolved: arm64/ptrace: Fix stack-out-of-bounds read in regs_get_kernel_stack_nth() KASAN reports a s… linux · linux_kernel, debian · debian_linux 2025-07-10 high7.8 CVE-2025-38313 In the Linux kernel, the following vulnerability has been resolved: bus: fsl-mc: fix double-free on mc_dev The blamed commit tried to simplify how the dealloca… linux · linux_kernel, debian · debian_linux 2025-07-10 high7.8 CVE-2025-38298 In the Linux kernel, the following vulnerability has been resolved: EDAC/skx_common: Fix general protection fault After loading i10nm_edac (which automatically… linux · linux_kernel, debian · debian_linux 2025-07-10 high8.8 CVE-2025-38293 In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix node corruption in ar->arvifs list In current WLAN recovery code flow, at… linux · linux_kernel, debian · debian_linux 2025-07-10 high7.1 CVE-2025-38286 In the Linux kernel, the following vulnerability has been resolved: pinctrl: at91: Fix possible out-of-boundary access at91_gpio_probe() doesn't check that giv… linux · linux_kernel, debian · debian_linux 2025-07-10 high7.8 CVE-2025-38280 In the Linux kernel, the following vulnerability has been resolved: bpf: Avoid __bpf_prog_ret0_warn when jit fails syzkaller reported an issue: WARNING: CPU: 3… linux · linux_kernel, debian · debian_linux 2025-07-10 high7.8 CVE-2025-38273 In the Linux kernel, the following vulnerability has been resolved: net: tipc: fix refcount warning in tipc_aead_encrypt syzbot reported a refcount warning [1]… linux · linux_kernel, debian · debian_linux 2025-07-10 high7.8 CVE-2025-38262 In the Linux kernel, the following vulnerability has been resolved: tty: serial: uartlite: register uart driver in init When two instances of uart devices are … linux · linux_kernel, debian · debian_linux 2025-07-09 high7.8 CVE-2025-38259 In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: wcd9335: Fix missing free of regulator supplies Driver gets and enables all r… linux · linux_kernel, debian · debian_linux 2025-07-09 high7.3 CVE-2025-38257 In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Prevent overflow in size calculation for memdup_user() Number of apqn target lis… linux · linux_kernel, debian · debian_linux 2025-07-09 high7.1 CVE-2025-38249 In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Fix out-of-bounds read in snd_usb_get_audioformat_uac3() In snd_usb_get_au… linux · linux_kernel, debian · debian_linux 2025-07-09 high7.8 CVE-2025-38245 In the Linux kernel, the following vulnerability has been resolved: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). linux · linux_kernel, debian · debian_linux 2025-07-09 high7.3 CVE-2025-38239 In the Linux kernel, the following vulnerability has been resolved: scsi: megaraid_sas: Fix invalid node index On a system with DRAM interleave enabled, out-of… linux · linux_kernel, debian · debian_linux 2025-07-09 high8.0 CVE-2025-48384 Git Link Following VulnerabilityExploited git-scm · git, debian · debian_linux, apple · xcode 2025-07-08 high7.8 CVE-2025-38236 In the Linux kernel, the following vulnerability has been resolved: af_unix: Don't leave consecutive consumed OOB skbs. linux · linux_kernel, debian · debian_linux 2025-07-08 high7.8 CVE-2025-38230 In the Linux kernel, the following vulnerability has been resolved: jfs: validate AG parameters in dbMount() to prevent crashes Validate db_agheight, db_agwidt… linux · linux_kernel, debian · debian_linux 2025-07-04 high7.8 CVE-2025-38227 In the Linux kernel, the following vulnerability has been resolved: media: vidtv: Terminating the subsequent process of initialization failure syzbot reported … linux · linux_kernel, debian · debian_linux 2025-07-04 high7.8 CVE-2025-38226 In the Linux kernel, the following vulnerability has been resolved: media: vivid: Change the siize of the composing syzkaller found a bug: BUG: KASAN: vmalloc-… linux · linux_kernel, debian · debian_linux 2025-07-04 high7.8 CVE-2025-38218 In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on sit_bitmap_size w/ below testcase, resize will generate a c… linux · linux_kernel, debian · debian_linux 2025-07-04 high7.8 CVE-2025-38212 In the Linux kernel, the following vulnerability has been resolved: ipc: fix to protect IPCS lookups using RCU syzbot reported that it discovered a use-after-f… linux · linux_kernel, debian · debian_linux 2025-07-04

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.