CVE-2026-98993 is a high-severity vulnerability in the Linux kernel related to mount namespace handling. The flaw occurs because the MNT_UMOUNT flag, which indicates a mount has been lazily unmounted, is inherited incorrectly during mount cloning operations. This leads to mounts being detached improperly, reference count errors, and potential resource leaks. The issue affects Linux kernel versions 4.0.2 through 4.1. A fix has been implemented to prevent the MNT_UMOUNT flag from being copied during clone_mnt(), addressing the root cause.
CVE-2026-98992 is a vulnerability in the Linux kernel's namespace handling where the system incorrectly copies an unmounted mount tree during certain bind mount operations. This occurs because the kernel allows copying of mounts whose root is an nsfs or pidfs file even if they are unmounted but kept alive by a file descriptor. The flaw permits recursive copying of an unmounted mount stack, which is unintended behavior. The issue has been fixed by refusing to walk unmounted trees during copy operations, causing recursive copying of such trees to fail with an error.
CVE-2026-98984 is a vulnerability in the Linux kernel's dcache subsystem where a mountpoint can be incorrectly assigned to a dentry that is in the process of being removed. This occurs due to a race condition between detach_mounts() and d_delete(), allowing a bind mount of a directory being removed to be moved beneath an existing mount, causing the mount to remain attached to a removed directory indefinitely.
A vulnerability in the Linux kernel's unshare system call could cause active namespace references to be dropped incorrectly when set_cred_ucounts() fails during unshare. This leads to namespace reference counts going negative and the caller losing references to namespaces it continues to use, causing those namespaces to no longer appear in namespace listings. The issue affects multiple Linux kernel versions and has been fixed in later releases.
CVE-2026-98982 is a high-severity vulnerability in the Linux kernel affecting version 6.9. It involves a flaw where a pseudo dentry, which should never become the root of a mount, can be improperly used as such via bind mounting /proc/self/fd/<fd>. This can lead to use-after-free conditions during mount namespace operations. The issue has been fixed in specific commits in the Linux kernel source.
CVE-2026-98980 is a high-severity vulnerability in the Linux kernel affecting the namei component. It involves a flaw in the reference walking (refwalk) mechanism where overmounted entries can be revealed due to improper handling of unlinked mountpoints. This can cause a refwalk to expose underlying filesystem entries that should be hidden after a mountpoint is unlinked. The issue arises because refwalk does not revalidate dentries after taking references, unlike other lookup methods. The vulnerability has been fixed in specific Linux kernel commits.
A use-after-free vulnerability in the Linux kernel's cgroup cpuset subsystem was addressed by avoiding direct access to a potentially stale pointer in the is_in_v2_mode() function. The fix introduces a new flag to safely indicate cpuset v2 mode, preventing unsafe memory access during cgroup filesystem rebind operations.
A vulnerability in the Linux kernel's btrfs filesystem involving io_uring encoded data handling was fixed. The issue involved leaking btrfs_uring_encoded_data when a request returned -EAGAIN and was cancelled or the ring exited before reissue. This could lead to memory not being freed properly during cleanup. The fix ensures that data is freed on all exit paths when -EAGAIN is returned, preventing leaks.
A vulnerability in the Linux kernel ext4 filesystem driver allows a crash due to a NULL pointer dereference when large folios are enabled on encrypted inodes. This occurs because enabling the encrypt feature on a mounted filesystem bypasses checks that disable large folios, leading to a kernel crash during encrypted data writes. The issue affects Linux kernel versions from 6.19 through 7.2 and was fixed by disabling large folios on encrypted inodes, similar to the handling of data journaling inodes. The fix is included starting with kernel version 7.3, where the code was refactored.
A vulnerability in the Linux kernel's AMD GPU driver (drm/amd/pm/si) was fixed to prevent scheduling thermal work when the thermal work queue is not initialized. This issue occurs when Dynamic Power Management (DPM) is disabled using the amdgpu.dpm=0 module parameter, which leaves the thermal work queue uninitialized. Scheduling work on an uninitialized queue could lead to kernel instability or crashes.
A vulnerability in the Linux kernel's ksmbd component involves holding a mutex lock (ci->m_lock) while waiting for a lease break acknowledgment, causing a potential deadlock and long delays in lease break resolution. This issue affects versions from 6.6.35 up to but not including 6.7, and version 6.9. The problem arises when a conflicting open triggers a lease break, but the acknowledgment wait blocks due to lock contention, leading to a timeout of up to 35 seconds. The fix involves changing the locking strategy to avoid holding the lock during the wait, improving lease break handling and performance.
A vulnerability in the Linux kernel's irqchip/gic-v4 subsystem causes a kernel panic when the virtual GICv4 is enabled on a system without an MSI controller device tree node and GICv4 support. This occurs due to a NULL pointer dereference when the kernel attempts to access a non-existent gic_domain. The issue is fixed by disabling vLPI support at initialization if the host has no ITS, preventing the panic.
A vulnerability in the Linux kernel's iwlwifi driver related to Multi-Link Device (MLD) handling during WoWLAN suspend without netdetect configuration has been resolved. The issue involved the driver generating warnings (WARN_ON) when suspending WoWLAN without an active network connection or netdetect configured. The fix removes the warning and ensures the driver cleanly handles this scenario by disconnecting and suspending properly.
A vulnerability in the Linux kernel's freevxfs filesystem code caused a kernel crash (BUG) when encountering an unknown typed-extent type during ioctl(FIBMAP) operations on regular files. The issue was fixed by replacing the BUG() call with a WARN_ON_ONCE() and returning an error code, preventing kernel crashes.
Capcom notified customers of unauthorized access to CAPCOM ID accounts but their email security configuration is weak. Their official notification emails failed DMARC alignment checks despite passing SPF and DKIM individually. Capcom's DMARC policy is set to 'p=none', which only monitors failures without requesting rejection or quarantine of unauthenticated emails. This lax configuration increases the risk of phishing and spoofing attacks impersonating Capcom. The company uses an external email delivery service but has not properly aligned authentication to prevent spoofing. The notification warns customers about potential misuse of their information but Capcom has not taken stronger email security measures to prevent secondary damage.