---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
A use-after-free vulnerability exists in the Linux kernel's batman-adv module during the deletion of backbone claims.

Executive Summary:
A critical use-after-free vulnerability in the Linux kernel batman-adv module poses a significant risk of system instability or potential code execution.

Vulnerability Details

CVE-ID: CVE-2026-46212

Affected Software: Linux kernel

Affected Versions: See vendor advisory for affected versions

Vulnerability: This is a use-after-free memory corruption vulnerability triggered within the batadv_bla_del_backbone_claims() function. The flaw occurs when the module incorrectly handles memory references while dropping link entries from a hash list.

Business Impact

The CVSS score of 8.8 indicates a high severity risk. Successful exploitation could lead to kernel-level memory corruption, resulting in system crashes (Denial of Service) or potential arbitrary code execution, which would compromise the integrity and availability of the affected system.

Remediation Plan

Immediate Action: Apply the latest security updates provided by your Linux distribution maintainer to address the batman-adv module vulnerability.

Proactive Monitoring: Monitor system logs for kernel oops or panic messages specifically associated with the batman-adv module.

Compensating Controls: Restrict access to network configurations that utilize the B.A.T.M.A.N. advanced protocol to trusted administrative users only.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 31, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Given the high CVSS score, organizations running Linux kernels with batman-adv enabled should prioritize patching. Ensure that all kernel updates are tested in a staging environment before deployment to production systems to mitigate the risk of operational disruption.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: Linux kernel versions up to c6c8fea29769d998d94fcec9b9f14d4b52b349d3; version 2.6.38 is affected.
---END_METADATA---

Description Summary:
An integer overflow in the Linux kernel's batman-adv component can lead to out-of-bounds memory access.

Executive Summary:
A high-severity integer overflow in the Linux kernel's batman-adv module poses a risk of out-of-bounds memory read and system compromise.

Vulnerability Details

CVE-ID: CVE-2026-46198

Affected Software: Linux Kernel

Affected Versions: Linux kernel versions up to c6c8fea29769d998d94fcec9b9f14d4b52b349d3; version 2.6.38 is affected.

Vulnerability: The batadv_iv_ogm_send_to_if function suffers from an integer overflow due to a type mismatch between size checks (int) and the variable buff_pos (s16), allowing out-of-bounds reads.

Business Impact

This vulnerability could be exploited to leak sensitive kernel memory or cause a denial of service. The CVSS score of 8.8 reflects the significant risk to systems utilizing the batman-adv routing protocol.

Remediation Plan

Immediate Action: Upgrade to a kernel version that includes the fix, such as Debian trixie (6.12.90-2), forky (7.0.9-1), sid (7.0.10-1), or upstream commit 0799e5943611006b346b8813c7daf7dd5aa26bfd.

Proactive Monitoring: Monitor network traffic and system logs for unusual behavior related to the batman-adv protocol.

Compensating Controls: Isolate networks running batman-adv to prevent untrusted traffic from interacting with the vulnerable module.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 31, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Administrators of mesh networks utilizing batman-adv should prioritize updating their kernel to the versions specified above. This is essential to prevent potential information disclosure and system instability.

---METADATA---
VENDOR: AMD
PRODUCT: Zen2 Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A flaw in the AMD Zen2 op cache management allows for improper resource sharing, which may lead to instruction corruption.

Executive Summary:
Improper resource isolation in AMD Zen2 processors can result in instruction corruption, necessitating an urgent microcode or kernel-level update to ensure system integrity.

Vulnerability Details

CVE-ID: CVE-2026-46174

Affected Software: AMD Zen2 (Linux Kernel)

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability resides in the x86 CPU architecture code for AMD Zen2 processors regarding the op cache. Improper isolation of shared resources within the cache can lead to instruction corruption, which could be exploited to alter the expected execution flow of system processes.

Business Impact

With a CVSS score of 8.8, this vulnerability represents a high risk to system integrity. Instruction corruption can lead to unpredictable application behavior, bypass of security checks, or potential privilege escalation by forcing the CPU to execute unintended instructions, ultimately threatening the security of the entire operating system.

Remediation Plan

Immediate Action: Apply the latest microcode and kernel security updates released by AMD and your Linux distribution provider.

Proactive Monitoring: Monitor for unusual system crashes or inconsistent application behavior that might indicate instruction corruption.

Compensating Controls: While difficult to mitigate via network controls, ensuring that all software is signed and verified can help prevent the injection of malicious code that might exploit such hardware-level flaws.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of May 31, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Hardware-level vulnerabilities require rapid remediation via firmware or kernel patches. Administrators should monitor vendor channels for official updates and apply them as a matter of high priority to maintain the integrity of the computing environment.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
A slab-use-after-free vulnerability exists in the Linux kernel's mac80211 subsystem during radar detection work.

Executive Summary:
A high-severity use-after-free flaw in the Linux kernel's mac80211 radar detection logic can lead to system crashes or arbitrary code execution.

Vulnerability Details

CVE-ID: CVE-2026-46166

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for affected versions

Vulnerability: The ieee80211_dfs_cac_cancel function can free a channel context while it is still being iterated during radar detection, leading to a use-after-free condition.

Business Impact

Exploitation of this vulnerability could lead to system instability, crashes, or potential code execution. The CVSS score of 8.8 highlights the severity of this memory management flaw in the wireless subsystem.

Remediation Plan

Immediate Action: Apply the kernel patch available via the GitHub advisory (GHSA-pqxf-3wq6-69f8) to ensure safe list iteration.

Proactive Monitoring: Monitor system logs for kernel oops related to the mac80211 subsystem.

Compensating Controls: Disable wireless radar detection features if not required, or restrict the affected system's environment to minimize exposure to DFS-related triggers.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 31, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Wireless infrastructure administrators must prioritize applying the provided kernel patch to fix this use-after-free vulnerability. Failure to address this could lead to significant system instability and potential security compromises.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
A race condition in the Linux kernel's mac80211 fast-RX handling can lead to packet processing errors.

Executive Summary:
A high-severity concurrency issue in the Linux kernel's wireless subsystem can lead to incorrect packet processing and potential denial of service.

Vulnerability Details

CVE-ID: CVE-2026-46152

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for affected versions

Vulnerability: A static variable rx_result in ieee80211_invoke_fast_rx() is accessed concurrently, allowing callers to overwrite each other's results during parallel RX operations.

Business Impact

This flaw can result in the incorrect processing of Wi-Fi packets, potentially leading to unstable network performance or denial of service. With a CVSS score of 8.8, this vulnerability poses a risk to the reliability of wireless communication.

Remediation Plan

Immediate Action: Apply the kernel patch that converts rx_result to an automatic variable, ensuring each invocation maintains its own result.

Proactive Monitoring: Monitor wireless performance metrics and system logs for packet processing errors or driver-related errors.

