CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50210 – MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
https://notcve.org/view.php?id=CVE-2022-50210
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS is selected, cpu_max_bits_warn() generates a runtime warning similar as below while we show /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit) instead of NR_CPUS to iterate CPUs. [ 3.052463] ------------[ cut here ]------------ [ 3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x... • https://git.kernel.org/stable/c/d3ac4e47510ec0753ebe1e418a334ad202784aa8 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50206 – arm64: fix oops in concurrently setting insn_emulation sysctls
https://notcve.org/view.php?id=CVE-2022-50206
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: arm64: fix oops in concurrently setting insn_emulation sysctls emulation_proc_handler() changes table->data for proc_dointvec_minmax and can generate the following Oops if called concurrently with itself: | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010 | Internal error: Oops: 96000006 [#1] SMP | Call trace: | update_insn_emulation_mode+0xc0/0x148 | emulation_proc_handler+0x64/0xb8 | proc_sys_call_handl... • https://git.kernel.org/stable/c/9d5fec6ba2e4117d196a8259ab54615ffe562460 •
CVSS: 7.1EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50205 – ext2: Add more validity checks for inode counts
https://notcve.org/view.php?id=CVE-2022-50205
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ext2: Add more validity checks for inode counts Add checks verifying number of inodes stored in the superblock matches the number computed from number of inodes per group. Also verify we have at least one block worth of inodes per group. This prevents crashes on corrupted filesystems. In the Linux kernel, the following vulnerability has been resolved: ext2: Add more validity checks for inode counts Add checks verifying number of inodes stor... • https://git.kernel.org/stable/c/0bcdc31094a12b4baf59e241feabc9787cf635fa •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-50204 – ARM: OMAP2+: pdata-quirks: Fix refcount leak bug
https://notcve.org/view.php?id=CVE-2022-50204
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ARM: OMAP2+: pdata-quirks: Fix refcount leak bug In pdata_quirks_init_clocks(), the loop contains of_find_node_by_name() but without corresponding of_node_put(). In the Linux kernel, the following vulnerability has been resolved: ARM: OMAP2+: pdata-quirks: Fix refcount leak bug In pdata_quirks_init_clocks(), the loop contains of_find_node_by_name() but without corresponding of_node_put(). • https://git.kernel.org/stable/c/75f23d72b6e0a34c8a0e8d275b69ba1e6dd0f15f •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50203 – ARM: OMAP2+: display: Fix refcount leak bug
https://notcve.org/view.php?id=CVE-2022-50203
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ARM: OMAP2+: display: Fix refcount leak bug In omapdss_init_fbdev(), of_find_node_by_name() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore. In the Linux kernel, the following vulnerability has been resolved: ARM: OMAP2+: display: Fix refcount leak bug In omapdss_init_fbdev(), of_find_node_by_name() will return a node pointer with refcount incremented. We should use of_node_put()... • https://git.kernel.org/stable/c/bdbdf69d5b78c5712c60c0004fa6aed12da36e26 •
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: 7.0EPSS: 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 • CWE-125: Out-of-bounds Read •
CVSS: 7.8EPSS: 0%CPEs: 7EXPL: 0CVE-2022-50087 – firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails
https://notcve.org/view.php?id=CVE-2022-50087
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails When scpi probe fails, at any point, we need to ensure that the scpi_info is not set and will remain NULL until the probe succeeds. If it is not taken care, then it could result use-after-free as the value is exported via get_scpi_ops() and could refer to a memory allocated via devm_kzalloc() but freed when the probe fails. In the Linux kernel, the following vulnerabili... • https://git.kernel.org/stable/c/5aa558232edc30468d1f35108826dd5b3ffe978f •
CVSS: 7.1EPSS: 0%CPEs: 4EXPL: 0CVE-2022-50086 – block: don't allow the same type rq_qos add more than once
https://notcve.org/view.php?id=CVE-2022-50086
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: block: don't allow the same type rq_qos add more than once In our test of iocost, we encountered some list add/del corruptions of inner_walk list in ioc_timer_fn. The reason can be described as follows: cpu 0 cpu 1 ioc_qos_write ioc_qos_write ioc = q_to_ioc(queue); if (!ioc) { ioc = kzalloc(); ioc = q_to_ioc(queue); if (!ioc) { ioc = kzalloc(); ... rq_qos_add(q, rqos); } ... rq_qos_add(q, rqos); ... } When the io.cost.qos file is written by... • https://git.kernel.org/stable/c/0b7f5d7a4d2a72ad9de04ab8ccba2a31904aa638 •