CVSS: 5.6EPSS: 0%CPEs: 5EXPL: 0CVE-2022-50633 – usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init
https://notcve.org/view.php?id=CVE-2022-50633
09 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init of_icc_get() alloc resources for path handle, we should release it when not need anymore. Like the release in dwc3_qcom_interconnect_exit() function. Add icc_put() in error handling to fix this. In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init of_icc_get() alloc resources for path handle, we shou... • https://git.kernel.org/stable/c/bea46b9815154ac47baf16b64022d791a4471375 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50632 – drivers: perf: marvell_cn10k: Fix hotplug callback leak in tad_pmu_init()
https://notcve.org/view.php?id=CVE-2022-50632
08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: drivers: perf: marvell_cn10k: Fix hotplug callback leak in tad_pmu_init() tad_pmu_init() won't remove the callback added by cpuhp_setup_state_multi() when platform_driver_register() failed. Remove the callback by cpuhp_remove_multi_state() in fail path. Similar to the handling of arm_ccn_init() in commit 26242b330093 ("bus: arm-ccn: Prevent hotplug callback leak") In the Linux kernel, the following vulnerability has been resolved: drivers: ... • https://git.kernel.org/stable/c/036a7584bede317d0df6b854e4f531b7a2dd8b33 •
CVSS: 5.6EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50631 – RISC-V: kexec: Fix memory leak of fdt buffer
https://notcve.org/view.php?id=CVE-2022-50631
08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: RISC-V: kexec: Fix memory leak of fdt buffer This is reported by kmemleak detector: unreferenced object 0xff60000082864000 (size 9588): comm "kexec", pid 146, jiffies 4294900634 (age 64.788s) hex dump (first 32 bytes): d0 0d fe ed 00 00 12 ed 00 00 00 48 00 00 11 40 ...........H...@ 00 00 00 28 00 00 00 11 00 00 00 02 00 00 00 00 ...(............ backtrace: [<00000000f95b17c4>] kmemleak_alloc+0x34/0x3e [<00000000b9ec8e3e>] kmalloc_order+0x9... • https://git.kernel.org/stable/c/6261586e0c91db14c34f894f4bc48f2300cff1d4 •
CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 0CVE-2023-53769 – virt/coco/sev-guest: Double-buffer messages
https://notcve.org/view.php?id=CVE-2023-53769
08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: virt/coco/sev-guest: Double-buffer messages The encryption algorithms read and write directly to shared unencrypted memory, which may leak information as well as permit the host to tamper with the message integrity. Instead, copy whole messages in or out as needed before doing any computation on them. In the Linux kernel, the following vulnerability has been resolved: virt/coco/sev-guest: Double-buffer messages The encryption algorithms rea... • https://git.kernel.org/stable/c/d5af44dde5461d125d1602ac913ab5c6bdf09b8b •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53768 – regmap-irq: Fix out-of-bounds access when allocating config buffers
https://notcve.org/view.php?id=CVE-2023-53768
08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: regmap-irq: Fix out-of-bounds access when allocating config buffers When allocating the 2D array for handling IRQ type registers in regmap_add_irq_chip_fwnode(), the intent is to allocate a matrix with num_config_bases rows and num_config_regs columns. This is currently handled by allocating a buffer to hold a pointer for each row (i.e. num_config_bases). After that, the logic attempts to allocate the memory required to hold the register co... • https://git.kernel.org/stable/c/faa87ce9196dbb074d75bd4aecb8bacf18f19b4e •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2023-53767 – wifi: ath12k: fix memory leak in ath12k_qmi_driver_event_work()
https://notcve.org/view.php?id=CVE-2023-53767
08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix memory leak in ath12k_qmi_driver_event_work() Currently the buffer pointed by event is not freed in case ATH12K_FLAG_UNREGISTERING bit is set, this causes memory leak. Add a goto skip instead of return, to ensure event and all the list entries are freed properly. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1 In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix memor... • https://git.kernel.org/stable/c/a87f59041a7f77b4bdab05cea60ac6adc69dc5d2 •
CVSS: 7.1EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53766 – FS: JFS: Check for read-only mounted filesystem in txBegin
https://notcve.org/view.php?id=CVE-2023-53766
08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: FS: JFS: Check for read-only mounted filesystem in txBegin This patch adds a check for read-only mounted filesystem in txBegin before starting a transaction potentially saving from NULL pointer deref. • https://git.kernel.org/stable/c/a88efca805bea93cea9187dfd00835aa7093bf1b •
CVSS: 6.6EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53765 – dm cache: free background tracker's queued work in btracker_destroy
https://notcve.org/view.php?id=CVE-2023-53765
08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: dm cache: free background tracker's queued work in btracker_destroy Otherwise the kernel can BUG with: [ 2245.426978] ============================================================================= [ 2245.435155] BUG bt_work (Tainted: G B W ): Objects remaining in bt_work on __kmem_cache_shutdown() [ 2245.445233] ----------------------------------------------------------------------------- [ 2245.445233] [ 2245.454879] Slab 0x00000000b0ce2b30... • https://git.kernel.org/stable/c/673a3af21d5e3ed769f3eaed0c888244290a3506 •
CVSS: 7.8EPSS: 0%CPEs: 2EXPL: 0CVE-2023-53764 – wifi: ath12k: Handle lock during peer_id find
https://notcve.org/view.php?id=CVE-2023-53764
08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Handle lock during peer_id find ath12k_peer_find_by_id() requires that the caller hold the ab->base_lock. Currently the WBM error path does not hold the lock and calling that function, leads to the following lockdep_assert()in QCN9274: [105162.160893] ------------[ cut here ]------------ [105162.160916] WARNING: CPU: 3 PID: 0 at drivers/net/wireless/ath/ath12k/peer.c:71 ath12k_peer_find_by_id+0x52/0x60 [ath12k] [105162.160933]... • https://git.kernel.org/stable/c/9faf7c696610a348ca94a224d55c946b19b3279d •
CVSS: 7.3EPSS: 0%CPEs: 5EXPL: 0CVE-2023-53763 – Revert "f2fs: fix to do sanity check on extent cache correctly"
https://notcve.org/view.php?id=CVE-2023-53763
08 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: Revert "f2fs: fix to do sanity check on extent cache correctly" syzbot reports a f2fs bug as below: UBSAN: array-index-out-of-bounds in fs/f2fs/f2fs.h:3275:19 index 1409 is out of range for type '__le32[923]' (aka 'unsigned int[923]') Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:217 [inline] __ubsan_handle_out_of_bounds+0x11c/0x150 lib/ubsan.c:348 inline_dat... • https://git.kernel.org/stable/c/85eb8b61dd4cfc7a839a0e86287b92ca6193444e •