
CVE-2022-49433 – RDMA/hfi1: Prevent use of lock before it is initialized
https://notcve.org/view.php?id=CVE-2022-49433
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Prevent use of lock before it is initialized If there is a failure during probe of hfi1 before the sdma_map_lock is initialized, the call to hfi1_free_devdata() will attempt to use a lock that has not been initialized. In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Prevent use of lock before it is initialized If there is a failure during probe of hfi1 before the sdma_map_lock is initi... • https://git.kernel.org/stable/c/7724105686e718ac476a6ad3304fea2fbcfcffde •

CVE-2022-49432 – powerpc/xics: fix refcount leak in icp_opal_init()
https://notcve.org/view.php?id=CVE-2022-49432
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: powerpc/xics: fix refcount leak in icp_opal_init() The of_find_compatible_node() function returns a node pointer with refcount incremented, use of_node_put() on it when done. In the Linux kernel, the following vulnerability has been resolved: powerpc/xics: fix refcount leak in icp_opal_init() The of_find_compatible_node() function returns a node pointer with refcount incremented, use of_node_put() on it when done. • https://git.kernel.org/stable/c/977dbc81d0f866ef63b93c127b7404f07734b3cc •

CVE-2022-49431 – powerpc/iommu: Add missing of_node_put in iommu_init_early_dart
https://notcve.org/view.php?id=CVE-2022-49431
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: powerpc/iommu: Add missing of_node_put in iommu_init_early_dart The device_node pointer is returned by of_find_compatible_node with refcount incremented. ... In the Linux kernel, the following vulnerability has been resolved: powerpc/iommu: Add missing of_node_put in iommu_init_early_dart The device_node pointer is returned by of_find_compatible_node with refcount incremented. • https://git.kernel.org/stable/c/cb4f2dc513e99c5d0485661f114e4dda73612d10 •

CVE-2022-49430 – Input: gpio-keys - cancel delayed work only in case of GPIO
https://notcve.org/view.php?id=CVE-2022-49430
26 Feb 2025 — This fixes the issue seen below when the gpio_keys module is unloaded and an interrupt pin is used instead of GPIO: [ 360.297569] ------------[ cut here ]------------ [ 360.302303] WARNING: CPU: 0 PID: 237 at kernel/workqueue.c:3066 __flush_work+0x414/0x470 [ 360.310531] Modules linked in: gpio_keys(-) [ 360.314797] CPU: 0 PID: 237 Comm: rmmod Not tainted 5.18.0-rc5-arm64-renesas-00116-g73636105874d-dirty #166 [ 360.324662] Hardware name: Renesas SMARC EVK based on r9a07g054l2 (DT) [ 360.331270] pstate: 604... • https://git.kernel.org/stable/c/96c460687813915dedca9dd7d04ae0e90607fd79 •

CVE-2022-49429 – RDMA/hfi1: Prevent panic when SDMA is disabled
https://notcve.org/view.php?id=CVE-2022-49429
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Prevent panic when SDMA is disabled If the hfi1 module is loaded with HFI1_CAP_SDMA off, a call to hfi1_write_iter() will dereference a NULL pointer and panic. ... In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Prevent panic when SDMA is disabled If the hfi1 module is loaded with HFI1_CAP_SDMA off, a call to hfi1_write_iter() will dereference a NULL pointer and panic. • https://git.kernel.org/stable/c/33794e8e9bcb4affc0ebff9cdec85acc8b8a1762 • CWE-476: NULL Pointer Dereference •

CVE-2022-49428 – f2fs: fix to do sanity check on inline_dots inode
https://notcve.org/view.php?id=CVE-2022-49428
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on inline_dots inode As Wenqing reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?... In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on inline_dots inode As Wenqing reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi? • https://git.kernel.org/stable/c/510022a85839a8409d1e6a519bb86ce71a84f30a •

CVE-2022-49427 – iommu/mediatek: Remove clk_disable in mtk_iommu_remove
https://notcve.org/view.php?id=CVE-2022-49427
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Remove clk_disable in mtk_iommu_remove After the commit b34ea31fe013 ("iommu/mediatek: Always enable the clk on resume"), the iommu clock is controlled by the runtime callback. thus remove the clk control in the mtk_iommu_remove. • https://git.kernel.org/stable/c/b34ea31fe013569d42b7e8681ef3f717f77c5b72 •

CVE-2022-49426 – iommu/arm-smmu-v3-sva: Fix mm use-after-free
https://notcve.org/view.php?id=CVE-2022-49426
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-v3-sva: Fix mm use-after-free We currently call arm64_mm_context_put() without holding a reference to the mm, which can result in use-after-free. ... In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-v3-sva: Fix mm use-after-free We currently call arm64_mm_context_put() without holding a reference to the mm, which can result in use-after-free. • https://git.kernel.org/stable/c/32784a9562fb0518b12e9797ee2aec52214adf6f • CWE-416: Use After Free •

CVE-2022-49425 – f2fs: fix dereference of stale list iterator after loop body
https://notcve.org/view.php?id=CVE-2022-49425
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: f2fs: fix dereference of stale list iterator after loop body The list iterator variable will be a bogus pointer if no break was hit. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix dereference of stale list iterator after loop body The list iterator variable will be a bogus pointer if no break was hit. • https://git.kernel.org/stable/c/8c242db9b8c01b252290e23827163787f07e01d1 •

CVE-2022-49424 – iommu/mediatek: Fix NULL pointer dereference when printing dev_name
https://notcve.org/view.php?id=CVE-2022-49424
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Fix NULL pointer dereference when printing dev_name When larbdev is NULL (in the case I hit, the node is incorrectly set iommus = <&iommu NUM>), it will cause device_link_add() fail and kernel crashes when we try to print dev_name(larbdev). In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Fix NULL pointer dereference when printing dev_name When larbdev is NULL (in the case I h... • https://git.kernel.org/stable/c/77fbe028d5a3f7fc6060c4454ead9510533acd1e •