Threats Tagged 'cve-2025-68324'

The kernel packages contain the Linux kernel, the core of any Linux operating system. Security Fix(es): * kernel: iommu: disable SVA when CONFIG_X86 is set (CVE-2025-71089) * kernel: crypto: seqiv - Do not use req->iv after crypto_aead_encrypt (CVE-2025-71131) * kernel: scsi: core: Wake up the error handler when final completions race against each other (CVE-2026-23110) * kernel: mm: thp: deny THP for files on anonymous inodes (CVE-2026-23375) * kernel: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() (CVE-2026-23455) * kernel: drm/amd/display: Do not skip unrelated mode changes in DSC validation (CVE-2026-31488) * kernel: ALSA: usb-audio: Add sanity check for OOB writes at silencing (CVE-2026-43279) * kernel: rxrpc: Fix potential UAF after skb_unshare() failure (CVE-2026-45998) * kernel: Arm Processors: Privilege escalation or information disclosure via writes to higher exception level resources (CVE-2025-10263) * kernel: netfilter: nat: use kfree_rcu to release ops (CVE-2026-53000) * kernel: dm log: fix out-of-bounds write due to region_count overflow (CVE-2026-53059) * kernel: net/sched: act_api: use RCU with deferred freeing for action lifecycle (CVE-2026-53264) Bug Fix(es) and Enhancement(s): * backport make module and modules-core provides use variant [rhel-10.0.z] (JIRA:RHEL-219433) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

A security update for the SUSE Linux Enterprise 11 SP4 kernel addresses multiple vulnerabilities, including use-after-free bugs, race conditions, and improper handling of network protocols. The update fixes 10 distinct CVEs affecting components such as SCSI, TCP, bonding, ALSA, KVM, networking, and Bluetooth subsystems. These vulnerabilities could lead to memory corruption or unexpected behavior in kernel modules.

A use-after-free vulnerability in the Linux kernel's SCSI IMM driver was fixed. The issue arises when a delayed work item accesses memory after the associated device structure has been freed during device detachment. This race condition could lead to kernel memory corruption. The vulnerability affects multiple Linux kernel versions prior to 6.17.0-19.19~24.04.2 and similar builds. A patch is available that properly cancels the delayed work before freeing memory. No known exploits are reported in the wild.

In the Linux kernel, the following vulnerability has been resolved: efivarfs: Fix memory leak of efivarfs_fs_info in fs_context error paths When processing mount options, efivarfs allocates efivarfs_fs_info (sfi) early in fs_context initialization. However, sfi is associated with the superblock and typically freed when the superblock is destroyed. If the fs_context is released (final put) before fill_super is called—such as on error paths or during reconfiguration—the sfi structure would leak, as ownership never transfers to the superblock. Implement the .free callback in efivarfs_context_ops to ensure any allocated sfi is properly freed if the fs_context is torn down before fill_super, preventing this memory leak.