Compensating Controls: If patching is unavailable, implement network-level monitoring to detect and alert on anomalous packet loss or wireless instability.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 31, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Administrators should prioritize kernel updates that resolve this concurrency flaw. Ensuring that packet processing remains isolated between parallel threads is critical for network reliability and performance.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
A Bluetooth stack vulnerability in the Linux kernel allows for out-of-bounds reads and infinite loops during specific event processing.

Executive Summary:
An out-of-bounds read vulnerability in the Linux kernel Bluetooth subsystem could lead to system crashes or sensitive information exposure.

Vulnerability Details

CVE-ID: CVE-2026-46138

Affected Software: Linux kernel

Affected Versions: See vendor advisory

Vulnerability: The flaw resides in hci_le_create_big_complete_evt(), where incorrect iteration logic over bis_handle results in out-of-bounds memory access and a potential infinite loop when processing Bluetooth LE events.

Business Impact

With a CVSS score of 8.1 (High), this vulnerability poses a risk to any system utilizing Bluetooth functionality. Successful exploitation can lead to a denial-of-service (system hang) or potentially expose sensitive memory contents, which is particularly concerning in mobile or IoT deployments.

Remediation Plan

Immediate Action: Apply the latest kernel security patches from your distribution vendor to resolve the Bluetooth event processing logic.

Proactive Monitoring: Disable Bluetooth on servers or critical systems where it is not required to eliminate the attack surface entirely.

Compensating Controls: Monitor system performance for high CPU usage or logs indicating Bluetooth driver issues.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Bluetooth-related vulnerabilities are often overlooked in server environments. Ensure that your kernel is patched and consider disabling unused Bluetooth hardware to reduce the overall attack surface.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
A vulnerability in the Linux kernel's mac80211 subsystem occurs when MLO connection preparation fails.

Executive Summary:
An improper handling of MLO connection failures in the Linux kernel's mac80211 component can lead to unexpected interface resets.

Vulnerability Details

CVE-ID: CVE-2026-46125

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for affected versions

Vulnerability: When connection preparation fails for Multi-Link Operation (MLO) connections, the wireless interface is incorrectly reset to a non-MLD state, potentially causing network connectivity issues.

Business Impact

This vulnerability can cause Denial of Service (DoS) for wireless network interfaces, impacting connectivity for affected systems. The CVSS score of 8.8 reflects the potential for significant operational disruption in wireless-dependent environments.

Remediation Plan

Immediate Action: Apply the latest security updates for the Linux kernel provided by your distribution vendor.

Proactive Monitoring: Monitor wireless interface logs for frequent resets or unexpected changes in interface configuration.

Compensating Controls: Use wired network connections where possible for mission-critical systems until a patch can be verified and deployed.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 31, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Wireless infrastructure administrators should monitor for vendor-provided kernel patches to address this interface reset issue. Promptly applying these updates will prevent potential denial-of-service scenarios in your wireless environment.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: Linux kernel stable lines including 6.6.140, 6.12.88, 6.18.30, 7.0.7, and the 7.1 release-candidate fix path.
---END_METADATA---

Description Summary:
A use-after-free vulnerability in the Linux kernel's KVM x86 shadow paging allows for potential memory corruption.

Executive Summary:
A high-severity KVM x86 shadow paging flaw can result in a use-after-free condition due to stale reverse-map entries.

Vulnerability Details

CVE-ID: CVE-2026-46113

Affected Software: Linux Kernel

Affected Versions: Linux kernel stable lines including 6.6.140, 6.12.88, 6.18.30, 7.0.7, and the 7.1 release-candidate fix path.

Vulnerability: The KVM shadow MMU incorrectly computes Guest Frame Numbers (GFNs) for direct shadow pages, leaving stale reverse-map entries after an unexpected GFN appears, leading to a use-after-free.

Business Impact

This vulnerability could be exploited to compromise the stability of virtualized environments, potentially leading to guest-to-host escapes or system crashes. With a CVSS score of 8.8, this is a critical concern for virtualization infrastructure.

Remediation Plan

Immediate Action: Update the Linux kernel to the corrected versions (6.6.140, 6.12.88, 6.18.30, 7.0.7, or 7.1-rc) immediately.

Proactive Monitoring: Monitor virtualized host logs for unexpected KVM errors or memory-related crashes.

Compensating Controls: Restrict access to KVM configuration interfaces and ensure guest isolation policies are strictly enforced.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 31, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Organizations running Linux-based virtualization hosts must prioritize these kernel updates. Ensuring the stability and security of the KVM hypervisor is essential for preventing host-level compromises.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A metadata reference count underflow in the Linux kernel's dm-thin driver could lead to memory corruption and potential system compromise.

Executive Summary:
A high-severity reference count underflow in the dm-thin metadata handling could lead to memory corruption and potential system-wide instability.

Vulnerability Details

CVE-ID: CVE-2026-46107

Affected Software: Linux kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability exists in the dm-thin (Device Mapper Thin Provisioning) driver, specifically within the rebalance_children function. An error in managing metadata reference counts leads to an underflow condition, which can cause the kernel to free memory that is still in use.

Business Impact

The CVSS score of 7.8 reflects the high risk of this vulnerability. Use-after-free and reference count underflows are critical memory corruption issues that can lead to system crashes, unauthorized data access, or arbitrary code execution by a local attacker.

Remediation Plan

Immediate Action: Apply the latest kernel security patches provided by your Linux distribution, specifically those addressing dm-thin metadata management.

Proactive Monitoring: Monitor storage-related kernel logs for any signs of metadata corruption or unexpected dm-thin performance issues.

Compensating Controls: If possible, limit the use of thin-provisioned volumes on untrusted or highly exposed systems until the patch is applied.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Storage driver vulnerabilities are extremely dangerous as they can impact data integrity at the block level. Organizations should treat this as a high-priority update, especially on systems heavily reliant on thin provisioning.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
An improper NVMe request size limitation in the Linux kernel's mpt3sas SCSI driver could lead to firmware-related issues or potential buffer overflows.

Executive Summary:
A high-severity flaw in the mpt3sas driver's handling of NVMe request sizes could potentially lead to buffer overflows or system instability when communicating with HBA hardware.

Vulnerability Details

CVE-ID: CVE-2026-46105

Affected Software: Linux kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability exists in the mpt3sas driver, which failed to adequately limit NVMe request sizes according to the HBA firmware's MDTS (Maximum Data Transfer Size) capabilities. This oversight can lead to requests that exceed the hardware's capacity, causing unpredictable behavior or potential buffer overflows.

Business Impact

A CVSS score of 7.8 highlights the risk posed by this driver flaw. Successful exploitation could lead to system crashes or potentially allow an attacker to corrupt kernel memory via the interaction with the HBA hardware, impacting both data integrity and system availability.

Remediation Plan

