A race condition vulnerability in the Linux kernel's i915 DRM driver was resolved by ensuring interrupts are only unmasked when the RPS (Render Power State) is active. The flaw involved a timing window where interrupts could be unmasked after the GPU was parked and the runtime power management wakelock was dropped, causing kernel taint due to hardware access without the wakelock held.
A vulnerability in the Linux kernel's drm/vmwgfx component was resolved by validating the pitch value received from userspace along with box dimensions before copying data. This fix addresses potential out-of-bounds reads that could occur during cursor snooping.
A vulnerability in the Linux kernel's mount propagation logic allowed synchronous unmount operations to succeed even when the mount was still in use. This was due to propagate_mount_busy() not properly checking certain mount copies with children, leading to mounts being silently unmounted while still referenced. The flaw could affect container environments sharing mount trees with the host, causing mounts to be detached unexpectedly.
A vulnerability in the Linux kernel's namespace handling was resolved by preventing the MNT_UMOUNT flag from being inherited in clone_mnt(). The issue involved mounts that were lazily unmounted but kept alive by file descriptors still being copied with the MNT_UMOUNT flag set, causing multiple bugs including mount namespace leaks, improper unmount behavior, and corrupted mount propagation. The fix adds MNT_UMOUNT to internal flags so it is not copied during cloning, preventing these issues.
A vulnerability in the Linux kernel's namespace handling has been resolved. The issue involves the may_copy_tree() function accepting mounts whose roots are nsfs or pidfs files before verifying if the mount is actually mounted. This allowed recursive copying of unmounted mount trees, which is unintended behavior. The fix prevents walking an unmounted tree during recursive copy operations, causing such attempts to fail with EINVAL. Bind mounting a namespace that is gone remains possible if pinned by a file descriptor.
A vulnerability in the Linux kernel related to namespace handling and unmounting submounts has been resolved. The issue involves the unmounting process where busy mounts may be incorrectly unmounted due to improper reference checks, potentially leading to mounts being marked as synchronously unmounted while still in use. This affects mounts with the MNT_SHRINKABLE flag, such as automounted submounts of NFS, AFS, CIFS, and certain debugfs mounts. The fix ensures that each mount is checked for references right before unmounting under appropriate locks to maintain correctness.
A vulnerability in the Linux kernel's mount namespace handling allows recursive bind mounts of mount namespace files, which can cause cycles and unlimited resource leaks. The issue arises because the kernel does not fully check for mount namespace loops when performing recursive bind mounts with MS_REC, allowing a process to create a bind-mount stack of mount namespace file descriptors that leaks kernel memory.
An integer overflow or wraparound vulnerability has been identified in GitLab version 3.0. This type of vulnerability can lead to unexpected behavior in software when integer calculations exceed their maximum value and wrap around, potentially causing security issues.
An integer overflow or wraparound vulnerability has been identified in GitLab version 3.0. This type of vulnerability involves improper handling of integer values, which can lead to unexpected behavior in software. No CVSS score or detailed technical impact information is provided. There is no indication of known exploits in the wild or available patches at this time.
A vulnerability identified as CVE-2026-112085 affects webpack-dev-server version 3.0, allowing cross-origin WebSocket access via proxied upgrades. This issue relates to improper handling of WebSocket upgrade requests that could enable unauthorized cross-origin access. No CVSS score is provided, and there is no indication of known exploits in the wild. No patch or remediation details are currently available.
CVE-2026-91403 is a vulnerability affecting Microsoft product version 3.0. The description references Microsoft Support Lifecycle information but does not provide specific technical details about the vulnerability. No CVSS score or detailed impact information is available.
A vulnerability identified as CVE-2026-111181 affects the body-parser component version 3.0, allowing a Denial of Service (DoS) attack via trailing bytes after a compressed request body. The issue relates to improper handling of compressed request bodies that contain extra trailing bytes, which can be exploited to disrupt service availability.
A vulnerability in Node.js HTTP Agent connection reuse can cause a client to accept a response that was sent before, potentially leading to incorrect or unexpected behavior. This flaw relates to improper handling of HTTP connection reuse in the affected version 3.0 of the product. No CVSS score or detailed impact information is provided.
A vulnerability in Node.js TLS hostname verification allows a certificate containing only a DNS Subject Alternative Name (SAN) to authenticate an IP endpoint improperly. This flaw could lead to incorrect validation of TLS connections when IP addresses are used instead of hostnames.
A vulnerability exists in Node.js version 3.0 related to the internal entropy caches used by the crypto module's randomUUID() and randomUUIDv7() functions. This flaw involves improper handling of entropy, which may affect the randomness quality of UUID generation. No CVSS score or detailed impact information is provided. No patch or remediation details are available at this time.
A vulnerability in Node.js TLS hostname verification can cause a server certificate to be validated against an incorrect IP address. This flaw affects Node.js version 3.0. No CVSS score or exploit details are available. The issue relates to improper validation of server certificates during TLS connections.
A vulnerability in Node.js TLS hostname verification allows a certificate lacking a matching IP address Subject Alternative Name (SAN) to authenticate improperly. This flaw affects Node.js version 3.0. No CVSS score or detailed impact metrics are provided. No patch or remediation information is currently available. There is no evidence of exploitation in the wild at this time.
A vulnerability in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions. This flaw affects version 3.0 of the affected Microsoft product. No CVSS score or detailed impact information is provided. There is no indication of known exploits in the wild or available patches at this time.
A security flaw exists in the Node.js permission model related to filesystem enforcement, specifically affecting the fs.realpathSync() function, which does not require the necessary read permissions. This vulnerability is identified as CVE-2026-106073 and affects Microsoft product version 3.0. No CVSS score or detailed impact information is provided, and no known exploits are reported in the wild.
A vulnerability in the Node.js permission model for filesystem enforcement allows access to paths that do not match a specified wildcard pattern. This flaw could lead to unauthorized access to filesystem paths beyond intended restrictions. The issue is identified in Microsoft-related software, specifically version 3.0. No CVSS score or detailed exploit information is currently available.