CVSS: -EPSS: %CPEs: 4EXPL: 0CVE-2022-49192 – drivers: ethernet: cpsw: fix panic when interrupt coaleceing is set via ethtool
https://notcve.org/view.php?id=CVE-2022-49192
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: drivers: ethernet: cpsw: fix panic when interrupt coaleceing is set via ethtool cpsw_ethtool_begin directly returns the result of pm_runtime_get_sync when successful. pm_runtime_get_sync returns -error code on failure and 0 on successful resume but also 1 when the device is already active. So the common case for cpsw_ethtool_begin is to return 1. That leads to inconsistent calls to pm_runtime_put in the call-chain so that pm_runtime_put is ... • https://git.kernel.org/stable/c/d43c65b05b848e0b2db1a6c78b02c189da3a95b5 •
CVSS: -EPSS: %CPEs: 9EXPL: 0CVE-2022-49191 – mxser: fix xmit_buf leak in activate when LSR == 0xff
https://notcve.org/view.php?id=CVE-2022-49191
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: mxser: fix xmit_buf leak in activate when LSR == 0xff When LSR is 0xff in ->activate() (rather unlike), we return an error. Provided ->shutdown() is not called when ->activate() fails, nothing actually frees the buffer in this case. Fix this by properly freeing the buffer in a designated label. We jump there also from the "!info->type" if now too. • https://git.kernel.org/stable/c/6769140d304731f0a3b177470a2adb4bacd9036b •
CVSS: -EPSS: %CPEs: 4EXPL: 0CVE-2022-49190 – kernel/resource: fix kfree() of bootmem memory again
https://notcve.org/view.php?id=CVE-2022-49190
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: kernel/resource: fix kfree() of bootmem memory again Since commit ebff7d8f270d ("mem hotunplug: fix kfree() of bootmem memory"), we could get a resource allocated during boot via alloc_resource(). And it's required to release the resource using free_resource(). Howerver, many people use kfree directly which will result in kernel BUG. In order to fix this without fixing every call site, just leak a couple of bytes in such corner case. • https://git.kernel.org/stable/c/ebff7d8f270d045338d9f4796014f4db429a17f9 •
CVSS: -EPSS: %CPEs: 6EXPL: 0CVE-2022-49189 – clk: qcom: clk-rcg2: Update logic to calculate D value for RCG
https://notcve.org/view.php?id=CVE-2022-49189
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: clk: qcom: clk-rcg2: Update logic to calculate D value for RCG The display pixel clock has a requirement on certain newer platforms to support M/N as (2/3) and the final D value calculated results in underflow errors. As the current implementation does not check for D value is within the accepted range for a given M & N value. Update the logic to calculate the final D value based on the range. • https://git.kernel.org/stable/c/99cbd064b059f222c8839ba433a68b2d6ee33066 •
CVSS: -EPSS: %CPEs: 5EXPL: 0CVE-2022-49188 – remoteproc: qcom_q6v5_mss: Fix some leaks in q6v5_alloc_memory_region
https://notcve.org/view.php?id=CVE-2022-49188
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: remoteproc: qcom_q6v5_mss: Fix some leaks in q6v5_alloc_memory_region The device_node pointer is returned by of_parse_phandle() or of_get_child_by_name() with refcount incremented. We should use of_node_put() on it when done. This function only call of_node_put(node) when of_address_to_resource succeeds, missing error cases. • https://git.kernel.org/stable/c/051fb70fd4ea40fbc7139186a4890b2fe5cb1e76 •
CVSS: -EPSS: %CPEs: 4EXPL: 0CVE-2022-49187 – clk: Fix clk_hw_get_clk() when dev is NULL
https://notcve.org/view.php?id=CVE-2022-49187
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: clk: Fix clk_hw_get_clk() when dev is NULL Any registered clk_core structure can have a NULL pointer in its dev field. While never actually documented, this is evidenced by the wide usage of clk_register and clk_hw_register with a NULL device pointer, and the fact that the core of_clk_hw_register() function also passes a NULL device pointer. A call to clk_hw_get_clk() on a clk_hw struct whose clk_core is in that case will result in a NULL p... • https://git.kernel.org/stable/c/30d6f8c15d2cd877c1f3d47d8a1064649ebe58e2 •
CVSS: -EPSS: %CPEs: 2EXPL: 0CVE-2022-49186 – clk: visconti: prevent array overflow in visconti_clk_register_gates()
https://notcve.org/view.php?id=CVE-2022-49186
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: clk: visconti: prevent array overflow in visconti_clk_register_gates() This code was using -1 to represent that there was no reset function. Unfortunately, the -1 was stored in u8 so the if (clks[i].rs_id >= 0) condition was always true. This lead to an out of bounds access in visconti_clk_register_gates(). • https://git.kernel.org/stable/c/b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa •
CVSS: -EPSS: %CPEs: 9EXPL: 0CVE-2022-49185 – pinctrl: nomadik: Add missing of_node_put() in nmk_pinctrl_probe
https://notcve.org/view.php?id=CVE-2022-49185
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: pinctrl: nomadik: Add missing of_node_put() in nmk_pinctrl_probe This node pointer is returned by of_parse_phandle() with refcount incremented in this function. Calling of_node_put() to avoid the refcount leak. • https://git.kernel.org/stable/c/32e67eee670e1254ee5ab41e2f454680acb9c17c •
CVSS: -EPSS: %CPEs: 4EXPL: 0CVE-2022-49184 – net: sparx5: switchdev: fix possible NULL pointer dereference
https://notcve.org/view.php?id=CVE-2022-49184
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: net: sparx5: switchdev: fix possible NULL pointer dereference As the possible failure of the allocation, devm_kzalloc() may return NULL pointer. Therefore, it should be better to check the 'db' in order to prevent the dereference of NULL pointer. • https://git.kernel.org/stable/c/10615907e9b51c9ae92f3a6ecabd01c482f20f32 •
CVSS: -EPSS: %CPEs: 5EXPL: 0CVE-2022-49183 – net/sched: act_ct: fix ref leak when switching zones
https://notcve.org/view.php?id=CVE-2022-49183
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: net/sched: act_ct: fix ref leak when switching zones When switching zones or network namespaces without doing a ct clear in between, it is now leaking a reference to the old ct entry. That's because tcf_ct_skb_nfct_cached() returns false and tcf_ct_flow_table_lookup() may simply overwrite it. The fix is to, as the ct entry is not reusable, free it already at tcf_ct_skb_nfct_cached(). • https://git.kernel.org/stable/c/a95ea90deb3071c1ded77a05e91cfebc5238d908 •