Immediate Action: Update to a kernel version that correctly enforces the 2 MiB limit for NVMe requests within the mpt3sas driver.

Proactive Monitoring: Check logs for hardware-related error messages or firmware communication errors during high I/O workloads.

Compensating Controls: Ensure firmware for all HBA devices is up-to-date, as this can sometimes provide additional safeguards against large I/O requests.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Driver-level vulnerabilities can often be exploited if an attacker has the ability to trigger specific I/O patterns. Organizations using mpt3sas controllers should prioritize patching to ensure that hardware communication remains within safe, validated bounds.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A vulnerability in the Linux kernel's AFS filesystem driver involves an incorrect implementation of mmap preparation.

Executive Summary:
A high-severity memory management issue in the AFS filesystem driver could lead to potential security vulnerabilities related to incorrect mmap handling.

Vulnerability Details

CVE-ID: CVE-2026-46100

Affected Software: Linux kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The issue is related to the mmap_prepare() function within the AFS filesystem driver. A previous code change introduced a flaw that necessitated a partial revert of commit 9d5403b1036c, which attempted to convert generic file mmap users but introduced a regression.

Business Impact

The CVSS score of 7.8 indicates a high severity, as improper mmap handling can often lead to memory corruption or security bypasses. This vulnerability could be exploited to cause system instability or potential unauthorized memory access.

Remediation Plan

Immediate Action: Apply the vendor-provided kernel updates which include the revert of the faulty mmap_prepare() change.

Proactive Monitoring: Monitor for any anomalous activity or system panics on servers utilizing the AFS (Andrew File System) network filesystem.

Compensating Controls: If the AFS driver is not required, consider blacklisting the afs module to reduce the attack surface.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Security teams should audit their Linux environments for the use of the AFS filesystem and ensure that kernel updates are applied promptly. Addressing regressions in core filesystem drivers is essential for maintaining a secure and stable operating environment.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
A use-after-free vulnerability exists in the Linux kernel's IPv6 networking stack within seg6 and rpl lwtunnels, potentially leading to denial of service.

Executive Summary:
A critical use-after-free vulnerability in the Linux kernel's IPv6 networking stack poses a significant risk of system instability and denial of service.

Vulnerability Details

CVE-ID: CVE-2026-46099

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for affected versions

Vulnerability: This is a use-after-free vulnerability within the seg6 and rpl lwtunnels of the Linux kernel's IPv6 stack. It can be triggered by a local user under specific race conditions involving PREEMPT_RT configurations and concurrent nexthop route entry releases.

Business Impact

Successful exploitation of this vulnerability can lead to a system crash or denial of service, significantly impacting service availability and operational continuity. With a CVSS score of 8.1, this is classified as a High-severity flaw that requires prompt attention to ensure system stability and reliability.

Remediation Plan

Immediate Action: Apply the latest security updates provided by your Linux distribution maintainer. The fix involves ensuring proper reference counting by calling skb_dst_force() after ip6_route_input() to prevent the use of invalid memory.

Proactive Monitoring: Monitor system logs for kernel panics or unexpected service interruptions, particularly on systems utilizing IPv6 segment routing or RPL tunnels.

Compensating Controls: Restrict access to local system resources to trusted users to mitigate the risk of a local user triggering the race condition required for exploitation.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw and its impact on core kernel memory management, the potential for exploitation is high.

Analyst Recommendation

Given the severity of this kernel-level vulnerability, organizations should prioritize the deployment of kernel security updates across all affected infrastructure. Testing the patch in a staging environment is advised to ensure compatibility before deploying to production systems to prevent potential downtime.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A concurrency issue in the Linux kernel's vmalloc shrinker mechanism can lead to race conditions and potential memory corruption.

Executive Summary:
A high-severity concurrency flaw in the Linux kernel's memory management subsystem could allow local attackers to induce race conditions and potential system failure.

Vulnerability Details

CVE-ID: CVE-2026-46093

Affected Software: Linux kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability involves a lack of proper locking in the decay_va_pool_node() function within the vmalloc memory management code. The concurrent invocation from both the __purge_vmap_area_lazy() path and the shrinker via vmap_node_shrink_scan() without the vmap_purge_lock results in a race condition.

Business Impact

With a CVSS score of 7.8, this flaw poses a significant risk to the stability of the virtual memory subsystem. Successful exploitation could result in kernel panics, memory corruption, or potentially elevated privileges for a local attacker.

Remediation Plan

Immediate Action: Upgrade to a kernel version that correctly implements the vmap_purge_lock within the shrinker path.

Proactive Monitoring: Monitor system logs for memory-related kernel errors or unusual performance degradation associated with virtual memory operations.

Compensating Controls: Ensure that systems are running with hardened kernel configurations that limit the ability of user-space processes to trigger intensive memory management operations.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Kernel memory management bugs are critical due to their potential for widespread system impact. Patching should be treated as a high-priority task for all Linux environments to ensure the integrity of the memory subsystem.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A use-after-free vulnerability in the Linux kernel's ALSA loopback driver during format changes can lead to system instability.

Executive Summary:
A high-severity use-after-free vulnerability in the ALSA loopback driver could allow an attacker to trigger kernel-level memory errors and potentially compromise the system.

Vulnerability Details

CVE-ID: CVE-2026-46090

Affected Software: Linux kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability is a use-after-free flaw in the aloop (ALSA loopback) driver, specifically occurring when a peer runtime is accessed during a format-change stop operation. The race condition in loopback_check_format() allows the kernel to access a stale pointer, leading to memory corruption.

Business Impact

The CVSS score of 7.8 reflects the high severity associated with kernel-level memory corruption. An attacker capable of triggering this race condition can cause system crashes, leading to downtime, or potentially achieve arbitrary code execution in the kernel context.

Remediation Plan

Immediate Action: Update the Linux kernel to a version containing the fix for the ALSA aloop UAF issue.

Proactive Monitoring: Monitor for unexpected kernel crashes or instability, particularly on systems utilizing audio loopback functionality.

Compensating Controls: Limit access to audio devices and system configuration if possible, as the exploit requires specific conditions related to audio stream format changes.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability highlights the risk of complex race conditions in kernel drivers. Administrators should prioritize patching to prevent potential memory-based attacks that could lead to full system compromise.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A memory management flaw in the Linux kernel's acomp component allows for an incorrect pointer to be stored in the request base.

Executive Summary:
A high-severity memory vulnerability in the Linux kernel may lead to system instability or potential exploitation.

Vulnerability Details

CVE-ID: CVE-2026-46081

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for affected versions.

Vulnerability: The vulnerability exists in the acomp_save_req function, where an incorrect pointer is stored during cryptographic operations. This memory mismanagement can result in undefined behavior or system crashes.

Business Impact

A CVSS score of 7.8 indicates a significant risk. Successful exploitation could lead to local privilege escalation or denial-of-service conditions, impacting the reliability and security of systems running the affected kernel.

