Threats Tagged 'cve-2026-46215'
View all threats tagged with 'cve-2026-46215'. 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-46215'
Click on any threat for detailed analysis and mitigation recommendations
Red Hat Security Advisory: kernel security, bug fix, and enhancement updateCVE-2025-71113 0 This Red Hat security advisory addresses multiple vulnerabilities in the Linux kernel packages for Red Hat Enterprise Linux 10. The issues include memory initialization flaws, denial of service due to memory leaks, use-after-free bugs, and race conditions across various kernel subsystems such as crypto, TPM, flex_proportions, cxl/port, xfrm, fanotify, DRM, ice, Bluetooth, and CAN BCM. The update also includes bug fixes and enhancements unrelated to security. The advisory rates the security impact as Important and requires a system reboot after applying the update. Join the discussion | GCVE Database | 07/21/2026, 18:24:11 UTC Added: 07/22/2026, 00:11:33 UTC |
In the Linux kernel, the following vulnerability has been resolved: drm: Set old handle to NULL before prime swap in change_handle There was a… (CVE-2026-46215)CVE-2026-46215 0 In the Linux kernel, the following vulnerability has been resolved: drm: Set old handle to NULL before prime swap in change_handle There was a potential race condition in change_handle. The ioctl briefly had a single object with two idr entries; a concurrent gem_close could delete the object and remove one of the handles while leaving the other one dangling, which could subsequently be dereferenced for a use-after-free. To fix this, do the same dance that gem_close itself does. (f6cd7daecff5 drm: Release driver references to handle before making it available again) First idr_replace the old handle to NULL. Later, if the prime operations are successful, actually close it. create_tail required a similar dance to avoid a similar problem. (bd46cece51a3 drm/gem: Fix race in drm_gem_handle_create_tail()) It idr_allocs the new handle with NULL, then swaps in the correct object later to avoid races. We don't need to do that here, since the only operations that could race are drm_prime, and change_handle holds the prime lock for the entire duration. v2: cleanups of error paths Join the discussion | GCVE Database | 05/28/2026, 12:30:33 UTC Added: 07/10/2026, 09:24:59 UTC |
Showing 1 to 2 of 2 results