CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2022-50514 – usb: gadget: f_hid: fix refcount leak on error path
https://notcve.org/view.php?id=CVE-2022-50514
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_hid: fix refcount leak on error path When failing to allocate report_desc, opts->refcnt has already been incremented so it needs to be decremented to avoid leaving the options structure permanently locked. In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_hid: fix refcount leak on error path When failing to allocate report_desc, opts->refcnt has already been incremented so it needs to be decre... • https://git.kernel.org/stable/c/21a9476a7ba847e413bf1c144d7c614532aed6dd •
CVSS: 5.6EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50513 – staging: rtl8723bs: fix a potential memory leak in rtw_init_cmd_priv()
https://notcve.org/view.php?id=CVE-2022-50513
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix a potential memory leak in rtw_init_cmd_priv() In rtw_init_cmd_priv(), if `pcmdpriv->rsp_allocated_buf` is allocated in failure, then `pcmdpriv->cmd_allocated_buf` will be not properly released. Besides, considering there are only two error paths and the first one can directly return, so we do not need implicitly jump to the `exit` tag to execute the error handler. So this patch added `kfree(pcmdpriv->cmd_allocated_b... • https://git.kernel.org/stable/c/e5d8f05edb36fc4ab15beec62cb6ab62f5a60fe2 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2022-50512 – ext4: fix potential memory leak in ext4_fc_record_regions()
https://notcve.org/view.php?id=CVE-2022-50512
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: ext4: fix potential memory leak in ext4_fc_record_regions() As krealloc may return NULL, in this case 'state->fc_regions' may not be freed by krealloc, but 'state->fc_regions' already set NULL. Then will lead to 'state->fc_regions' memory leak. In the Linux kernel, the following vulnerability has been resolved: ext4: fix potential memory leak in ext4_fc_record_regions() As krealloc may return NULL, in this case 'state->fc_regions' may not b... • https://git.kernel.org/stable/c/2cfb769d60a2a57eb3566765428b6131cd16dcfe • CWE-772: Missing Release of Resource after Effective Lifetime •
CVSS: 7.8EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50511 – lib/fonts: fix undefined behavior in bit shift for get_default_font
https://notcve.org/view.php?id=CVE-2022-50511
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: lib/fonts: fix undefined behavior in bit shift for get_default_font Shifting signed 32-bit value by 31 bits is undefined, so changing significant bit to unsigned. The UBSAN warning calltrace like below: UBSAN: shift-out-of-bounds in lib/fonts/fonts.c:139:20 left shift of 1 by 31 places cannot be represented in type 'int'
CVSS: 6.4EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50509 – media: coda: Add check for kmalloc
https://notcve.org/view.php?id=CVE-2022-50509
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: media: coda: Add check for kmalloc As the kmalloc may return NULL pointer, it should be better to check the return value in order to avoid NULL poineter dereference, same as the others. In the Linux kernel, the following vulnerability has been resolved: media: coda: Add check for kmalloc As the kmalloc may return NULL pointer, it should be better to check the return value in order to avoid NULL poineter dereference, same as the others. The ... • https://git.kernel.org/stable/c/cb1d3a336371e35c3920cc50a701c5403c255644 •
CVSS: 7.8EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53616 – jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount
https://notcve.org/view.php?id=CVE-2023-53616
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount syzbot found an invalid-free in diUnmount: BUG: KASAN: double-free in slab_free mm/slub.c:3661 [inline] BUG: KASAN: double-free in __kmem_cache_free+0x71/0x110 mm/slub.c:3674 Free of addr ffff88806f410000 by task syz-executor131/3632 CPU: 0 PID: 3632 Comm: syz-executor131 Not tainted 6.1.0-rc7-syzkaller-00012-gca57f02295f1 #0 Hardware name: Google Google Compute Engine/Google Comp... • https://git.kernel.org/stable/c/c3c0f0ddd851b3fa3e9d3450bbcd561f4f850469 •
CVSS: 6.3EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53615 – scsi: qla2xxx: Fix deletion race condition
https://notcve.org/view.php?id=CVE-2023-53615
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix deletion race condition System crash when using debug kernel due to link list corruption. The cause of the link list corruption is due to session deletion was allowed to queue up twice. Here's the internal trace that show the same port was allowed to double queue for deletion on different cpu. 20808683956 015 qla2xxx [0000:13:00.1]-e801:4: Scheduling sess ffff93ebf9306800 for deletion 50:06:0e:80:12:48:ff:50 fc4_type 1 20... • https://git.kernel.org/stable/c/726b85487067d7f5b23495bc33c484b8517c4074 • CWE-413: Improper Resource Locking •
CVSS: 7.1EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53612 – hwmon: (coretemp) Simplify platform device handling
https://notcve.org/view.php?id=CVE-2023-53612
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) Simplify platform device handling Coretemp's platform driver is unconventional. All the real work is done globally by the initcall and CPU hotplug notifiers, while the "driver" effectively just wraps an allocation and the registration of the hwmon interface in a long-winded round-trip through the driver core. The whole logic of dynamically creating and destroying platform devices to bring the interfaces up and down is erro... • https://git.kernel.org/stable/c/4000384684f612b3645a944f6acde0e65ac370b8 • CWE-476: NULL Pointer Dereference •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53611 – ipmi_si: fix a memleak in try_smi_init()
https://notcve.org/view.php?id=CVE-2023-53611
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: ipmi_si: fix a memleak in try_smi_init() Kmemleak reported the following leak info in try_smi_init(): unreferenced object 0xffff00018ecf9400 (size 1024): comm "modprobe", pid 2707763, jiffies 4300851415 (age 773.308s) backtrace: [<000000004ca5b312>] __kmalloc+0x4b8/0x7b0 [<00000000953b1072>] try_smi_init+0x148/0x5dc [ipmi_si] [<000000006460d325>] 0xffff800081b10148 [<0000000039206ea5>] do_one_initcall+0x64/0x2a4 [<00000000601399ce>] do_init... • https://git.kernel.org/stable/c/7960f18a56475bf2177c5ff56c72eb4c12c56440 • CWE-771: Missing Reference to Active Allocated Resource •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53608 – nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread()
https://notcve.org/view.php?id=CVE-2023-53608
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread() The finalization of nilfs_segctor_thread() can race with nilfs_segctor_kill_thread() which terminates that thread, potentially causing a use-after-free BUG as KASAN detected. At the end of nilfs_segctor_thread(), it assigns NULL to "sc_task" member of "struct nilfs_sc_info" to indicate the thread has finished, and then notifies nilfs_segctor_kill_thread() of this us... • https://git.kernel.org/stable/c/034cce77d52ba013ce62b4f5258c29907eb1ada5 •