CVSS: 6.6EPSS: %CPEs: 7EXPL: 0CVE-2022-49526 – md/bitmap: don't set sb values if can't pass sanity check
https://notcve.org/view.php?id=CVE-2022-49526
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: md/bitmap: don't set sb values if can't pass sanity check If bitmap area contains invalid data, kernel will crash then mdadm triggers "Segmentation fault". This is cluster-md speical bug. In non-clustered env, mdadm will handle broken metadata case. In clustered array, only kernel space handles bitmap slot info. But even this bug only happened in clustered env, current sanity check is wrong, the code should be changed. How to trigger: (faul... • https://git.kernel.org/stable/c/422e8f7ba1e08c8e0e88d375bcb550bc2bbfe96d •
CVSS: 5.5EPSS: %CPEs: 9EXPL: 0CVE-2022-49525 – media: cx25821: Fix the warning when removing the module
https://notcve.org/view.php?id=CVE-2022-49525
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: media: cx25821: Fix the warning when removing the module When removing the module, we will get the following warning: [ 14.746697] remove_proc_entry: removing non-empty directory 'irq/21', leaking at least 'cx25821[1]' [ 14.747449] WARNING: CPU: 4 PID: 368 at fs/proc/generic.c:717 remove_proc_entry+0x389/0x3f0 [ 14.751611] RIP: 0010:remove_proc_entry+0x389/0x3f0 [ 14.759589] Call Trace: [ 14.759792]
CVSS: 5.6EPSS: %CPEs: 8EXPL: 0CVE-2022-49524 – media: pci: cx23885: Fix the error handling in cx23885_initdev()
https://notcve.org/view.php?id=CVE-2022-49524
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: media: pci: cx23885: Fix the error handling in cx23885_initdev() When the driver fails to call the dma_set_mask(), the driver will get the following splat: [ 55.853884] BUG: KASAN: use-after-free in __process_removed_driver+0x3c/0x240 [ 55.854486] Read of size 8 at addr ffff88810de60408 by task modprobe/590 [ 55.856822] Call Trace: [ 55.860327] __process_removed_driver+0x3c/0x240 [ 55.861347] bus_for_each_dev+0x102/0x160 [ 55.861681] i2c_de... • https://git.kernel.org/stable/c/6041d1a0365baa729b6adfb6ed5386d9388018db •
CVSS: 5.5EPSS: %CPEs: 6EXPL: 0CVE-2022-49522 – mmc: jz4740: Apply DMA engine limits to maximum segment size
https://notcve.org/view.php?id=CVE-2022-49522
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: mmc: jz4740: Apply DMA engine limits to maximum segment size Do what is done in other DMA-enabled MMC host drivers (cf. host/mmci.c) and limit the maximum segment size based on the DMA engine's capabilities. This is needed to avoid warnings like the following with CONFIG_DMA_API_DEBUG=y. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 21 at kernel/dma/debug.c:1162 debug_dma_map_sg+0x2f4/0x39c DMA-API: jz4780-dma 13420000.dma-contr... • https://git.kernel.org/stable/c/7923f95997a79cef2ad161a2facae64c25a0bca0 •
CVSS: 5.5EPSS: %CPEs: 5EXPL: 0CVE-2022-49521 – scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
https://notcve.org/view.php?id=CVE-2022-49521
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp() If no handler is found in lpfc_complete_unsol_iocb() to match the rctl of a received frame, the frame is dropped and resources are leaked. Fix by returning resources when discarding an unhandled frame type. Update lpfc_fc_frame_check() handling of NOP basic link service. In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix resource leak in lpfc_sli4_... • https://git.kernel.org/stable/c/fa1b509d41c5433672f72c0615cf4aefa0611c99 •
CVSS: 5.6EPSS: %CPEs: 6EXPL: 0CVE-2022-49520 – arm64: compat: Do not treat syscall number as ESR_ELx for a bad syscall
https://notcve.org/view.php?id=CVE-2022-49520
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: arm64: compat: Do not treat syscall number as ESR_ELx for a bad syscall If a compat process tries to execute an unknown system call above the __ARM_NR_COMPAT_END number, the kernel sends a SIGILL signal to the offending process. Information about the error is printed to dmesg in compat_arm_syscall() -> arm64_notify_die() -> arm64_force_sig_fault() -> arm64_show_signal(). arm64_show_signal() interprets a non-zero value for current->thread.fa... • https://git.kernel.org/stable/c/efd183d988b416fcdf6f7c298a17ced4859ca77d •
CVSS: 5.5EPSS: %CPEs: 5EXPL: 0CVE-2022-49519 – ath10k: skip ath10k_halt during suspend for driver state RESTARTING
https://notcve.org/view.php?id=CVE-2022-49519
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ath10k: skip ath10k_halt during suspend for driver state RESTARTING Double free crash is observed when FW recovery(caused by wmi timeout/crash) is followed by immediate suspend event. The FW recovery is triggered by ath10k_core_restart() which calls driver clean up via ath10k_halt(). When the suspend event occurs between the FW recovery, the restart worker thread is put into frozen state until suspend completes. The suspend event triggers a... • https://git.kernel.org/stable/c/8aa3750986ffcf73e0692db3b40dd3a8e8c0c575 •
CVSS: 5.5EPSS: %CPEs: 2EXPL: 0CVE-2022-49518 – ASoC: SOF: ipc3-topology: Correct get_control_data for non bytes payload
https://notcve.org/view.php?id=CVE-2022-49518
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc3-topology: Correct get_control_data for non bytes payload It is possible to craft a topology where sof_get_control_data() would do out of bounds access because it expects that it is only called when the payload is bytes type. Confusingly it also handles other types of controls, but the payload parsing implementation is only valid for bytes. Fix the code to count the non bytes controls and instead of storing a pointer to sof_a... • https://git.kernel.org/stable/c/896b03bb7c7010042786cfae2115083d4c241dd3 •
CVSS: 5.5EPSS: %CPEs: 2EXPL: 0CVE-2022-49516 – ice: always check VF VSI pointer values
https://notcve.org/view.php?id=CVE-2022-49516
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ice: always check VF VSI pointer values The ice_get_vf_vsi function can return NULL in some cases, such as if handling messages during a reset where the VSI is being removed and recreated. Several places throughout the driver do not bother to check whether this VSI pointer is valid. Static analysis tools maybe report issues because they detect paths where a potentially NULL pointer could be dereferenced. Fix this by checking the return valu... • https://git.kernel.org/stable/c/e7be3877589d539c52e5d1d23a625f889b541b9d •
CVSS: 5.5EPSS: %CPEs: 2EXPL: 0CVE-2022-49504 – scsi: lpfc: Inhibit aborts if external loopback plug is inserted
https://notcve.org/view.php?id=CVE-2022-49504
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Inhibit aborts if external loopback plug is inserted After running a short external loopback test, when the external loopback is removed and a normal cable inserted that is directly connected to a target device, the system oops in the llpfc_set_rrq_active() routine. When the loopback was inserted an FLOGI was transmit. As we're looped back, we receive the FLOGI request. The FLOGI is ABTS'd as we recognize the same wppn thus unde... • https://git.kernel.org/stable/c/a1516930cb605caee3bc7b4f3b7994b88c0b8505 •