CVSS: 6.2EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50202 – PM: hibernate: defer device probing when resuming from hibernation
https://notcve.org/view.php?id=CVE-2022-50202
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: PM: hibernate: defer device probing when resuming from hibernation syzbot is reporting hung task at misc_open() [1], for there is a race window of AB-BA deadlock which involves probe_count variable. Currently wait_for_device_probe() from snapshot_open() from misc_open() can sleep forever with misc_mtx held if probe_count cannot become 0. When a device is probed by hub_event() work function, probe_count is incremented before the probe functi... • https://git.kernel.org/stable/c/8c90947e5f1801e6c7120021c6ea0f3ad6a4eb91 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-50201 – selinux: fix memleak in security_read_state_kernel()
https://notcve.org/view.php?id=CVE-2022-50201
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: selinux: fix memleak in security_read_state_kernel() In this function, it directly returns the result of __security_read_policy without freeing the allocated memory in *data, cause memory leak issue, so free the memory if __security_read_policy failed. [PM: subject line tweak] In the Linux kernel, the following vulnerability has been resolved: selinux: fix memleak in security_read_state_kernel() In this function, it directly returns the res... • https://git.kernel.org/stable/c/c877c5217145bda8fd95f506bf42f8d981afa57d •
CVSS: 5.6EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50200 – selinux: Add boundary check in put_entry()
https://notcve.org/view.php?id=CVE-2022-50200
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: selinux: Add boundary check in put_entry() Just like next_entry(), boundary check is necessary to prevent memory out-of-bound access. In the Linux kernel, the following vulnerability has been resolved: selinux: Add boundary check in put_entry() Just like next_entry(), boundary check is necessary to prevent memory out-of-bound access. • https://git.kernel.org/stable/c/2dabe6a872a5744865372eb30ea51e8ccd21305a •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50199 – ARM: OMAP2+: Fix refcount leak in omapdss_init_of
https://notcve.org/view.php?id=CVE-2022-50199
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ARM: OMAP2+: Fix refcount leak in omapdss_init_of omapdss_find_dss_of_node() calls of_find_compatible_node() to get device node. of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() in later error path and normal path. In the Linux kernel, the following vulnerability has been resolved: ARM: OMAP2+: Fix refcount leak in omapdss_init_of omapdss_find_... • https://git.kernel.org/stable/c/e0c827aca0730b51f38081aa4e8ecf0912aab55f •
CVSS: 7.1EPSS: 0%CPEs: 7EXPL: 0CVE-2022-50198 – ARM: OMAP2+: Fix refcount leak in omap3xxx_prm_late_init
https://notcve.org/view.php?id=CVE-2022-50198
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ARM: OMAP2+: Fix refcount leak in omap3xxx_prm_late_init of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak. In the Linux kernel, the following vulnerability has been resolved: ARM: OMAP2+: Fix refcount leak in omap3xxx_prm_late_init of_find_matching_node() returns a node pointer with refcount incremented, we shou... • https://git.kernel.org/stable/c/1e037794f7f00ff464db446ace892dae84175a6a •
CVSS: 7.1EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50197 – cpufreq: zynq: Fix refcount leak in zynq_get_revision
https://notcve.org/view.php?id=CVE-2022-50197
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: cpufreq: zynq: Fix refcount leak in zynq_get_revision of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak. In the Linux kernel, the following vulnerability has been resolved: cpufreq: zynq: Fix refcount leak in zynq_get_revision of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node... • https://git.kernel.org/stable/c/00f7dc636366f72474b1896f4990b3c086cd2c6d •
CVSS: 6.4EPSS: 0%CPEs: 5EXPL: 0CVE-2022-50196 – soc: qcom: ocmem: Fix refcount leak in of_get_ocmem
https://notcve.org/view.php?id=CVE-2022-50196
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: soc: qcom: ocmem: Fix refcount leak in of_get_ocmem of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak. of_node_put() will check NULL pointer. In the Linux kernel, the following vulnerability has been resolved: soc: qcom: ocmem: Fix refcount leak in of_get_ocmem of_parse_phandle() returns a node pointer with refcount i... • https://git.kernel.org/stable/c/88c1e9404f1deee02e52d13aae3d9ee2cabd66f5 •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-50195 – ARM: dts: qcom: replace gcc PXO with pxo_board fixed clock
https://notcve.org/view.php?id=CVE-2022-50195
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ARM: dts: qcom: replace gcc PXO with pxo_board fixed clock Replace gcc PXO phandle to pxo_board fixed clock declared in the dts. gcc driver doesn't provide PXO_SRC as it's a fixed-clock. This cause a kernel panic if any driver actually try to use it. In the Linux kernel, the following vulnerability has been resolved: ARM: dts: qcom: replace gcc PXO with pxo_board fixed clock Replace gcc PXO phandle to pxo_board fixed clock declared in the d... • https://git.kernel.org/stable/c/40cf5c884a965554a424797afb424ffbca4c24b3 •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50194 – soc: qcom: aoss: Fix refcount leak in qmp_cooling_devices_register
https://notcve.org/view.php?id=CVE-2022-50194
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: soc: qcom: aoss: Fix refcount leak in qmp_cooling_devices_register Every iteration of for_each_available_child_of_node() decrements the reference count of the previous node. When breaking early from a for_each_available_child_of_node() loop, we need to explicitly call of_node_put() on the child node. Add missing of_node_put() to avoid refcount leak. In the Linux kernel, the following vulnerability has been resolved: soc: qcom: aoss: Fix ref... • https://git.kernel.org/stable/c/05589b30b21ac0273970b61edd50c07d2ba156af •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50193 – erofs: wake up all waiters after z_erofs_lzma_head ready
https://notcve.org/view.php?id=CVE-2022-50193
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: erofs: wake up all waiters after z_erofs_lzma_head ready When the user mounts the erofs second times, the decompression thread may hung. The problem happens due to a sequence of steps like the following: 1) Task A called z_erofs_load_lzma_config which obtain all of the node from the z_erofs_lzma_head. 2) At this time, task B called the z_erofs_lzma_decompress and wanted to get a node. But the z_erofs_lzma_head was empty, the Task B had to s... • https://git.kernel.org/stable/c/622ceaddb7649ca328832f50ba1400af778d75fa •