CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-49459 – thermal/drivers/broadcom: Fix potential NULL dereference in sr_thermal_probe
https://notcve.org/view.php?id=CVE-2022-49459
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: thermal/drivers/broadcom: Fix potential NULL dereference in sr_thermal_probe platform_get_resource() may return NULL, add proper check to avoid potential NULL dereferencing. In the Linux kernel, the following vulnerability has been resolved: thermal/drivers/broadcom: Fix potential NULL dereference in sr_thermal_probe platform_get_resource() may return NULL, add proper check to avoid potential NULL dereferencing. • https://git.kernel.org/stable/c/250e211057c7237dc75634b1372a1a3bd58dcd96 •
CVSS: 5.6EPSS: 0%CPEs: 4EXPL: 0CVE-2022-49458 – drm/msm: don't free the IRQ if it was not requested
https://notcve.org/view.php?id=CVE-2022-49458
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/msm: don't free the IRQ if it was not requested As msm_drm_uninit() is called from the msm_drm_init() error path, additional care should be necessary as not to call the free_irq() for the IRQ that was not requested before (because an error occured earlier than the request_irq() call). This fixed the issue reported with the following backtrace: [ 8.571329] Trying to free already-free IRQ 187 [ 8.571339] WARNING: CPU: 0 PID: 76 at kernel/... • https://git.kernel.org/stable/c/f026e431cf861197dc03217d1920b38b80b31dd9 •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2022-49457 – ARM: versatile: Add missing of_node_put in dcscb_init
https://notcve.org/view.php?id=CVE-2022-49457
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ARM: versatile: Add missing of_node_put in dcscb_init The device_node pointer is returned by of_find_compatible_node with refcount incremented. We should use of_node_put() to avoid the refcount leak. In the Linux kernel, the following vulnerability has been resolved: ARM: versatile: Add missing of_node_put in dcscb_init The device_node pointer is returned by of_find_compatible_node with refcount incremented. We should use of_node_put() to a... • https://git.kernel.org/stable/c/2d7b23db35254b7d46e852967090c64cdccf24da •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-49455 – misc: ocxl: fix possible double free in ocxl_file_register_afu
https://notcve.org/view.php?id=CVE-2022-49455
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: misc: ocxl: fix possible double free in ocxl_file_register_afu info_release() will be called in device_unregister() when info->dev's reference count is 0. So there is no need to call ocxl_afu_put() and kfree() again. Fix this by adding free_minor() and return to err_unregister error path. In the Linux kernel, the following vulnerability has been resolved: misc: ocxl: fix possible double free in ocxl_file_register_afu info_release() will be ... • https://git.kernel.org/stable/c/75ca758adbafc81804c39b2c200ecdc819a6c042 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-49454 – PCI: mediatek: Fix refcount leak in mtk_pcie_subsys_powerup()
https://notcve.org/view.php?id=CVE-2022-49454
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: PCI: mediatek: Fix refcount leak in mtk_pcie_subsys_powerup() The of_find_compatible_node() function returns a node pointer with refcount incremented, We should use of_node_put() on it when done Add the missing of_node_put() to release the refcount. In the Linux kernel, the following vulnerability has been resolved: PCI: mediatek: Fix refcount leak in mtk_pcie_subsys_powerup() The of_find_compatible_node() function returns a node pointer wi... • https://git.kernel.org/stable/c/87e8657ba99cac87b84c7f8ead91b44d88345504 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2022-49453 – soc: ti: ti_sci_pm_domains: Check for null return of devm_kcalloc
https://notcve.org/view.php?id=CVE-2022-49453
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: soc: ti: ti_sci_pm_domains: Check for null return of devm_kcalloc The allocation funciton devm_kcalloc may fail and return a null pointer, which would cause a null-pointer dereference later. It might be better to check it and directly return -ENOMEM just like the usage of devm_kcalloc in previous code. In the Linux kernel, the following vulnerability has been resolved: soc: ti: ti_sci_pm_domains: Check for null return of devm_kcalloc The al... • https://git.kernel.org/stable/c/05efc4591f80582b6fe53366b70b6a35a42fd255 •
CVSS: 8.5EPSS: 0%CPEs: 7EXPL: 0CVE-2022-49451 – firmware: arm_scmi: Fix list protocols enumeration in the base protocol
https://notcve.org/view.php?id=CVE-2022-49451
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Fix list protocols enumeration in the base protocol While enumerating protocols implemented by the SCMI platform using BASE_DISCOVER_LIST_PROTOCOLS, the number of returned protocols is currently validated in an improper way since the check employs a sum between unsigned integers that could overflow and cause the check itself to be silently bypassed if the returned value 'loop_num_ret' is big enough. Fix the validation av... • https://git.kernel.org/stable/c/b6f20ff8bd94ad34032804a60bab5ee56752007e •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2022-49450 – rxrpc: Fix listen() setting the bar too high for the prealloc rings
https://notcve.org/view.php?id=CVE-2022-49450
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix listen() setting the bar too high for the prealloc rings AF_RXRPC's listen() handler lets you set the backlog up to 32 (if you bump up the sysctl), but whilst the preallocation circular buffers have 32 slots in them, one of them has to be a dead slot because we're using CIRC_CNT(). This means that listen(rxrpc_sock, 32) will cause an oops when the socket is closed because rxrpc_service_prealloc_one() allocated one too many calls ... • https://git.kernel.org/stable/c/00e907127e6f86d0f9b122d9b4347a8aa09a8b61 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2022-49449 – pinctrl: renesas: rzn1: Fix possible null-ptr-deref in sh_pfc_map_resources()
https://notcve.org/view.php?id=CVE-2022-49449
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: pinctrl: renesas: rzn1: Fix possible null-ptr-deref in sh_pfc_map_resources() It will cause null-ptr-deref when using 'res', if platform_get_resource() returns NULL, so move using 'res' after devm_ioremap_resource() that will check it to avoid null-ptr-deref. And use devm_platform_get_and_ioremap_resource() to simplify code. In the Linux kernel, the following vulnerability has been resolved: pinctrl: renesas: rzn1: Fix possible null-ptr-der... • https://git.kernel.org/stable/c/b646e0cfeb38bf5f1944fd548f1dfa9b129fa00c •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-49448 – soc: bcm: Check for NULL return of devm_kzalloc()
https://notcve.org/view.php?id=CVE-2022-49448
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: soc: bcm: Check for NULL return of devm_kzalloc() As the potential failure of allocation, devm_kzalloc() may return NULL. Then the 'pd->pmb' and the follow lines of code may bring null pointer dereference. Therefore, it is better to check the return value of devm_kzalloc() to avoid this confusion. In the Linux kernel, the following vulnerability has been resolved: soc: bcm: Check for NULL return of devm_kzalloc() As the potential failure of... • https://git.kernel.org/stable/c/8bcac4011ebe0dbdd46fd55b036ee855c95702d3 •