CVSS: 7.1EPSS: 0%CPEs: 4EXPL: 0CVE-2022-50021 – ext4: block range must be validated before use in ext4_mb_clear_bb()
https://notcve.org/view.php?id=CVE-2022-50021
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ext4: block range must be validated before use in ext4_mb_clear_bb() Block range to free is validated in ext4_free_blocks() using ext4_inode_block_valid() and then it's passed to ext4_mb_clear_bb(). However in some situations on bigalloc file system the range might be adjusted after the validation in ext4_free_blocks() which can lead to troubles on corrupted file systems such as one found by syzkaller that resulted in the following BUG kern... • https://git.kernel.org/stable/c/7550aade978371ac582f6d43b14c4cb89ca54463 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50020 – ext4: avoid resizing to a partial cluster size
https://notcve.org/view.php?id=CVE-2022-50020
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ext4: avoid resizing to a partial cluster size This patch avoids an attempt to resize the filesystem to an unaligned cluster boundary. An online resize to a size that is not integral to cluster size results in the last iteration attempting to grow the fs by a negative amount, which trips a BUG_ON and leaves the fs with a corrupted in-memory superblock. In the Linux kernel, the following vulnerability has been resolved: ext4: avoid resizing ... • https://git.kernel.org/stable/c/53f62a4201be1cfc1e3c971e566888b182c3ffb0 •
CVSS: 7.1EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50019 – tty: serial: Fix refcount leak bug in ucc_uart.c
https://notcve.org/view.php?id=CVE-2022-50019
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: tty: serial: Fix refcount leak bug in ucc_uart.c In soc_info(), of_find_node_by_type() 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: tty: serial: Fix refcount leak bug in ucc_uart.c In soc_info(), of_find_node_by_type() will return a node pointer with refcount incremented. We should use of_node_put() when it i... • https://git.kernel.org/stable/c/8245e7d1d7f75a9255ad1e8146752e5051d528b8 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50017 – mips: cavium-octeon: Fix missing of_node_put() in octeon2_usb_clocks_start
https://notcve.org/view.php?id=CVE-2022-50017
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: mips: cavium-octeon: Fix missing of_node_put() in octeon2_usb_clocks_start We should call of_node_put() for the reference 'uctl_node' returned by of_get_parent() which will increase the refcount. Otherwise, there will be a refcount leak bug. In the Linux kernel, the following vulnerability has been resolved: mips: cavium-octeon: Fix missing of_node_put() in octeon2_usb_clocks_start We should call of_node_put() for the reference 'uctl_node' ... • https://git.kernel.org/stable/c/9d1afa0169a84dcd5b79901d792edeb8403684ab •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-50016 – ASoC: SOF: Intel: cnl: Do not process IPC reply before firmware boot
https://notcve.org/view.php?id=CVE-2022-50016
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Intel: cnl: Do not process IPC reply before firmware boot It is not yet clear, but it is possible to create a firmware so broken that it will send a reply message before a FW_READY message (it is not yet clear if FW_READY will arrive later). Since the reply_data is allocated only after the FW_READY message, this will lead to a NULL pointer dereference if not filtered out. The issue was reported with IPC4 firmware but the same con... • https://git.kernel.org/stable/c/273020522ef62361c5d86eebe45a72418ed8dea4 •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-50015 – ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot
https://notcve.org/view.php?id=CVE-2022-50015
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot It is not yet clear, but it is possible to create a firmware so broken that it will send a reply message before a FW_READY message (it is not yet clear if FW_READY will arrive later). Since the reply_data is allocated only after the FW_READY message, this will lead to a NULL pointer dereference if not filtered out. The issue was reported with IPC4 firmware but the same... • https://git.kernel.org/stable/c/6e9cde974863dc9d9c6cdb178f625e410c5be3d0 •
CVSS: 7.8EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50013 – f2fs: fix to avoid use f2fs_bug_on() in f2fs_new_node_page()
https://notcve.org/view.php?id=CVE-2022-50013
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid use f2fs_bug_on() in f2fs_new_node_page() As Dipanjan Das
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50012 – powerpc/64: Init jump labels before parse_early_param()
https://notcve.org/view.php?id=CVE-2022-50012
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: powerpc/64: Init jump labels before parse_early_param() On 64-bit, calling jump_label_init() in setup_feature_keys() is too late because static keys may be used in subroutines of parse_early_param() which is again subroutine of early_init_devtree(). For example booting with "threadirqs": static_key_enable_cpuslocked(): static key '0xc000000002953260' used before call to jump_label_init() WARNING: CPU: 0 PID: 0 at kernel/jump_label.c:166 sta... • https://git.kernel.org/stable/c/c4ced9fd10073adc854919976b88ad6004271119 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50011 – venus: pm_helpers: Fix warning in OPP during probe
https://notcve.org/view.php?id=CVE-2022-50011
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: venus: pm_helpers: Fix warning in OPP during probe Fix the following WARN triggered during Venus driver probe on 5.19.0-rc8-next-20220728: WARNING: CPU: 7 PID: 339 at drivers/opp/core.c:2471 dev_pm_opp_set_config+0x49c/0x610 Modules linked in: qcom_spmi_adc5 rtc_pm8xxx qcom_spmi_adc_tm5 leds_qcom_lpg led_class_multicolor qcom_pon qcom_vadc_common venus_core(+) qcom_spmi_temp_alarm v4l2_mem2mem videobuf2_v4l2 msm(+) videobuf2_common crct10di... • https://git.kernel.org/stable/c/0bdec5eed69c73886af4cfbb94b663e1e10b8344 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50010 – video: fbdev: i740fb: Check the argument of i740_calc_vclk()
https://notcve.org/view.php?id=CVE-2022-50010
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: video: fbdev: i740fb: Check the argument of i740_calc_vclk() Since the user can control the arguments of the ioctl() from the user space, under special arguments that may result in a divide-by-zero bug. If the user provides an improper 'pixclock' value that makes the argumet of i740_calc_vclk() less than 'I740_RFREQ_FIX', it will cause a divide-by-zero bug in: drivers/video/fbdev/i740fb.c:353 p_best = min(15, ilog2(I740_MAX_VCO_FREQ / (freq... • https://git.kernel.org/stable/c/59cefb583c984c0da8cf21a4c57d26d5a20dff5c •