Threats Tagged 'cve-2026-64120'
View all threats tagged with 'cve-2026-64120'. 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-2026-64120'
Click on any threat for detailed analysis and mitigation recommendations
In the Linux kernel, the following vulnerability has been resolved: net: ethtool: fix NULL pointer dereference in phy_reply_size In phy_prepare_data(), several strings such as 'name', 'drvname', 'upstream_sfp_name', and 'downstream_sfp_name' are allocated using kstrdup(). However, these allocations were not checked for failure. If kstrdup() fails for 'name', it returns NULL while the function continues. This leads to a kernel NULL pointer dereference and panic later in phy_reply_size() when it unconditionally calls strlen() on the NULL pointer. While other strings like 'upstream_sfp_name' might be checked before access in certain code paths, failing to handle these allocations consistently can lead to incomplete data reporting or hidden bugs. Fix this by adding proper NULL checks for all kstrdup() calls in phy_prepare_data() and implement a centralized error handling path using goto labels to ensure all previously allocated resources are freed on failure. Join the discussion | GCVE Database | 07/20/2026, 00:00:00 UTC Added: 07/21/2026, 19:59:03 UTC |
A NULL pointer dereference vulnerability in the Linux kernel's ethtool component was fixed. The issue occurs in the phy_prepare_data() function where memory allocation failures from kstrdup() were not checked, leading to a NULL pointer dereference and kernel panic in phy_reply_size(). This could cause a denial of service by crashing the kernel. The fix adds proper NULL checks and centralized error handling to prevent this condition. Join the discussion | GCVE Database | 07/19/2026, 18:31:52 UTC Added: 07/19/2026, 19:38:17 UTC |
Showing 1 to 2 of 2 results