Answer in brief
CVE-2026-46093 records a High severity (CVSS 7.8) security vulnerability in CVE-2026-46093. The source record does not mark it as known exploited. No package mapping is present, so exposure must be confirmed against the affected product and deployment inventory.
Review the upstream advisory, identify the affected product in your inventory, and apply the vendor update when one is available.
Vulnerability describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-46093 as known exploited; continue to monitor the source for status changes. This is a product-level record in the current feed, not a package-level dependency mapping.
Affected software not mapped. Review the upstream record for vendor-specific product and version guidance.
Answer in brief
CVE-2026-46093 records a High severity (CVSS 7.8) security vulnerability in CVE-2026-46093. The source record does not mark it as known exploited. No package mapping is present, so exposure must be confirmed against the affected product and deployment inventory.
Review the upstream advisory, identify the affected product in your inventory, and apply the vendor update when one is available.
Vulnerability describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-46093 as known exploited; continue to monitor the source for status changes. This is a product-level record in the current feed, not a package-level dependency mapping.
Affected software not mapped. Review the upstream record for vendor-specific product and version guidance.
In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: take vmap_purge_lock in shrinker decay_va_pool_node() can be invoked concurrently from two paths: __purge_vmap_area_lazy() when pools are being purged, and the shrinker via vmap_node_shrink_scan(). However, decay_va_pool_node() is not safe to run concurrently, and the shrinker path currently lacks serialization, leading to races and possible leaks. Protect decay_va_pool_node() by taking vmap_purge_lock in the shrinker path to ensure serialization with purge users.
Reported by NVD (nvd).
CVE-2026-46093 records a High severity (CVSS 7.8) security vulnerability in CVE-2026-46093. The source record does not mark it as known exploited. No package mapping is present, so exposure must be confirmed against the affected product and deployment inventory.
The source record does not mark it as known exploited.
Confirm whether the product or interface named by this advisory exists in your inventory.
HOL Guard can help your team monitor supply-chain activity while the upstream record is clarified.
Explore HOL GuardIn the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: take vmap_purge_lock in shrinker decay_va_pool_node() can be invoked concurrently from two paths: __purge_vmap_area_lazy() when pools are being purged, and the shrinker via vmap_node_shrink_scan(). However, decay_va_pool_node() is not safe to run concurrently, and the shrinker path currently lacks serialization, leading to races and possible leaks. Protect decay_va_pool_node() by taking vmap_purge_lock in the shrinker path to ensure serialization with purge users.
Reported by NVD (nvd).
CVE-2026-46093 records a High severity (CVSS 7.8) security vulnerability in CVE-2026-46093. The source record does not mark it as known exploited. No package mapping is present, so exposure must be confirmed against the affected product and deployment inventory.
The source record does not mark it as known exploited.
Confirm whether the product or interface named by this advisory exists in your inventory.
HOL Guard can help your team monitor supply-chain activity while the upstream record is clarified.
Explore HOL Guard