Remediation Plan

Immediate Action: Apply the latest kernel security updates provided by your Linux distribution vendor immediately.

Proactive Monitoring: Review system logs for kernel panics or unusual memory-related errors that may indicate exploitation attempts.

Compensating Controls: Implement kernel hardening features and ensure that non-privileged users have restricted access to sensitive system functions.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

System administrators should prioritize patching the Linux kernel across all affected environments. Maintaining an updated kernel is essential for protecting against memory-based vulnerabilities of this nature.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
A KVM nested virtualization vulnerability in the Linux kernel may lead to improper exception handling when processing unhandled VMMCALLs.

Executive Summary:
An exception handling flaw in the Linux kernel KVM module could allow a malicious guest to trigger instability in the host environment.

Vulnerability Details

CVE-ID: CVE-2026-46076

Affected Software: Linux kernel

Affected Versions: See vendor advisory

Vulnerability: The issue occurs in KVM's nested SVM implementation, where a #UD (Invalid Opcode) exception is not properly synthesized for unhandled VMMCALL instructions, potentially leading to incorrect execution flow within the hypervisor.

Business Impact

A CVSS score of 7.9 (High) highlights the risk to virtualized environments. Exploitation could allow a guest VM to disrupt the host kernel or potentially escape the sandbox, posing a severe threat to multi-tenant cloud environments and virtualized server infrastructure.

Remediation Plan

Immediate Action: Update the Linux kernel on the host hypervisor to the latest version to ensure proper exception handling for nested virtualization.

Proactive Monitoring: Monitor host system logs for unexpected hypervisor exceptions or guest-triggered kernel panics.

Compensating Controls: Ensure that untrusted guests are isolated using proper security policies and that hypervisor features are configured with the principle of least privilege.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

For organizations relying on virtualization, this patch is critical. Prioritize updates to host kernels to prevent potential guest-to-host breakout scenarios.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A lifetime management issue in the Linux kernel's framebuffer deferred I/O (fbdev) subsystem could lead to use-after-free conditions.

Executive Summary:
A high-severity memory management flaw in the Linux kernel's framebuffer subsystem could lead to use-after-free exploitation and system instability.

Vulnerability Details

CVE-ID: CVE-2026-46065

Affected Software: Linux kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability arises from improper handling of the fb_info structure lifetime in the deferred I/O subsystem. By failing to properly disconnect deferred I/O from the fb_info lifecycle, the kernel may access freed memory, resulting in a use-after-free vulnerability.

Business Impact

With a CVSS score of 7.8, this vulnerability poses a significant risk to system stability and security. Exploitation could allow an attacker to trigger kernel panics or potentially gain unauthorized control over kernel execution flow, leading to system-wide compromise or persistent Denial of Service.

Remediation Plan

Immediate Action: Apply the latest kernel security patches provided by your Linux distribution maintainer to ensure the fix for fb_deferred_io_state is implemented.

Proactive Monitoring: Review system audit logs for recurring kernel panic events or memory-related faults specifically involving graphics or framebuffer drivers.

Compensating Controls: If immediate patching is not feasible, restrict local access to the system and limit the ability of non-privileged users to interact with framebuffer devices.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Kernel vulnerabilities involving memory management are highly dangerous and often serve as primitives for further exploitation. Security teams should expedite the deployment of kernel updates to all affected Linux-based infrastructure to neutralize this risk.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
An integer overflow vulnerability in the Linux kernel NTFS3 driver's volume boundary check could lead to memory corruption.

Executive Summary:
A high-severity integer overflow vulnerability in the Linux kernel NTFS3 driver could allow a local attacker to trigger memory corruption and potentially escalate privileges.

Vulnerability Details

CVE-ID: CVE-2026-46062

Affected Software: Linux kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability exists within the run_unpack() function of the NTFS3 driver due to an improper integer overflow check during volume boundary validation. This flaw allows an attacker to bypass boundary checks, potentially resulting in out-of-bounds memory access.

Business Impact

The vulnerability carries a CVSS score of 7.8, indicating a high risk to system integrity and availability. Successful exploitation could lead to system crashes (Denial of Service) or potential arbitrary code execution, resulting in unauthorized access to sensitive kernel-level data and operational disruption.

Remediation Plan

Immediate Action: Update your Linux kernel to the latest version provided by your distribution vendor that includes the fix for this NTFS3 driver flaw.

Proactive Monitoring: Monitor system logs for kernel oops or unexpected service restarts associated with file system operations.

Compensating Controls: Restrict access to mounting NTFS volumes to trusted users only, as the vulnerability typically requires the ability to mount or interact with a malicious file system.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Given the critical nature of kernel-level vulnerabilities, organizations should prioritize patching their Linux distributions. Ensure that automated patching workflows are active and verify that the kernel updates are applied across all production environments to mitigate the risk of local exploitation.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A race condition in the Linux kernel's amphion media driver leads to a kernel panic during m2m job release.

Executive Summary:
A race condition between job abort and device run in the Linux kernel amphion driver can cause a kernel panic due to premature memory deallocation.

Vulnerability Details

CVE-ID: CVE-2026-46058

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability is a race condition where v4l2_m2m_ctx_release() frees the m2m_ctx structure while v4l2_m2m_try_run() is concurrently attempting to call device_run using the same context. This leads to a kernel panic when the driver attempts to access the freed memory.

Business Impact

This vulnerability can be exploited to cause a denial-of-service (system panic) on devices using the Amphion VPU. With a CVSS score of 7.8, it represents a high-severity risk to system reliability.

Remediation Plan

Immediate Action: Update the kernel to a version that properly synchronizes the job abort and device run paths in the amphion driver.

Proactive Monitoring: Monitor for kernel panics associated with video processing tasks.

Compensating Controls: If possible, restrict access to the video hardware nodes to authorized processes.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This update is vital for maintaining the stability of systems utilizing Amphion video drivers. Administrators should apply the kernel patches as soon as they are made available by their distribution vendor.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
A use-after-free vulnerability exists in the Linux kernel's Bluetooth subsystem during SSP passkey handling.

Executive Summary:
A high-severity use-after-free vulnerability in the Linux kernel Bluetooth component could lead to system crashes or arbitrary code execution.

Vulnerability Details

CVE-ID: CVE-2026-46056

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for affected versions

Vulnerability: The vulnerability occurs because hci_conn lookup and field access are not protected by the hdev lock in hci_user_passkey_notify_evt() and hci_keypress_notify_evt(), allowing the connection to be freed concurrently.

Business Impact

This flaw can result in a kernel crash or potentially be leveraged for further exploitation, such as code execution. The 8.8 CVSS score reflects the high risk posed to systems utilizing Bluetooth functionality.

Remediation Plan

Immediate Action: Update the Linux kernel to a version that includes the fix ensuring hci_conn lookup and field access are covered by the hdev lock.

