Threats Tagged 'cve-2025-40292'
View all threats tagged with 'cve-2025-40292'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2025-40292'
Click on any threat for detailed analysis and mitigation recommendations
A vulnerability in the Linux kernel's virtio-net driver involves an incorrect length check when handling large packets. The issue arises because the buffer length check was not updated after changes to how buffer sizes are allocated based on negotiated MTU, potentially leading to a NULL page pointer dereference. This flaw can cause denial of service and compromise confidentiality, integrity, and availability. The vulnerability is tracked as CVE-2025-40292 and is rated high severity. Join the discussion | GCVE Database | 12/08/2025, 03:31:00 UTC Added: 07/30/2026, 15:50:44 UTC |
In the Linux kernel, the following vulnerability has been resolved: virtio-net: fix received length check in big packets Since commit 4959aebba8c0 ("virtio-net: use mtu size as buffer length for big packets"), when guest gso is off, the allocated size for big packets is not MAX_SKB_FRAGS * PAGE_SIZE anymore but depends on negotiated MTU. The number of allocated frags for big packets is stored in vi->big_packets_num_skbfrags. Because the host announced buffer length can be malicious (e.g. the host vhost_net driver's get_rx_bufs is modified to announce incorrect length), we need a check in virtio_net receive path. Currently, the check is not adapted to the new change which can lead to NULL page pointer dereference in the below while loop when receiving length that is larger than the allocated one. This commit fixes the received length check corresponding to the new change. Join the discussion | GCVE Database | 12/08/2025, 01:16:00 UTC Added: 07/18/2026, 11:35:08 UTC |
Showing 1 to 2 of 2 results