Page 87 of 7704 results (0.007 seconds)

CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0

08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix monitor mode bringup crash When the interface is brought up in monitor mode, it leads to NULL pointer dereference crash. This crash happens when the packet type is extracted for a SKB. This extraction which is present in the received msdu delivery path,is not needed for the monitor ring packets since they are all RAW packets. Hence appending the flags with "RX_FLAG_ONLY_MONITOR" to skip that extraction. Observed calltrace:... • https://git.kernel.org/stable/c/d5c65159f2895379e11ca13f62feabe93278985d •

CVSS: 6.6EPSS: 0%CPEs: 9EXPL: 0

08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: media: dvb-usb: fix memory leak in dvb_usb_adapter_init() Syzbot reports a memory leak in "dvb_usb_adapter_init()". The leak is due to not accounting for and freeing current iteration's adapter->priv in case of an error. Currently if an error occurs, it will exit before incrementing "num_adapters_initalized", which is used as a reference counter to free all adap->priv in "dvb_usb_adapter_exit()". There are multiple error paths that can exit... • https://git.kernel.org/stable/c/4d43e13f723e12734257277cc38497fab1efc605 •

CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0

08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: serial: amba-pl011: avoid SBSA UART accessing DMACR register Chapter "B Generic UART" in "ARM Server Base System Architecture" [1] documentation describes a generic UART interface. Such generic UART does not support DMA. In current code, sbsa_uart_pops and amba_pl011_pops share the same stop_rx operation, which will invoke pl011_dma_rx_stop, leading to an access of the DMACR register. This commit adds a using_rx_dma check in pl011_dma_rx_st... • https://git.kernel.org/stable/c/0dd1e247fd39aed20fd2baacc62ca44d82534798 •

CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0

08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: net: netsec: fix error handling in netsec_register_mdio() If phy_device_register() fails, phy_device_free() need be called to put refcount, so memory of phy device and device name can be freed in callback function. If get_phy_device() fails, mdiobus_unregister() need be called, or it will cause warning in mdiobus_free() and kobject is leaked. In the Linux kernel, the following vulnerability has been resolved: net: netsec: fix error handling... • https://git.kernel.org/stable/c/533dd11a12f698c571a12271b20f235792d3e148 •

CVSS: 7.8EPSS: 0%CPEs: 5EXPL: 0

08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: fpga: prevent integer overflow in dfl_feature_ioctl_set_irq() The "hdr.count * sizeof(s32)" multiplication can overflow on 32 bit systems leading to memory corruption. Use array_size() to fix that. In the Linux kernel, the following vulnerability has been resolved: fpga: prevent integer overflow in dfl_feature_ioctl_set_irq() The "hdr.count * sizeof(s32)" multiplication can overflow on 32 bit systems leading to memory corruption. Use array_... • https://git.kernel.org/stable/c/322b598be4d9b9090cda560c4caab78704615ab4 •

CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0

08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: ext4: fix potential memory leak in ext4_fc_record_modified_inode() As krealloc may return NULL, in this case 'state->fc_modified_inodes' may not be freed by krealloc, but 'state->fc_modified_inodes' already set NULL. Then will lead to 'state->fc_modified_inodes' memory leak. In the Linux kernel, the following vulnerability has been resolved: ext4: fix potential memory leak in ext4_fc_record_modified_inode() As krealloc may return NULL, in t... • https://git.kernel.org/stable/c/8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 •

CVSS: 7.1EPSS: 0%CPEs: 4EXPL: 0

08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to invalidate dcc->f2fs_issue_discard in error path Syzbot reports a NULL pointer dereference issue as below: __refcount_add include/linux/refcount.h:193 [inline] __refcount_inc include/linux/refcount.h:250 [inline] refcount_inc include/linux/refcount.h:267 [inline] get_task_struct include/linux/sched/task.h:110 [inline] kthread_stop+0x34/0x1c0 kernel/kthread.c:703 f2fs_stop_discard_thread+0x3c/0x5c fs/f2fs/segment.c:1638 kill_f2f... • https://git.kernel.org/stable/c/4d67490498acb4ffcef5ba7bc44990d46e66a44c •

CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0

08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix memory leak in kfd_mem_dmamap_userptr() If the number of pages from the userptr BO differs from the SG BO then the allocated memory for the SG table doesn't get freed before returning -EINVAL, which may lead to a memory leak in some error paths. Fix this by checking the number of pages before allocating memory for the SG table. In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix memory leak in... • https://git.kernel.org/stable/c/264fb4d332f5e76743818480e482464437837c52 •

CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0

08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: mmc: meson-gx: fix return value check of mmc_add_host() mmc_add_host() may return error, if we ignore its return value, it will lead two issues: 1. The memory that allocated in mmc_alloc_host() is leaked. 2. In the remove() path, mmc_remove_host() will be called to delete device, but it's not added yet, it will lead a kernel crash because of null-ptr-deref in device_del(). Fix this by checking the return value and goto error path which will... • https://git.kernel.org/stable/c/51c5d8447bd71b7e539c19c46a03b73c0e91fa66 •

CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0

08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/powerplay/psm: Fix memory leak in power state init Commit 902bc65de0b3 ("drm/amdgpu/powerplay/psm: return an error in power state init") made the power state init function return early in case of failure to get an entry from the powerplay table, but it missed to clean up the allocated memory for the current power state before returning. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/powerplay/psm: ... • https://git.kernel.org/stable/c/902bc65de0b3d72c481b45cbac3e97ab8cb399c2 •