Proactive Monitoring: Monitor system logs for Bluetooth-related kernel oops or instability.

Compensating Controls: Disable Bluetooth services on servers or systems where it is not strictly required to reduce the attack surface.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 31, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Administrators should treat this vulnerability with high urgency, particularly on systems where Bluetooth is active. Updating the kernel to the patched version is the only effective way to mitigate this use-after-free risk.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
An improper memory cleanup in the Linux kernel's RDS protocol driver during copy errors leads to a potential use-after-free.

Executive Summary:
A memory management error in the Linux kernel RDS driver during copy errors can cause a use-after-free vulnerability, risking system stability.

Vulnerability Details

CVE-ID: CVE-2026-46053

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The __rds_rdma_map() function incorrectly handles MR cleanup when a copy error occurs. Because ownership of sg/pages is handed to the transport after get_mr() succeeds, failing to handle cleanup correctly results in a use-after-free condition.

Business Impact

This flaw can be exploited to cause a system crash or potentially corrupt kernel memory. Given the 7.8 CVSS score, this is a significant risk for systems that utilize the Reliable Datagram Sockets (RDS) protocol.

Remediation Plan

Immediate Action: Apply the vendor-provided kernel patch to fix the MR cleanup logic in the RDS driver.

Proactive Monitoring: Monitor system logs for RDS-related errors or kernel panics.

Compensating Controls: Disable the RDS protocol if it is not required for your network infrastructure.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Organizations using the RDS protocol should prioritize this security update. Verify kernel versions and apply the patches to mitigate the risk of kernel memory corruption and system instability.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
A flaw in the Linux kernel's IPv4 ICMP implementation fails to validate reply types, potentially leading to memory corruption or instability.

Executive Summary:
An input validation vulnerability in the Linux kernel ICMP handling could allow an attacker to trigger kernel-level memory corruption.

Vulnerability Details

CVE-ID: CVE-2026-46037

Affected Software: Linux kernel

Affected Versions: See vendor advisory

Vulnerability: The vulnerability occurs in the IPv4 ICMP stack, where the kernel fails to validate the outbound reply type before accessing icmp_pointers. This can lead to improper pointer usage when handling Extended Echo Replies.

Business Impact

The CVSS score of 8.2 (High) signifies a severe risk to system stability and security. Successful exploitation could lead to kernel panics (Denial of Service) or potential privilege escalation, impacting critical production workloads and server reliability.

Remediation Plan

Immediate Action: Apply the latest kernel security patches provided by your Linux distribution maintainer to ensure the ICMP pointer validation logic is updated.

Proactive Monitoring: Monitor network traffic for malformed ICMP packets and review system logs for signs of kernel instability.

Compensating Controls: Use network-level filtering to block or sanitize anomalous ICMP traffic where possible, although this does not replace the necessity of a kernel update.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Given the high severity of kernel-level flaws, it is imperative to treat this update with high priority. Organizations should test and deploy the latest kernel updates to mitigate the risk of exploitation.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
A race condition in the Linux kernel's vfio/cdx driver can lead to a use-after-free of the cdx_irqs array during concurrent ioctl calls.

Executive Summary:
A high-severity race condition in the Linux kernel's vfio/cdx driver may lead to system instability or unauthorized memory access.

Vulnerability Details

CVE-ID: CVE-2026-46036

Affected Software: Linux kernel

Affected Versions: See vendor advisory

Vulnerability: The vfio_cdx_set_msi_trigger() function lacks proper serialization when handling concurrent VFIO_DEVICE_SET_IRQS ioctls. This can lead to a use-after-free vulnerability when the cdx_irqs array is modified simultaneously by multiple threads.

Business Impact

With a CVSS score of 7.8, this flaw poses a significant risk to system stability and integrity. An attacker capable of triggering this race condition could cause a kernel panic or potentially escalate privileges.

Remediation Plan

Immediate Action: Apply the latest Linux kernel security patches that introduce the cdx_irqs_lock mutex.

Proactive Monitoring: Monitor system logs for unexpected behavior in VFIO-related kernel functions or concurrent access errors.

Compensating Controls: Limit access to VFIO device interfaces to privileged users to prevent unauthorized exploitation.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Kernel updates should be applied immediately to resolve the serialization flaw. Ensuring that the kernel is patched against such race conditions is vital for maintaining a secure and stable operating environment.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A missing notification during listener migration in the Linux kernel's TCP stack can lead to stalled connections.

Executive Summary:
A failure to notify waiters during TCP listener migration in the Linux kernel can cause connection handling issues and potential service disruption.

Vulnerability Details

CVE-ID: CVE-2026-46015

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: When a TCP child socket is migrated from a closing listener to another socket in an SO_REUSEPORT group, the target listener does not receive a notification via sk_data_ready(). This leaves the waiter unaware of the new accept-queue entry.

Business Impact

This issue can result in dropped or stalled network connections, impacting the availability of network services. While not a direct exploit for code execution, the 7.8 CVSS score acknowledges the potential for significant denial-of-service in high-traffic network environments.

Remediation Plan

Immediate Action: Update the Linux kernel to a version that includes the fix for sk_data_ready() notifications during listener migration.

Proactive Monitoring: Monitor network service performance and check for stalled accept-queues or unexpected connection timeouts.

Compensating Controls: Ensure network load balancers are configured to handle potential connection drops gracefully if the kernel cannot be patched immediately.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

For high-availability network services, this update is essential to prevent connection handling errors. Administrators should test and deploy the kernel patch in their network infrastructure to ensure continued stability of TCP services.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A use-after-free vulnerability in the Linux kernel's mtk-jpeg media driver occurs due to uncancelled work during the release path.

Executive Summary:
A race condition in the mtk-jpeg driver's release process can trigger a use-after-free vulnerability, leading to system crashes.

Vulnerability Details

CVE-ID: CVE-2026-46011

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The mtk_jpeg_release() function frees the context structure without properly cancelling pending or running work in ctx->jpeg_work. This leaves a dangling pointer, resulting in a use-after-free condition when the work queue attempts to access the already-freed context.

Business Impact

This flaw can be used to cause a denial-of-service (system crash) on devices that utilize the MediaTek JPEG hardware decoder. With a 7.8 CVSS score, it represents a high-severity risk for mobile or embedded devices running affected kernel versions.

Remediation Plan

Immediate Action: Update the kernel to a version that properly cancels pending work in the mtk-jpeg release path.

Proactive Monitoring: Monitor system logs for kernel panics during video processing or JPEG decoding tasks.

Compensating Controls: If applicable, restrict user access to the hardware media decoders.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability should be addressed through standard patch management processes for kernel-based software. Given the risk of system instability, ensure that all affected hardware devices receive the necessary kernel update.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
A missing error handling check in the Linux kernel rxrpc implementation can lead to improper state management during token extraction.

