
CVE-2022-50031 – scsi: iscsi: Fix HW conn removal use after free
https://notcve.org/view.php?id=CVE-2022-50031
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: iscsi: Fix HW conn removal use after free If qla4xxx doesn't remove the connection before the session, the iSCSI class tries to remove the connection for it. We were doing a iscsi_put_conn() in the iter function which is not needed and will result in a use after free because iscsi_remove_conn() will free the connection. In the Linux kernel, the following vulnerability has been resolved: scsi: iscsi: Fix HW conn removal use after free ... • https://git.kernel.org/stable/c/0483ffc02ebb953124c592485a5c48ac4ffae5fe •

CVE-2022-50030 – scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input
https://notcve.org/view.php?id=CVE-2022-50030
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input Malformed user input to debugfs results in buffer overflow crashes. Adapt input string lengths to fit within internal buffers, leaving space for NULL terminators. In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input Malformed user input to debugfs results in buffer o... • https://git.kernel.org/stable/c/927907f1cbb3408cadde637fccfc17bb6b10a87d •

CVE-2022-50029 – clk: qcom: ipq8074: dont disable gcc_sleep_clk_src
https://notcve.org/view.php?id=CVE-2022-50029
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: clk: qcom: ipq8074: dont disable gcc_sleep_clk_src Once the usb sleep clocks are disabled, clock framework is trying to disable the sleep clock source also. However, it seems that it cannot be disabled and trying to do so produces: [ 245.436390] ------------[ cut here ]------------ [ 245.441233] gcc_sleep_clk_src status stuck at 'on' [ 245.441254] WARNING: CPU: 2 PID: 223 at clk_branch_wait+0x130/0x140 [ 245.450435] Modules linked in: xhci_... • https://git.kernel.org/stable/c/38cee0d2b65eed42a44052de1bfdc0177b6c3f05 •

CVE-2022-50028 – gadgetfs: ep_io - wait until IRQ finishes
https://notcve.org/view.php?id=CVE-2022-50028
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: gadgetfs: ep_io - wait until IRQ finishes after usb_ep_queue() if wait_for_completion_interruptible() is interrupted we need to wait until IRQ gets finished. Otherwise complete() from epio_complete() can corrupt stack. In the Linux kernel, the following vulnerability has been resolved: gadgetfs: ep_io - wait until IRQ finishes after usb_ep_queue() if wait_for_completion_interruptible() is interrupted we need to wait until IRQ gets finished.... • https://git.kernel.org/stable/c/67a4874461422e633236a0286a01b483cd647113 •

CVE-2022-50027 – scsi: lpfc: Fix possible memory leak when failing to issue CMF WQE
https://notcve.org/view.php?id=CVE-2022-50027
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix possible memory leak when failing to issue CMF WQE There is no corresponding free routine if lpfc_sli4_issue_wqe fails to issue the CMF WQE in lpfc_issue_cmf_sync_wqe. If ret_val is non-zero, then free the iocbq request structure. In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix possible memory leak when failing to issue CMF WQE There is no corresponding free routine if lpfc_sli4_issue_wqe ... • https://git.kernel.org/stable/c/9c8e2e607270a368834a0ef72aa82d970f89c596 •

CVE-2022-50025 – cxl: Fix a memory leak in an error handling path
https://notcve.org/view.php?id=CVE-2022-50025
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: cxl: Fix a memory leak in an error handling path A bitmap_zalloc() must be balanced by a corresponding bitmap_free() in the error handling path of afu_allocate_irqs(). In the Linux kernel, the following vulnerability has been resolved: cxl: Fix a memory leak in an error handling path A bitmap_zalloc() must be balanced by a corresponding bitmap_free() in the error handling path of afu_allocate_irqs(). • https://git.kernel.org/stable/c/c2c7a29f99788e9e5dfe41d16868ea33da7cc235 •

CVE-2022-50024 – dmaengine: dw-axi-dmac: do not print NULL LLI during error
https://notcve.org/view.php?id=CVE-2022-50024
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-axi-dmac: do not print NULL LLI during error During debugging we have seen an issue where axi_chan_dump_lli() is passed a NULL LLI pointer which ends up causing an OOPS due to trying to get fields from it. Simply print NULL LLI and exit to avoid this. In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-axi-dmac: do not print NULL LLI during error During debugging we have seen an issue where axi_ch... • https://git.kernel.org/stable/c/af76e6fdcf92f1a742b788d0dba5edd194267bf9 •

CVE-2022-50023 – dmaengine: dw-axi-dmac: ignore interrupt if no descriptor
https://notcve.org/view.php?id=CVE-2022-50023
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-axi-dmac: ignore interrupt if no descriptor If the channel has no descriptor and the interrupt is raised then the kernel will OOPS. Check the result of vchan_next_desc() in the handler axi_chan_block_xfer_complete() to avoid the error happening. In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-axi-dmac: ignore interrupt if no descriptor If the channel has no descriptor and the interrupt is rais... • https://git.kernel.org/stable/c/54aa6c49361b79f7f6b15fc63dfe9ea52c70bb03 •

CVE-2022-50022 – drivers:md:fix a potential use-after-free bug
https://notcve.org/view.php?id=CVE-2022-50022
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: drivers:md:fix a potential use-after-free bug In line 2884, "raid5_release_stripe(sh);" drops the reference to sh and may cause sh to be released. However, sh is subsequently used in lines 2886 "if (sh->batch_head && sh != sh->batch_head)". This may result in an use-after-free bug. It can be fixed by moving "raid5_release_stripe(sh);" to the bottom of the function. • https://git.kernel.org/stable/c/7470a4314b239e9a9580f248fdf4c9a92805490e •

CVE-2022-50021 – ext4: block range must be validated before use in ext4_mb_clear_bb()
https://notcve.org/view.php?id=CVE-2022-50021
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ext4: block range must be validated before use in ext4_mb_clear_bb() Block range to free is validated in ext4_free_blocks() using ext4_inode_block_valid() and then it's passed to ext4_mb_clear_bb(). However in some situations on bigalloc file system the range might be adjusted after the validation in ext4_free_blocks() which can lead to troubles on corrupted file systems such as one found by syzkaller that resulted in the following BUG kern... • https://git.kernel.org/stable/c/7550aade978371ac582f6d43b14c4cb89ca54463 •