CVE-2025-38669 is a medium-severity vulnerability in the Linux kernel's DRM subsystem related to the handling of dma_buf pointers in GEM objects. The dma_buf field in struct drm_gem_object can become NULL when user space releases the final GEM handle, leading to a NULL-pointer dereference and potential denial of service. Previous partial workarounds did not fully address the issue, especially for buffer objects without associated DRM framebuffers. The vulnerability was resolved by reverting a commit that introduced the unstable dma_buf usage and returning to a more stable reference approach.
CVE-2025-38675 is a medium severity vulnerability in the Linux kernel's xfrm subsystem. It involves improper initialization of a pointer (state_ptrs) in the xfrm_state_find function, which can lead to use of uninitialized memory during CPU preemption scenarios. This flaw can cause a denial of service (kernel crash) due to an invalid memory access. The issue has been resolved by initializing state_ptrs earlier in the function to prevent misuse.
CVE-2025-38673 is a medium severity vulnerability in the Linux kernel's Direct Rendering Manager (DRM) subsystem. It involves a NULL-pointer dereference caused by the dma_buf field in the drm_gem_object structure becoming NULL when user space releases the final GEM handle. Previous partial workarounds did not fully resolve the issue, especially for buffer objects without an associated DRM framebuffer. The vulnerability was addressed by reverting a prior commit and returning to the use of the .import_attach->dmabuf field.
CVE-2025-38651 addresses a warning in the Linux kernel's landlock security module related to KUnit tests. The issue arises because get_id_range() expects a positive value, but get_random_u8() can return zero, causing a warning during testing. The fix clamps the value to ensure it is positive, resolving the warning without impacting functionality.
CVE-2025-38649 is a vulnerability in the Linux kernel affecting arm64 devices using the Qualcomm qcs615 device tree. It causes an infinite loop in the Coresight subsystem when only a source device is enabled, leading to a stack overflow and system crash. The issue arises from recursive calls in the coresight_find_activated_sysfs_sink function. The fix involves disabling the replicator1 device to break the loop, which limits trace data flow to certain sinks.
CVE-2025-38657 is a vulnerability in the Linux kernel's wifi driver rtw89 related to multi-channel concurrency (mcc). The issue involves a shift operation on a 'link_id' value obtained from debugfs, which if larger than the system's BITS_PER_LONG, causes shift wrapping and potential out-of-bounds memory access. Since only root can write to debugfs files, the security impact is limited. The vulnerability has been resolved by limiting the 'link_id' to IEEE80211_MLD_MAX_NUM_LINKS (15).
CVE-2025-38658 is a vulnerability in the Linux kernel's nvmet pci-epf subsystem where commands may be completed twice if nvmet_req_init() fails. This double completion can corrupt the PCI NVMe target state and cause a kernel oops. The issue occurs when unsupported opcodes trigger failure paths that lead to redundant completion calls. A patch has been applied to prevent double completions by adjusting how failed commands are completed.
CVE-2025-38648 addresses a vulnerability in the Linux kernel's stm32 SPI driver where a NULL pointer dereference could occur due to missing checks for configuration data availability. The stm32_spi_probe function now verifies that the configuration pointer is not NULL before accessing its members, preventing potential system crashes.
A medium severity vulnerability in the Linux kernel related to the pinctrl driver for the canaan k230 platform has been fixed by correcting the order of device tree parsing and pinctrl registration. The fix ensures device tree parsing occurs before pinctrl registration to avoid using uninitialized pin resources, which could cause system instability or crashes.
A vulnerability in the Linux kernel's pinctrl driver for canaan k230 was fixed by adding a NULL check during device tree parsing. This prevents a potential NULL pointer dereference if the "pinmux" property is missing from the device tree node. The issue also included a minor comment typo fix.
CVE-2025-38633 is a medium severity vulnerability in the Linux kernel related to clock management. The pll1_d8 clock, enabled by the boot loader and a parent to many critical clocks, could be disabled incorrectly due to a probe deferral handling issue. This caused the system to hang. The issue was fixed by marking pll1_d8 as critical to prevent it from being disabled.
CVE-2025-38640 is a vulnerability in the Linux kernel related to the netfilter BPF program execution path. The issue arises because migration is not disabled in the transmit path when running BPF programs, causing an assertion failure in the kernel. This leads to a kernel crash (BUG) due to an assumption of a non-migratable context being violated. The flaw was reported by syzbot and involves the function nf_hook_run_bpf().
CVE-2025-38642 addresses a warning condition (WARN_ON) in the Linux kernel's mac80211 wireless subsystem related to monitor mode on certain devices. The issue occurs on devices lacking WANT_MONITOR_VIF and likely without channel context support, where changing the per-link setting of a monitor interface triggers a warning. The fix modifies the link change code to handle these cases properly, preventing the warning.
A medium-severity vulnerability in the Linux kernel Bluetooth driver (btusb) involves a potential NULL pointer dereference caused by failure to check the return value of kmalloc memory allocation. This flaw could lead to a denial of service due to kernel crash or instability.
CVE-2025-38646 is a medium-severity vulnerability in the Linux kernel's rtw89 Wi-Fi driver. It involves a NULL pointer dereference triggered when receiving a problematic packet on an unsupported 6 GHz band. This occurs because the software may mistakenly treat a packet as received on the 6 GHz band even if the hardware does not support it, leading to uninitialized data usage and a kernel crash.
CVE-2025-38638 addresses a vulnerability in the Linux kernel's IPv6 routing notification function net6_rt_notify(). The issue arises because inet6_rt_notify() can be called under RCU protection only, which allows concurrent route changes that may cause rt6_fill_node() to return an -EMSGSIZE error. This could trigger a kernel warning and potentially impact system stability. The fix involves adding retry logic that resizes the socket buffer (skb) and retries the operation, eliminating the warning condition.
A vulnerability in the Linux kernel's vfio/pds driver was fixed by adding a missing detach_ioas operation. When CONFIG_IOMMUFD is enabled and a device is bound to the pds_vfio_pci driver, the probe fails with a warning due to the missing detach_ioas operation. This issue causes the device probe to fail with error -22. The fix involves using the generic vfio_iommufd_physical_detach_ioas function to properly set the detach_ioas operation.
A vulnerability in the Linux kernel ALSA usb scarlett2 driver due to a missing NULL pointer check has been fixed. The function scarlett2_input_select_ctl_info() allocates string arrays but did not check for NULL, which could cause a NULL pointer dereference leading to a kernel Oops (crash).
A vulnerability in the Linux kernel's imx95-blk-ctl clock driver causes a synchronous abort crash when runtime power management is enabled improperly. The issue arises because enabling runtime PM without explicitly resuming the device leads to the power domain being cut off after clk_register() is called, resulting in a crash when the clock hardware provider accesses the BLK_CTL register. The flaw is fixed by changing the runtime PM enablement method and cleanup handling.
CVE-2025-38628 is a vulnerability in the Linux kernel's vdpa/mlx5 driver where uninitialized resources were improperly released on an error path during device addition. This could cause a kernel warning and potentially lead to a denial of service due to a kernel crash. The issue was fixed by ensuring proper handling of uninitialized resources and reordering initialization calls to prevent failures during cleanup.