Executive Summary:
An error handling flaw in the Linux kernel rxrpc module potentially exposes the system to memory exhaustion or state corruption.

Vulnerability Details

CVE-ID: CVE-2026-46010

Affected Software: Linux kernel

Affected Versions: See vendor advisory

Vulnerability: The issue exists in rxgk_extract_token(), where a failure in rxgk_decrypt_skb() (specifically an -ENOMEM return) is not handled correctly. The function fails to terminate execution, leading to continued processing in an invalid state.

Business Impact

The CVSS score of 8.1 (High) indicates a significant threat to system reliability. Improper error handling in the networking stack can be leveraged to induce system crashes or potentially facilitate more complex attacks, leading to downtime for critical network services.

Remediation Plan

Immediate Action: Update to the latest kernel version provided by your distribution, which includes the necessary error handling logic for rxgk_extract_token().

Proactive Monitoring: Monitor system logs for kernel errors related to network subsystem failures or unexpected abort signals.

Compensating Controls: Implement network segmentation to limit the attack surface available to interact with rxrpc services.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Patching the kernel is the only effective way to remediate this logic flaw. IT teams should verify vendor security notices and schedule maintenance windows for the necessary kernel updates.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
An integer overflow in the Linux kernel's Nouveau DRM driver allows for bypass of buffer bounds checks.

Executive Summary:
An integer overflow in the Linux kernel Nouveau driver's push buffer relocation validation could allow an attacker to bypass security checks and cause memory corruption.

Vulnerability Details

CVE-ID: CVE-2026-46006

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability is located in nouveau_gem_pushbuf_reloc_apply(), where a 32-bit integer overflow occurs during the bounds check of relocation offsets. This allows an attacker to bypass the validation logic, potentially leading to out-of-bounds memory access.

Business Impact

Successful exploitation could lead to local privilege escalation or system crashes on machines using NVIDIA GPUs with the Nouveau driver. The 7.8 CVSS score reflects the serious nature of this kernel-level memory corruption flaw.

Remediation Plan

Immediate Action: Apply the vendor-provided kernel update that corrects the overflow validation in the Nouveau DRM driver.

Proactive Monitoring: Monitor for anomalous GPU driver activity or unexpected system restarts.

Compensating Controls: If the Nouveau driver is not required, switch to proprietary NVIDIA drivers or blacklist the Nouveau module.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability poses a clear risk of memory corruption. Administrators should deploy the security update across all affected Linux systems to mitigate the risk of local privilege escalation.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
An improper UDF partition descriptor handling in the Linux kernel leads to a heap out-of-bounds write vulnerability.

Executive Summary:
A heap out-of-bounds write vulnerability in the Linux kernel UDF file system parser could allow an attacker to trigger corruption via a crafted UDF image.

Vulnerability Details

CVE-ID: CVE-2026-45991

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability exists in the UDF partition descriptor bookkeeping. Mounting a specially crafted UDF image with repeated descriptors causes the kernel to perform an out-of-bounds write to the part_descs_loc[] array on the heap.

Business Impact

This flaw could lead to arbitrary code execution or a system crash when a victim mounts a malicious UDF file system. Given the 7.8 CVSS score, this is a critical concern for systems that handle untrusted removable media or disk images.

Remediation Plan

Immediate Action: Update the kernel to a version that includes the fix for UDF partition descriptor bookkeeping.

Proactive Monitoring: Monitor for kernel crashes triggered during the mounting of external media or disk images.

Compensating Controls: Disable the automatic mounting of UDF file systems if they are not required for business operations.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The ability to trigger memory corruption via a crafted file system makes this a high-priority vulnerability. System administrators should ensure that kernel patches are applied and consider restricting the ability to mount external file systems by non-privileged users.

---METADATA---
VENDOR: jsrsasign
PRODUCT: jsrsasign
AFFECTED_VERSIONS: 7.0.0 to 11.1.1
---END_METADATA---

Description Summary:
The jsrsasign library is vulnerable to incomplete comparison checks in cryptographic functions, allowing attackers to bias DSA nonces and recover private keys.

Executive Summary:
A critical cryptographic flaw in the jsrsasign library allows remote attackers to recover private keys by exploiting biased DSA nonces caused by incorrect comparison logic.

Vulnerability Details

CVE-ID: CVE-2026-4599

Affected Software: jsrsasign jsrsasign

Affected Versions: Versions 7.0.0 before 11.1.1

Vulnerability: This vulnerability involves an Incomplete Comparison with Missing Factors within the getRandomBigIntegerZeroToMax and getRandomBigIntegerMinToMax functions. An unauthenticated attacker can exploit incorrect compareTo checks that accept out-of-range candidates, biasing DSA nonces during signature generation and leading to private key recovery.

Business Impact

A successful exploit of this vulnerability results in the total compromise of cryptographic identity. If an attacker recovers a private key, they can impersonate the affected entity, decrypt sensitive communications, and forge digital signatures. Given the CVSS score of 9.1, this represents a critical risk to data integrity and confidentiality across any system utilizing the affected library versions for secure communications.

Remediation Plan

Immediate Action: Update the jsrsasign library to version 11.1.1 or later immediately to patch the flawed cryptographic comparison logic.

Proactive Monitoring: Review application logs for unusual cryptographic activity and consider rotating any private keys that were utilized by the vulnerable library versions.

Compensating Controls: Implement strict input validation for cryptographic operations and ensure that sensitive key management is handled within secure, hardware-backed environments where possible.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 23, 2026, there is no public information indicating active exploitation of this vulnerability. However, because the flaw allows for the direct recovery of private keys, the potential for targeted exploitation is extremely high once the technical details are analyzed by threat actors.

Analyst Recommendation

The severity of this cryptographic flaw cannot be overstated, as it undermines the fundamental security of the jsrsasign library. Organizations must prioritize the update to version 11.1.1 immediately. Failure to remediate this vulnerability leaves sensitive data and digital identities exposed to total compromise.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A use-after-free vulnerability in the Linux kernel's GFS2 file system occurs during inline data write operations.

Executive Summary:
A premature release of memory in the GFS2 file system write path can lead to a use-after-free vulnerability, risking system stability.

Vulnerability Details

CVE-ID: CVE-2026-45984

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The inline data buffer head (dibh) is released prematurely in gfs2_iomap_begin() via release_metapath(), while the iomap structure still references the buffer. This creates a use-after-free condition when the kernel attempts to access the data.

Business Impact

This vulnerability could result in data corruption or a system crash on servers utilizing the GFS2 cluster file system. With a CVSS score of 7.8, the impact on data integrity and system uptime is significant, particularly in high-availability environments.

Remediation Plan

Immediate Action: Patch the Linux kernel to the version provided by your vendor that addresses the GFS2 inline data write path issue.

