CVSS: -EPSS: %CPEs: 5EXPL: 0CVE-2022-49131 – ath11k: fix kernel panic during unload/load ath11k modules
https://notcve.org/view.php?id=CVE-2022-49131
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ath11k: fix kernel panic during unload/load ath11k modules Call netif_napi_del() from ath11k_ahb_free_ext_irq() to fix the following kernel panic when unload/load ath11k modules for few iterations. [ 971.201365] Unable to handle kernel paging request at virtual address 6d97a208 [ 971.204227] pgd = 594c2919 [ 971.211478] [6d97a208] *pgd=00000000 [ 971.214120] Internal error: Oops: 5 [#1] PREEMPT SMP ARM [ 971.412024] CPU: 2 PID: 4435 Comm: i... • https://git.kernel.org/stable/c/c6a815f5abdf324108799829dd19ea62fef4bf95 •
CVSS: -EPSS: %CPEs: 5EXPL: 0CVE-2022-49130 – ath11k: mhi: use mhi_sync_power_up()
https://notcve.org/view.php?id=CVE-2022-49130
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ath11k: mhi: use mhi_sync_power_up() If amss.bin was missing ath11k would crash during 'rmmod ath11k_pci'. The reason for that was that we were using mhi_async_power_up() which does not check any errors. But mhi_sync_power_up() on the other hand does check for errors so let's use that to fix the crash. I was not able to find a reason why an async version was used. ath11k_mhi_start() (which enables state ATH11K_MHI_POWER_ON) is called from a... • https://git.kernel.org/stable/c/339bd0b55ecdd0f7f341e9357c4cfde799de9418 •
CVSS: -EPSS: %CPEs: 4EXPL: 0CVE-2022-49129 – mt76: mt7921: fix crash when startup fails.
https://notcve.org/view.php?id=CVE-2022-49129
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: mt76: mt7921: fix crash when startup fails. If the nic fails to start, it is possible that the reset_work has already been scheduled. Ensure the work item is canceled so we do not have use-after-free crash in case cleanup is called before the work item is executed. This fixes crash on my x86_64 apu2 when mt7921k radio fails to work. Radio still fails, but OS does not crash. • https://git.kernel.org/stable/c/38fbe806645090c07aa97171f20fc62c3d7d3a98 •
CVSS: -EPSS: %CPEs: 4EXPL: 0CVE-2022-49128 – drm/bridge: Add missing pm_runtime_put_sync
https://notcve.org/view.php?id=CVE-2022-49128
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/bridge: Add missing pm_runtime_put_sync pm_runtime_get_sync() will increase the rumtime PM counter even when it returns an error. Thus a pairing decrement is needed to prevent refcount leak. Fix this by replacing this API with pm_runtime_resume_and_get(), which will not change the runtime PM counter on error. Besides, a matching decrement is needed on the error handling path to keep the counter balanced. • https://git.kernel.org/stable/c/ff13c90d7f7ab606b37be6d15140d19013d6736c •
CVSS: -EPSS: %CPEs: 2EXPL: 0CVE-2022-49127 – ref_tracker: implement use-after-free detection
https://notcve.org/view.php?id=CVE-2022-49127
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ref_tracker: implement use-after-free detection Whenever ref_tracker_dir_init() is called, mark the struct ref_tracker_dir as dead. Test the dead status from ref_tracker_alloc() and ref_tracker_free() This should detect buggy dev_put()/dev_hold() happening too late in netdevice dismantle process. • https://git.kernel.org/stable/c/3743c9de303fa36c2e2ca2522ab280c52bcafbd2 •
CVSS: -EPSS: %CPEs: 4EXPL: 0CVE-2022-49126 – scsi: mpi3mr: Fix memory leaks
https://notcve.org/view.php?id=CVE-2022-49126
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix memory leaks Fix memory leaks related to operational reply queue's memory segments which are not getting freed while unloading the driver. • https://git.kernel.org/stable/c/5d76a88b8536d75ff5362e232097e85946b8aadf •
CVSS: -EPSS: %CPEs: 2EXPL: 0CVE-2022-49125 – drm/sprd: fix potential NULL dereference
https://notcve.org/view.php?id=CVE-2022-49125
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/sprd: fix potential NULL dereference 'drm' could be null in sprd_drm_shutdown, and drm_warn maybe dereference it, remove this warning log. v1 -> v2: - Split checking platform_get_resource() return value to a separate patch - Use dev_warn() instead of removing the warning log • https://git.kernel.org/stable/c/c3acc8db1bc221604e2db9807f01d8a44b97a64d •
CVSS: -EPSS: %CPEs: 2EXPL: 0CVE-2022-49124 – x86/mce: Work around an erratum on fast string copy instructions
https://notcve.org/view.php?id=CVE-2022-49124
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: x86/mce: Work around an erratum on fast string copy instructions A rare kernel panic scenario can happen when the following conditions are met due to an erratum on fast string copy instructions: 1) An uncorrected error. 2) That error must be in first cache line of a page. 3) Kernel must execute page_copy from the page immediately before that page. The fast string copy instructions ("REP; MOVS*") could consume an uncorrectable memory error i... • https://git.kernel.org/stable/c/ba37c73be3d5632f6fb9fa20b250ce45560ca85d •
CVSS: -EPSS: %CPEs: 2EXPL: 0CVE-2022-49123 – ath11k: Fix frames flush failure caused by deadlock
https://notcve.org/view.php?id=CVE-2022-49123
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ath11k: Fix frames flush failure caused by deadlock We are seeing below warnings: kernel: [25393.301506] ath11k_pci 0000:01:00.0: failed to flush mgmt transmit queue 0 kernel: [25398.421509] ath11k_pci 0000:01:00.0: failed to flush mgmt transmit queue 0 kernel: [25398.421831] ath11k_pci 0000:01:00.0: dropping mgmt frame for vdev 0, is_started 0 this means ath11k fails to flush mgmt. frames because wmi_mgmt_tx_work has no chance to run in 5 ... • https://git.kernel.org/stable/c/33e723dc054edfc94da90eecca3b72cb424ce4a3 •
CVSS: -EPSS: %CPEs: 9EXPL: 0CVE-2022-49122 – dm ioctl: prevent potential spectre v1 gadget
https://notcve.org/view.php?id=CVE-2022-49122
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: dm ioctl: prevent potential spectre v1 gadget It appears like cmd could be a Spectre v1 gadget as it's supplied by a user and used as an array index. Prevent the contents of kernel memory from being leaked to userspace via speculative execution by using array_index_nospec. • https://git.kernel.org/stable/c/76c94651005f58885facf9c973007f5ea01ab01f •