Proactive Monitoring: Monitor GFS2-related error logs and file system integrity checks for signs of corruption.

Compensating Controls: If immediate patching is not feasible, restrict the use of GFS2 inline data features if possible.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Organizations relying on GFS2 should prioritize this update to avoid potential file system instability. Ensure that kernel updates are applied to all nodes in the GFS2 cluster to maintain a secure and stable environment.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A race condition in the Linux kernel's amdxdna accelerator driver leads to use-after-free vulnerabilities during resource release.

Executive Summary:
A race condition in the Linux kernel amdxdna driver can result in use-after-free vulnerabilities and system crashes during job scheduling.

Vulnerability Details

CVE-ID: CVE-2026-45980

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The issue exists because the driver continues to schedule jobs on a hardware context while it is undergoing resource release via aie2_release_resource(). This overlap leads to a use-after-free condition when the scheduler accesses resources that have already been freed.

Business Impact

The vulnerability could lead to system instability or arbitrary code execution if an attacker can reliably trigger the race condition. Given the CVSS score of 7.8, this flaw represents a significant risk to systems using AMD XDNA hardware, potentially impacting system availability and integrity.

Remediation Plan

Immediate Action: Update to the latest stable kernel version that includes the patch to synchronize job scheduling with resource release.

Proactive Monitoring: Monitor for kernel panics or "use-after-free" warnings in the dmesg logs.

Compensating Controls: Restrict access to the hardware accelerator devices to authorized processes to minimize the window of opportunity for exploitation.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Given the potential for kernel-level crashes and memory corruption, administrators should treat this update as high priority. Ensure all systems utilizing affected hardware are patched to prevent exploitation of this race condition.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A use-after-free (UAF) vulnerability exists in the Linux kernel's bonding driver during bond teardown, potentially allowing for concurrent access.

Executive Summary:
A high-severity use-after-free vulnerability in the Linux kernel bonding driver could lead to system crashes or arbitrary code execution.

Vulnerability Details

CVE-ID: CVE-2026-45970

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for affected versions.

Vulnerability: The vulnerability occurs in rlb_arp_recv due to a race condition during bond teardown, where the ALB RX path accesses rx_hashtbl after it has been freed. This results in a use-after-free condition.

Business Impact

With a CVSS score of 7.8, this flaw poses a notable risk to system availability and security. An attacker capable of triggering this race condition could cause a denial-of-service or potentially execute arbitrary code with kernel-level privileges.

Remediation Plan

Immediate Action: Apply the latest kernel patches from your distribution provider to address the UAF in the bonding driver.

Proactive Monitoring: Monitor system performance and logs for unexpected kernel oops or crashes related to network bonding interfaces.

Compensating Controls: Limit the ability of unprivileged users to manipulate network interface configurations.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Patching the kernel is the recommended course of action to mitigate this vulnerability. Organizations should test and deploy the latest kernel updates to ensure system stability and protection against potential exploitation.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
An incorrect cleanup usage of kfree in the Linux kernel's crypto ccp driver results in a memory deallocation crash.

Executive Summary:
A memory management error in the Linux kernel crypto ccp driver can lead to a system crash when invalid deallocation occurs.

Vulnerability Details

CVE-ID: CVE-2026-45959

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability arises from the improper use of the __cleanup(kfree) attribute on a local pointer variable in the crypto ccp driver. This causes the kernel to attempt to free the address of the local variable itself rather than the buffer returned by kmalloc, leading to a crash due to invalid deallocation.

Business Impact

This vulnerability poses a risk of denial-of-service (DoS) as a local attacker could trigger the crash by interacting with the affected crypto driver. With a CVSS score of 7.8, this is considered a high-severity issue that could disrupt operations on systems utilizing specific hardware-accelerated cryptographic functions.

Remediation Plan

Immediate Action: Apply the latest kernel security patches from your OS vendor to resolve the incorrect cleanup attribute usage.

Proactive Monitoring: Review system logs for frequent driver crashes or unexpected reboots associated with cryptographic module initialization.

Compensating Controls: If patching is delayed, disable or blacklist the affected crypto driver if it is not required for system functionality.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The risk of immediate system crash necessitates timely remediation. Organizations should verify their kernel versions against vendor security bulletins and apply the necessary updates to prevent potential service disruption caused by this memory management error.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A use-after-free vulnerability exists in the Linux kernel's BPF subsystem due to incorrect reference counting within the check_pseudo_btf_id function.

Executive Summary:
A use-after-free vulnerability in the Linux kernel BPF subsystem could allow a local attacker to trigger memory corruption or system instability.

Vulnerability Details

CVE-ID: CVE-2026-45951

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability involves incorrect reference counting logic in the check_pseudo_btf_id() function, which can lead to a use-after-free condition when the function is invoked with a zero-refcounted BTF object. An authenticated user with sufficient privileges to interact with BPF could potentially exploit this to cause a kernel crash.

Business Impact

Successful exploitation of this flaw could result in a kernel panic, leading to unplanned downtime and service interruption for critical infrastructure. While the CVSS score of 7.8 indicates high severity, the primary risk is system instability and potential local privilege escalation, which threatens the integrity and availability of the affected host.

Remediation Plan

Immediate Action: Update the Linux kernel to the latest stable release provided by your distribution vendor that includes the fix for this BPF refcounting issue.

Proactive Monitoring: Monitor system logs for kernel oops or crash reports that coincide with BPF-related operations.

Compensating Controls: Restrict access to BPF functionality by limiting CAP_BPF and CAP_SYS_ADMIN privileges to trusted users only.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability represents a significant risk to system stability. Administrators should prioritize patching their kernels to ensure that the BPF subsystem is protected against this use-after-free condition. Apply the vendor-supplied security updates as soon as they become available in your distribution's repository.

---METADATA---
VENDOR: Intel
PRODUCT: VT-d
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A race condition in the Linux kernel's Intel VT-d implementation during PASID entry replacement could lead to memory corruption or system instability.

Executive Summary:
A high-severity race condition in the Linux kernel's Intel VT-d subsystem may expose the system to memory corruption risks, requiring an immediate kernel update.

Vulnerability Details

CVE-ID: CVE-2026-45945

Affected Software: Intel VT-d (Linux Kernel)

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability is a race condition occurring during the replacement of PASID (Process Address Space ID) table entries in the Intel VT-d IOMMU driver. An attacker capable of triggering this race condition could potentially cause memory corruption, impacting system stability and security.

Business Impact

With a CVSS score of 8.8, this vulnerability poses a significant risk of system instability or denial-of-service. In virtualized environments, such memory corruption could potentially be leveraged to escape the guest environment or compromise the host kernel, leading to unauthorized access to sensitive data processed within the memory space.

Remediation Plan

Immediate Action: Apply the latest security-focused Linux kernel updates provided by your distribution vendor as soon as they become available.

Proactive Monitoring: Monitor system logs for kernel panic events, hardware errors, or IOMMU-related faults that may indicate an exploitation attempt.

Compensating Controls: Ensure that system security hardening, such as enabling kernel self-protection features (e.g., KASLR), is active to increase the difficulty of successful exploitation.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of May 31, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw in the kernel's memory management, the potential for exploitation is high.

Analyst Recommendation

Users and administrators should prioritize updating their Linux kernel to the version specified in their vendor's advisory. Given the complexity of kernel-level vulnerabilities, testing updates in a staging environment before broad deployment is recommended to ensure compatibility while maintaining a high security posture.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A bitmap inconsistency in the Linux kernel's ext4 filesystem can lead to data integrity issues under heavy workloads.

Executive Summary:
A filesystem bitmap inconsistency in the Linux ext4 driver could lead to data corruption or system instability.

Vulnerability Details

CVE-ID: CVE-2026-45942

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The issue involves inconsistency reports in the e4b bitmap within the ext4 driver, observed during high-stress operations with mixed huge-page workloads. This suggests improper synchronization or management of filesystem metadata.

Business Impact

Data corruption is a severe risk for any production environment. With a CVSS score of 7.8, this flaw could lead to data loss or system-wide downtime, necessitating urgent attention for systems relying on ext4.

Remediation Plan

Immediate Action: Update the kernel to the latest version to include the fix for ext4 bitmap consistency.

Proactive Monitoring: Monitor filesystem logs for consistency errors and run fsck periodically on critical volumes.

Compensating Controls: Ensure robust backup procedures are in place to recover from potential data corruption caused by filesystem errors.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Filesystem stability is paramount. We recommend applying the kernel patch immediately to prevent the risk of data loss or corruption, particularly on high-load servers utilizing the ext4 filesystem.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A slab-out-of-bounds read vulnerability exists in the Linux kernel's NTFS3 driver during index entry deletion.

Executive Summary:
A memory bounds-checking error in the Linux NTFS3 driver could lead to information disclosure or system crashes.

Vulnerability Details

CVE-ID: CVE-2026-45935

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The flaw occurs in the DeleteIndexEntryRoot function within the NTFS3 driver, where the entry size (esize) is not properly validated against the log record length. An attacker providing a malicious NTFS filesystem could trigger this out-of-bounds read.

Business Impact

This vulnerability could be used to leak kernel memory or cause a denial-of-service. With a CVSS score of 7.8, it poses a risk to systems that mount untrusted NTFS-formatted storage media.

Remediation Plan

Immediate Action: Update the Linux kernel to the latest version containing the bounds-checking fix for the NTFS3 driver.

Proactive Monitoring: Monitor for kernel logs indicating slab out-of-bounds errors when interacting with external storage.

Compensating Controls: Avoid mounting NTFS filesystems from untrusted or unknown sources.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

We recommend applying the kernel patch promptly. For systems that do not require NTFS support, consider disabling the NTFS3 driver module to reduce the attack surface.

---METADATA---
VENDOR: Linux
PRODUCT: Kernel
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
An incorrect register state propagation in the Linux kernel's BPF verifier can lead to security policy bypasses.

Executive Summary:
A logic error in the Linux kernel BPF verifier could allow an attacker to bypass security restrictions.

Vulnerability Details

CVE-ID: CVE-2026-45933

Affected Software: Linux Kernel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The issue exists in sync_linked_regs(), where the BPF verifier incorrectly copies register IDs. This can lead to the propagation of incorrect bounds information, potentially allowing a malicious BPF program to read or write memory outside of its permitted range.

Business Impact

This vulnerability is highly significant as it targets the BPF subsystem, often used for security monitoring and packet filtering. Successful exploitation could lead to privilege escalation or complete system compromise, justifying the 7.8 CVSS score.

Remediation Plan

Immediate Action: Apply the vendor-provided kernel patch that corrects the BPF register ID synchronization.

Proactive Monitoring: Review BPF program loading logs and monitor for anomalous kernel behavior or unexpected BPF program crashes.

Compensating Controls: Restrict access to the bpf() system call to highly privileged users (e.g., via unprivileged_bpf_disabled sysctl).

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This is a critical patch for any system that utilizes BPF features. Given the potential for privilege escalation, administrators must prioritize this update to maintain the integrity of kernel-level security filters.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
A use-after-free vulnerability in the Linux kernel's accel/amdxdna component can lead to system crashes via an invalid mm structure reference.

Executive Summary:
A memory management vulnerability in the Linux kernel's amdxdna driver may lead to system instability or denial-of-service conditions.

Vulnerability Details

CVE-ID: CVE-2026-45931

Affected Software: Linux kernel

Affected Versions: See vendor advisory

Vulnerability: A race condition exists in the iommu_sva_unbind_device() function where the system attempts to access an iommu_mm structure after it has been freed. The fix requires explicit reference counting to ensure the mm structure remains valid during the unbinding process.

Business Impact

The CVSS score of 7.8 indicates a high severity, primarily impacting system availability. Successful exploitation could lead to kernel panics or system crashes, causing significant downtime for affected infrastructure.

Remediation Plan

Immediate Action: Update the Linux kernel to a version that includes the fix for the amdxdna driver.

Proactive Monitoring: Monitor system logs for kernel oops or crash reports related to the amdxdna component.

Compensating Controls: Restrict access to hardware acceleration features to trusted users to reduce the attack surface for local privilege escalation or DoS.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

System administrators should prioritize patching the Linux kernel to mitigate this high-severity memory safety issue. Ensuring kernel updates are applied in a timely manner is essential to prevent potential system instability.

---METADATA---
VENDOR: Linux
PRODUCT: kernel
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
A use-after-free vulnerability in the Linux kernel's ovpn_net_xmit function can lead to system instability or denial-of-service.

Executive Summary:
A use-after-free vulnerability in the Linux kernel's OVPN network driver poses a risk to system availability and stability.

Vulnerability Details

CVE-ID: CVE-2026-45929

Affected Software: Linux kernel

Affected Versions: See vendor advisory

Vulnerability: The ovpn_net_xmit function incorrectly handles socket buffers (skb) when they are shared. If skb_share_check frees the original skb, the function continues to use the pointer, leading to a use-after-free condition.

Business Impact

With a CVSS score of 7.8, this vulnerability represents a high risk to system uptime. Exploitation can result in kernel panics or denial-of-service conditions, impacting network-dependent services.

Remediation Plan

Immediate Action: Update the Linux kernel to a version that includes the fix for the ovpn_net_xmit function.

Proactive Monitoring: Monitor system logs for kernel crashes and error messages associated with the OVPN network interface.

Compensating Controls: If patching is delayed, consider disabling the OVPN module if not strictly required for network operations.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Administrators should treat this as a high-priority update. Patching the kernel will prevent potential system crashes and ensure the continued reliability of network communications.