ALT-BU-2022-5908-18
Branch p9 update bulletin.
Package kernel-image-std-def updated to version 5.4.211-alt1 for branch p9 in task 305756.
Closed vulnerabilities
Modified: 2024-09-30
BDU:2022-03162
Уязвимость функции ath9k_htc_wait_for_target драйвера беспроводного адаптера Atheros ядра операционной системы Linux, позволяющая нарушителю получить доступ к памяти ядра, что может привести к сбою системы или утечке внутренней информации ядра
Modified: 2024-12-05
BDU:2022-05178
Уязвимость функции route4_change (net/sched/cls_route.c) ядра операционной системы Linux, позволяющая нарушителю выполнить произвольный код или вызвать аварийное завершение работы приложения
Modified: 2024-09-13
BDU:2022-06017
Уязвимость реализации функции take_rmap_locks() ядра операционных систем Linux, позволяющая нарушителю вызвать отказ в обслуживании
Modified: 2025-01-29
BDU:2022-06616
Уязвимость функции devlink_param_set/devlink_param_get (net/core/devlink.c) компонента IPsec ядра операционной системы Linux, позволяющая нарушителю выполнить произвольный код
Modified: 2024-09-30
BDU:2023-04272
Уязвимость функции idt77252_exit() в модуле drivers/atm/idt77252.c сетевого драйвера ATM idt77252 операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
Modified: 2025-08-19
BDU:2024-01697
Уязвимость функции i2c_put_adapter() драйвера шины I2C ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-01522
Уязвимость функции raid5_end_write_request() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-01523
Уязвимость функций lpfc_debugfs_multixripools_write() и lpfc_debugfs_nvmestat_write() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-01546
Уязвимость функции attempt_restore_of_faulty_devices() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-01549
Уязвимость функций scpi_init_versions() и scpi_probe() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-01550
Уязвимость функций usbnet_stop() и usbnet_disconnect() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02255
Уязвимость функции raid_status() в модуле drivers/md/dm-raid.c драйвера нескольких устройств (RAID и LVM) ядра операционной системы Linux, позволяющая нарушителю получить доступ к защищаемой информации или вызвать отказ в обслуживании
BDU:2026-02256
Уязвимость функции put_entry() в модуле security/selinux/ss/policydb.h ядра операционной системы Linux, позволяющая нарушителю получить доступ к защищаемой информации или вызвать отказ в обслуживании
BDU:2026-02257
Уязвимость функции raid10_remove_disk() в модуле drivers/md/raid10.c драйвера нескольких устройств (RAID и LVM) ядра операционной системы Linux, позволяющая нарушителю получить доступ к защищаемой информации или вызвать отказ в обслуживании
BDU:2026-02337
Уязвимость функций sg_read() и sg_get_rq_mark() в модуле drivers/scsi/sg.c драйвера устройств SCSI ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-02366
Уязвимость функции ext4_resize_fs() в модуле fs/ext4/resize.c файловой системы Ext4 ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-02576
Уязвимость функции cdns3_wa2_remove_old_request() в модуле drivers/usb/cdns3/cdns3-gadget.c драйвера устройств шины USB ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02580
Уязвимость функций iavf_init_asq() и iavf_init_arq() в модуле drivers/net/ethernet/intel/iavf/iavf_adminq.c драйвера сетевых адаптеров Ethernet Intel ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02582
Уязвимость функции early_init_devtree() в модуле arch/powerpc/kernel/prom.c поддержки платформы PowerPC ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02660
Уязвимость функции f2fs_new_node_page() в модуле fs/f2fs/node.c файловой системы F2FS ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02664
Уязвимость функции mv88e6060_setup_port() в модуле drivers/net/dsa/mv88e6060.c драйвера DSA ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02665
Уязвимость функции vt8623fb_set_par() в модуле drivers/video/fbdev/vt8623fb.c драйвера устройств кадрового буфера ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02791
Уязвимость функции meson_vpu_has_available_connectors() модуля drivers/gpu/drm/meson/meson_drv.c драйвера инфраструктуры прямого рендеринга (DRI) ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-02802
Уязвимость функции afu_allocate_irqs() модуля drivers/misc/cxl/irq.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-02805
Уязвимость функции dm_pool_register_metadata_threshold() модуля drivers/md/dm-thin-metadata.c драйвера нескольких устройств (RAID и LVM) ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02806
Уязвимость функции dmar_parse_one_rhsa() модуля drivers/iommu/intel/dmar.c драйвера IOMMU ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02810
Уязвимость функции arkfb_set_par() модуля drivers/video/fbdev/arkfb.c драйвера устройств кадрового буфера ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02811
Уязвимость функции arkfb_set_par() модуля drivers/video/fbdev/arkfb.c драйвера устройств кадрового буфера ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-03106
Уязвимость функции vc_uniscr_alloc() модуля drivers/tty/vt/vt.c драйвера виртуального терминала консоли ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03124
Уязвимость функции msb_data_clear() модуля drivers/memstick/core/ms_block.c драйвера карт Sony MemoryStick ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03179
Уязвимость функции __driver_attach() модуля drivers/base/dd.c драйвера шинных устройства ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-03253
Уязвимость функций __msc_buffer_win_free() и msc_buffer_get_page() модуля drivers/hwtracing/intel_th/msu.c драйвера трассировки HW ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-03255
Уязвимость функции siw_proc_mpareply() модуля drivers/infiniband/sw/siw/siw_cm.c драйвера Infiniband ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-03262
Уязвимость функции jbd2_journal_dirty_metadata() модуля fs/jbd2/transaction.c файловой системы ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-03263
Уязвимость функций rxe_qp_init_misc() и rxe_qp_init_req() модуля drivers/infiniband/sw/rxe/rxe_qp.c драйвера InfiniBand ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-03374
Уязвимость функции soc_info() модуля drivers/tty/serial/ucc_uart.c драйвера консоли TTY на последовательном порте ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03396
Уязвимость функции xive_get_max_prio() модуля arch/powerpc/sysdev/xive/spapr.c поддержки платформы PowerPC ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03397
Уязвимость функций trace_spmi_write_begin() и trace_spmi_read_end() модуля include/trace/events/spmi.h ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03403
Уязвимость функции ohci_hcd_ppc_of_probe() модуля drivers/usb/host/ohci-ppc-of.c драйвера устройств шины USB ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03456
Уязвимость функции spufs_init_isolated_loader() модуля arch/powerpc/platforms/cell/spufs/inode.c поддержки платформы PowerPC ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03460
Уязвимость функции setup_msi_msg_address() модуля arch/powerpc/platforms/cell/axon_msi.c поддержки платформы PowerPC ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03468
Уязвимость функции max77620_initialise_fps() модуля drivers/mfd/max77620.c драйвера контроллера многофункциональных устройств (MFD) ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03470
Уязвимость функции clcdfb_of_init_display() модуля drivers/video/fbdev/amba-clcd.c драйвера устройств кадрового буфера ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03474
Уязвимость функции aa_pivotroot() модуля security/apparmor/mount.c компонента обеспечения безопасности AppArmor ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03476
Уязвимость функции qcom_smd_parse_edge() модуля drivers/rpmsg/qcom_smd.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03736
Уязвимость функции ath9k_htc_probe_device() модуля drivers/net/wireless/ath/ath9k/htc_drv_init.c драйвера адаптеров беспроводной связи Atheros/Qualcomm ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-03750
Уязвимость функции cp2112_xfer() модуля drivers/hid/hid-cp2112.c драйвера подсистемы устройств пользовательского интерфейса ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-04503
Уязвимость функции i740fb_decode_var() модуля drivers/video/fbdev/i740fb.c драйвера устройств кадрового буфера ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04505
Уязвимость функции octeon2_usb_clocks_start() модуля arch/mips/cavium-octeon/octeon-platform.c поддержки архитектуры MIPS ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04507
Уязвимость функции ep_io() модуля drivers/usb/gadget/legacy/inode.c драйвера гаджетов USB ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04508
Уязвимость функции clk_branch_wait() модуля drivers/clk/qcom/clk-branch.c драйвера контроллера тактовой частоты Samsung Exynos ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04509
Уязвимость функции usbhs_rza1_hardware_init() модуля drivers/usb/renesas_usbhs/rza.c драйвера устройств шины USB ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04511
Уязвимость функций snapshot_write() и snapshot_ioctl() модуля kernel/power/user.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04512
Уязвимость функции ext2_fill_super() модуля fs/ext2/super.c файловой системы ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04514
Уязвимость функции emulation_proc_handler() модуля arch/arm64/kernel/armv8_deprecated.c поддержки платформы ARM 64бит ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04515
Уязвимость функции c_start() модуля arch/mips/kernel/proc.c поддержки архитектуры MIPS ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04566
Уязвимость функции intel_th_pci_probe() модуля drivers/hwtracing/intel_th/pci.c драйвера трассировки HW ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04567
Уязвимость функции esdhc_signal_voltage_switch() модуля drivers/mmc/host/sdhci-of-esdhc.c драйвера карт MMC/SD/SDIO ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04571
Уязвимость функции setup_base_ctxt() модуля drivers/infiniband/hw/hfi1/file_ops.c драйвера InfiniBand ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04576
Уязвимость функции mt6797_mt6351_dev_probe() модуля sound/soc/mediatek/mt6797/mt6797-mt6351.c поддержки звука SoC ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04577
Уязвимость функции mt8173_rt5650_rt5676_dev_probe() модуля sound/soc/mediatek/mt8173/mt8173-rt5650-rt5676.c поддержки звука SoC ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04578
Уязвимость функции mt8173_rt5650_dev_probe() модуля sound/soc/mediatek/mt8173/mt8173-rt5650.c поддержки звука SoC ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04869
Уязвимость функции omapdss_init_fbdev() модуля arch/arm/mach-omap2/display.c поддержки платформы ARM ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04874
Уязвимость функции s3fb_set_par() модуля drivers/video/fbdev/s3fb.c драйвера устройств кадрового буфера ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-04875
Уязвимость функции bgmac_dma_tx_add() модуля drivers/net/ethernet/broadcom/bgmac.c драйвера сетевых адаптеров Ethernet Broadcom ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-05786
Уязвимость функции coresight_release_platform_data() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-05850
Уязвимость функции of_find_compatible_node() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-05851
Уязвимость функции isl29028_remove() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-06067
Уязвимость функции mcde_dsi_bind() в модуле drivers/gpu/drm/mcde/mcde_dsi.c драйвера инфраструктуры прямого рендеринга (DRI) ядра операционной системы Linux, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации
Modified: 2024-11-21
CVE-2019-25162
In the Linux kernel, the following vulnerability has been resolved: i2c: Fix a potential use after free Free the adap structure only after we are done using it. This patch just moves the put_device() down a bit to avoid the use after free. [wsa: added comment to the code, added Fixes tag]
- https://git.kernel.org/stable/c/12b0606000d0828630c033bf0c74c748464fe87d
- https://git.kernel.org/stable/c/23a191b132cd87f746c62f3dc27da33683d85829
- https://git.kernel.org/stable/c/35927d7509ab9bf41896b7e44f639504eae08af7
- https://git.kernel.org/stable/c/81cb31756888bb062e92d2dca21cd629d77a46a9
- https://git.kernel.org/stable/c/871a1e94929a27bf6e2cd99523865c840bbc2d87
- https://git.kernel.org/stable/c/e4c72c06c367758a14f227c847f9d623f1994ecf
- https://git.kernel.org/stable/c/e6412ba3b6508bdf9c074d310bf4144afa6aec1a
- https://git.kernel.org/stable/c/e8e1a046cf87c8b1363e5de835114f2779e2aaf4
- https://git.kernel.org/stable/c/12b0606000d0828630c033bf0c74c748464fe87d
- https://git.kernel.org/stable/c/23a191b132cd87f746c62f3dc27da33683d85829
- https://git.kernel.org/stable/c/35927d7509ab9bf41896b7e44f639504eae08af7
- https://git.kernel.org/stable/c/81cb31756888bb062e92d2dca21cd629d77a46a9
- https://git.kernel.org/stable/c/871a1e94929a27bf6e2cd99523865c840bbc2d87
- https://git.kernel.org/stable/c/e4c72c06c367758a14f227c847f9d623f1994ecf
- https://git.kernel.org/stable/c/e6412ba3b6508bdf9c074d310bf4144afa6aec1a
- https://git.kernel.org/stable/c/e8e1a046cf87c8b1363e5de835114f2779e2aaf4
Modified: 2024-11-21
CVE-2022-1679
A use-after-free flaw was found in the Linux kernel’s Atheros wireless adapter driver in the way a user forces the ath9k_htc_wait_for_target function to fail with some input messages. This flaw allows a local user to crash or potentially escalate their privileges on the system.
- https://lists.debian.org/debian-lts-announce/2022/10/msg00000.html
- https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html
- https://lore.kernel.org/lkml/87ilqc7jv9.fsf%40kernel.org/t/
- https://security.netapp.com/advisory/ntap-20220629-0007/
- https://lists.debian.org/debian-lts-announce/2022/10/msg00000.html
- https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html
- https://lore.kernel.org/lkml/87ilqc7jv9.fsf%40kernel.org/t/
- https://security.netapp.com/advisory/ntap-20220629-0007/
Modified: 2024-11-21
CVE-2022-2588
It was discovered that the cls_route filter implementation in the Linux kernel would not remove an old filter from the hashtable before freeing it if its handle had the value 0.
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2588
- https://github.com/Markakd/CVE-2022-2588
- https://lore.kernel.org/netdev/20220809170518.164662-1-cascardo@canonical.com/T/#u
- https://ubuntu.com/security/notices/USN-5557-1
- https://ubuntu.com/security/notices/USN-5560-1
- https://ubuntu.com/security/notices/USN-5560-2
- https://ubuntu.com/security/notices/USN-5562-1
- https://ubuntu.com/security/notices/USN-5564-1
- https://ubuntu.com/security/notices/USN-5565-1
- https://ubuntu.com/security/notices/USN-5566-1
- https://ubuntu.com/security/notices/USN-5567-1
- https://ubuntu.com/security/notices/USN-5582-1
- https://ubuntu.com/security/notices/USN-5588-1
- https://www.openwall.com/lists/oss-security/2022/08/09/6
- https://www.zerodayinitiative.com/advisories/ZDI-22-1117/
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2588
- https://github.com/Markakd/CVE-2022-2588
- https://lore.kernel.org/netdev/20220809170518.164662-1-cascardo@canonical.com/T/#u
- https://ubuntu.com/security/notices/USN-5557-1
- https://ubuntu.com/security/notices/USN-5560-1
- https://ubuntu.com/security/notices/USN-5560-2
- https://ubuntu.com/security/notices/USN-5562-1
- https://ubuntu.com/security/notices/USN-5564-1
- https://ubuntu.com/security/notices/USN-5565-1
- https://ubuntu.com/security/notices/USN-5566-1
- https://ubuntu.com/security/notices/USN-5567-1
- https://ubuntu.com/security/notices/USN-5582-1
- https://ubuntu.com/security/notices/USN-5588-1
- https://www.openwall.com/lists/oss-security/2022/08/09/6
- https://www.zerodayinitiative.com/advisories/ZDI-22-1117/
Modified: 2024-11-21
CVE-2022-3625
A vulnerability was found in Linux Kernel. It has been classified as critical. This affects the function devlink_param_set/devlink_param_get of the file net/core/devlink.c of the component IPsec. The manipulation leads to use after free. It is recommended to apply a patch to fix this issue. The identifier VDB-211929 was assigned to this vulnerability.
- https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git/commit/?id=6b4db2e528f650c7fb712961aac36455468d5902
- https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html
- https://vuldb.com/?id.211929
- https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git/commit/?id=6b4db2e528f650c7fb712961aac36455468d5902
- https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html
- https://vuldb.com/?id.211929
Modified: 2024-11-21
CVE-2022-3635
A vulnerability, which was classified as critical, has been found in Linux Kernel. Affected by this issue is the function tst_timer of the file drivers/atm/idt77252.c of the component IPsec. The manipulation leads to use after free. It is recommended to apply a patch to fix this issue. VDB-211934 is the identifier assigned to this vulnerability.
- https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git/commit/?id=3f4093e2bf4673f218c0bf17d8362337c400e77b
- https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html
- https://vuldb.com/?id.211934
- https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git/commit/?id=3f4093e2bf4673f218c0bf17d8362337c400e77b
- https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html
- https://vuldb.com/?id.211934
Modified: 2025-05-28
CVE-2022-41222
mm/mremap.c in the Linux kernel before 5.13.3 has a use-after-free via a stale TLB because an rmap lock is not held during a PUD move.
- http://packetstormsecurity.com/files/168466/Linux-Stable-5.4-5.10-Use-After-Free-Race-Condition.html
- http://packetstormsecurity.com/files/171005/Kernel-Live-Patch-Security-Notice-LNS-0091-1.html
- https://bugs.chromium.org/p/project-zero/issues/detail?id=2347
- https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.13.3
- https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=97113eb39fa7972722ff490b947d8af023e1f6a2
- https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html
- https://security.netapp.com/advisory/ntap-20230214-0008/
- http://packetstormsecurity.com/files/168466/Linux-Stable-5.4-5.10-Use-After-Free-Race-Condition.html
- http://packetstormsecurity.com/files/171005/Kernel-Live-Patch-Security-Notice-LNS-0091-1.html
- https://bugs.chromium.org/p/project-zero/issues/detail?id=2347
- https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.13.3
- https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=97113eb39fa7972722ff490b947d8af023e1f6a2
- https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html
- https://security.netapp.com/advisory/ntap-20230214-0008/
Modified: 2025-11-14
CVE-2022-50010
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 / I740_RFREQ_FIX))); The following log can reveal it: divide error: 0000 [#1] PREEMPT SMP KASAN PTI RIP: 0010:i740_calc_vclk drivers/video/fbdev/i740fb.c:353 [inline] RIP: 0010:i740fb_decode_var drivers/video/fbdev/i740fb.c:646 [inline] RIP: 0010:i740fb_set_par+0x163f/0x3b70 drivers/video/fbdev/i740fb.c:742 Call Trace: fb_set_var+0x604/0xeb0 drivers/video/fbdev/core/fbmem.c:1034 do_fb_ioctl+0x234/0x670 drivers/video/fbdev/core/fbmem.c:1110 fb_ioctl+0xdd/0x130 drivers/video/fbdev/core/fbmem.c:1189 Fix this by checking the argument of i740_calc_vclk() first.
- https://git.kernel.org/stable/c/2b7f559152a33c55f51b569b22efbe5e24886798
- https://git.kernel.org/stable/c/40bf722f8064f50200b8c4f8946cd625b441dda9
- https://git.kernel.org/stable/c/4b20c61365140d432dee7da7aa294215e7b900d9
- https://git.kernel.org/stable/c/59cefb583c984c0da8cf21a4c57d26d5a20dff5c
- https://git.kernel.org/stable/c/656689cb03ada4650016c153346939a1c334b1ae
- https://git.kernel.org/stable/c/d2d375eb68b4b8de6ea7460483a26fa9de56b443
- https://git.kernel.org/stable/c/e740e787f06671455b59d1e498c9945f7b4e7b3b
- https://git.kernel.org/stable/c/f350812e2d15278f1d867eeb997407782234fb3c
Modified: 2025-12-23
CVE-2022-50012
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 static_key_enable_cpuslocked+0xfc/0x120 ... NIP static_key_enable_cpuslocked+0xfc/0x120 LR static_key_enable_cpuslocked+0xf8/0x120 Call Trace: static_key_enable_cpuslocked+0xf8/0x120 (unreliable) static_key_enable+0x30/0x50 setup_forced_irqthreads+0x28/0x40 do_early_param+0xa0/0x108 parse_args+0x290/0x4e0 parse_early_options+0x48/0x5c parse_early_param+0x58/0x84 early_init_devtree+0xd4/0x518 early_setup+0xb4/0x214 So call jump_label_init() just before parse_early_param() in early_init_devtree(). [mpe: Add call trace to change log and minor wording edits.]
Modified: 2025-11-14
CVE-2022-50013
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
- https://git.kernel.org/stable/c/141170b759e03958f296033bb7001be62d1d363b
- https://git.kernel.org/stable/c/29e734ec33ae4bd7de4018fb0fb0eec808c36b92
- https://git.kernel.org/stable/c/43ce0a0bda2c54dad91d5a1943554eed9e050f55
- https://git.kernel.org/stable/c/5a01e45b925a0bc9718eccd33e5920f1a4e44caf
- https://git.kernel.org/stable/c/800ba8979111184d5194f4233cc83afe683efc54
- https://git.kernel.org/stable/c/fbfad62b29e9f8f1c1026a806c9e064ec2a7c342
Modified: 2025-11-13
CVE-2022-50017
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.
- https://git.kernel.org/stable/c/1b49707df679b5510ed06ace7378ddc2aec5c3fb
- https://git.kernel.org/stable/c/1e39037e44d7fa3728686af146f9285ea197097d
- https://git.kernel.org/stable/c/7822d994eb9579a1df4cdbc315db090a041e50f3
- https://git.kernel.org/stable/c/7a9f743ceead60ed454c46fbc3085ee9a79cbebb
- https://git.kernel.org/stable/c/9d1afa0169a84dcd5b79901d792edeb8403684ab
- https://git.kernel.org/stable/c/a80016c40cc797c7f3e5a705b8e12ae447280335
- https://git.kernel.org/stable/c/af87a469695dc2b2419b2fdff0bf41db5265b325
- https://git.kernel.org/stable/c/c06166a484eece51916dd700a870e53356b7e1bc
Modified: 2025-11-13
CVE-2022-50019
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.
- https://git.kernel.org/stable/c/17c32546166d8a7d2579c4b57c8b16241f94a66b
- https://git.kernel.org/stable/c/59bc4c19d53bdac61ec952c01c6e864f5f0f8367
- https://git.kernel.org/stable/c/81939c4fbc2d5c754d0f1c1f05149d4b70d751ed
- https://git.kernel.org/stable/c/8245e7d1d7f75a9255ad1e8146752e5051d528b8
- https://git.kernel.org/stable/c/ca3fc1c38e4253bc019881301a28ea60b8b0bca3
- https://git.kernel.org/stable/c/d24d7bb2cd947676f9b71fb944d045e09b8b282f
- https://git.kernel.org/stable/c/ec56f886f3bf0f15f7a3844d4c025e165b8e8de7
- https://git.kernel.org/stable/c/f6ed634eedb1a8a6a8cb110a7695c7abb70ffcbf
Modified: 2025-12-23
CVE-2022-50020
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.
- https://git.kernel.org/stable/c/0082e99a9074ff88eff729c70c93454c8588d8e1
- https://git.kernel.org/stable/c/69cb8e9d8cd97cdf5e293b26d70a9dee3e35e6bd
- https://git.kernel.org/stable/c/72b850a2a996f72541172e7cf686d54a2b29bcd8
- https://git.kernel.org/stable/c/7bdfb01fc5f6b3696728aeb527c50386e0ee09a1
- https://git.kernel.org/stable/c/80288883294c5b4ed18bae0d8bd9c4a12f297074
- https://git.kernel.org/stable/c/a6805b3dcf5cd41f2ae3a03dca43411135b99849
Modified: 2025-11-13
CVE-2022-50022
In the Linux kernel, the following vulnerability has been resolved: drivers:md:fix a potential use-after-free bug In line 2884, "raid5_release_stripe(sh);" drops the reference to sh and may cause sh to be released. However, sh is subsequently used in lines 2886 "if (sh->batch_head && sh != sh->batch_head)". This may result in an use-after-free bug. It can be fixed by moving "raid5_release_stripe(sh);" to the bottom of the function.
- https://git.kernel.org/stable/c/09cf99bace7789d91caa8d10fbcfc8b2fb35857f
- https://git.kernel.org/stable/c/104212471b1c1817b311771d817fb692af983173
- https://git.kernel.org/stable/c/5d8325fd15892c8ab1146edc1d7ed8463de39636
- https://git.kernel.org/stable/c/7470a4314b239e9a9580f248fdf4c9a92805490e
- https://git.kernel.org/stable/c/d9b94c3ace549433de8a93eeb27b0391fc8ac406
- https://git.kernel.org/stable/c/e5b3dd2d92c4511e81f6e4ec9c5bb7ad25e03d13
- https://git.kernel.org/stable/c/eb3a4f73f43f839df981dda5859e8e075067a360
- https://git.kernel.org/stable/c/f5d46f1b47f65da1faf468277b261eb78c8e25b5
Modified: 2025-11-13
CVE-2022-50025
In the Linux kernel, the following vulnerability has been resolved: cxl: Fix a memory leak in an error handling path A bitmap_zalloc() must be balanced by a corresponding bitmap_free() in the error handling path of afu_allocate_irqs().
- https://git.kernel.org/stable/c/3a15b45b5454da862376b5d69a4967f5c6fa1368
- https://git.kernel.org/stable/c/4be138bcd6d68cec0ce47051b117541061f5141a
- https://git.kernel.org/stable/c/6544ff559315498ad6c0a311359ca44987f9ca07
- https://git.kernel.org/stable/c/695af60af755873399ce01cb97176768828bc1fd
- https://git.kernel.org/stable/c/89d51dc6878c47b6400922fac21b6a33f9d1a588
- https://git.kernel.org/stable/c/addff638c41753639368c252d0c5ba0d8fe9ed97
- https://git.kernel.org/stable/c/c2557780ee7818b701681c226fa4cb7c0b171665
- https://git.kernel.org/stable/c/c2c7a29f99788e9e5dfe41d16868ea33da7cc235
Modified: 2025-11-13
CVE-2022-50028
In the Linux kernel, the following vulnerability has been resolved: gadgetfs: ep_io - wait until IRQ finishes after usb_ep_queue() if wait_for_completion_interruptible() is interrupted we need to wait until IRQ gets finished. Otherwise complete() from epio_complete() can corrupt stack.
- https://git.kernel.org/stable/c/04cb742d4d8f30dc2e83b46ac317eec09191c68e
- https://git.kernel.org/stable/c/118d967ce00a3d128bf731b35e4e2cb0facf5f00
- https://git.kernel.org/stable/c/2b06d5d97c0e067108a122986767731d40742138
- https://git.kernel.org/stable/c/67a4874461422e633236a0286a01b483cd647113
- https://git.kernel.org/stable/c/77040efe59a141286d090c8a0d37c65a355a1832
- https://git.kernel.org/stable/c/94aadba8d000d5de56af4ce8da3f334f21bf7a79
- https://git.kernel.org/stable/c/9ac14f973cb91f0c01776517e6d50981f32b8038
- https://git.kernel.org/stable/c/ca06b4cde54f8ec8be3aa53fd339bd56e62c12b3
Modified: 2025-11-13
CVE-2022-50029
In the Linux kernel, the following vulnerability has been resolved: clk: qcom: ipq8074: dont disable gcc_sleep_clk_src Once the usb sleep clocks are disabled, clock framework is trying to disable the sleep clock source also. However, it seems that it cannot be disabled and trying to do so produces: [ 245.436390] ------------[ cut here ]------------ [ 245.441233] gcc_sleep_clk_src status stuck at 'on' [ 245.441254] WARNING: CPU: 2 PID: 223 at clk_branch_wait+0x130/0x140 [ 245.450435] Modules linked in: xhci_plat_hcd xhci_hcd dwc3 dwc3_qcom leds_gpio [ 245.456601] CPU: 2 PID: 223 Comm: sh Not tainted 5.18.0-rc4 #215 [ 245.463889] Hardware name: Xiaomi AX9000 (DT) [ 245.470050] pstate: 204000c5 (nzCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 245.474307] pc : clk_branch_wait+0x130/0x140 [ 245.481073] lr : clk_branch_wait+0x130/0x140 [ 245.485588] sp : ffffffc009f2bad0 [ 245.489838] x29: ffffffc009f2bad0 x28: ffffff8003e6c800 x27: 0000000000000000 [ 245.493057] x26: 0000000000000000 x25: 0000000000000000 x24: ffffff800226ef20 [ 245.500175] x23: ffffffc0089ff550 x22: 0000000000000000 x21: ffffffc008476ad0 [ 245.507294] x20: 0000000000000000 x19: ffffffc00965ac70 x18: fffffffffffc51a7 [ 245.514413] x17: 68702e3030303837 x16: 3a6d726f6674616c x15: ffffffc089f2b777 [ 245.521531] x14: ffffffc0095c9d18 x13: 0000000000000129 x12: 0000000000000129 [ 245.528649] x11: 00000000ffffffea x10: ffffffc009621d18 x9 : 0000000000000001 [ 245.535767] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 : 0000000000000001 [ 245.542885] x5 : ffffff803fdca6d8 x4 : 0000000000000000 x3 : 0000000000000027 [ 245.550002] x2 : 0000000000000027 x1 : 0000000000000023 x0 : 0000000000000026 [ 245.557122] Call trace: [ 245.564229] clk_branch_wait+0x130/0x140 [ 245.566490] clk_branch2_disable+0x2c/0x40 [ 245.570656] clk_core_disable+0x60/0xb0 [ 245.574561] clk_core_disable+0x68/0xb0 [ 245.578293] clk_disable+0x30/0x50 [ 245.582113] dwc3_qcom_remove+0x60/0xc0 [dwc3_qcom] [ 245.585588] platform_remove+0x28/0x60 [ 245.590361] device_remove+0x4c/0x80 [ 245.594179] device_release_driver_internal+0x1dc/0x230 [ 245.597914] device_driver_detach+0x18/0x30 [ 245.602861] unbind_store+0xec/0x110 [ 245.607027] drv_attr_store+0x24/0x40 [ 245.610847] sysfs_kf_write+0x44/0x60 [ 245.614405] kernfs_fop_write_iter+0x128/0x1c0 [ 245.618052] new_sync_write+0xc0/0x130 [ 245.622391] vfs_write+0x1d4/0x2a0 [ 245.626123] ksys_write+0x58/0xe0 [ 245.629508] __arm64_sys_write+0x1c/0x30 [ 245.632895] invoke_syscall.constprop.0+0x5c/0x110 [ 245.636890] do_el0_svc+0xa0/0x150 [ 245.641488] el0_svc+0x18/0x60 [ 245.644872] el0t_64_sync_handler+0xa4/0x130 [ 245.647914] el0t_64_sync+0x174/0x178 [ 245.652340] ---[ end trace 0000000000000000 ]--- So, add CLK_IS_CRITICAL flag to the clock so that the kernel won't try to disable the sleep clock.
- https://git.kernel.org/stable/c/17d58499dc9c7e059dab7d170e9bae1e7e9c561b
- https://git.kernel.org/stable/c/1bf7305e79aab095196131bdc87a97796e0e3fac
- https://git.kernel.org/stable/c/38cee0d2b65eed42a44052de1bfdc0177b6c3f05
- https://git.kernel.org/stable/c/4203b76abe539f3cac258d4cf1e16e2dd95ea60f
- https://git.kernel.org/stable/c/459411b9f0180e3f382d7abfa3028dd3285984c3
- https://git.kernel.org/stable/c/6b90ab952401bd6c1a321dcfc0e0df080f2bc905
- https://git.kernel.org/stable/c/d401611a93b332914cf91eb9bc0b63fa1bdc17e9
Modified: 2025-11-13
CVE-2022-50030
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input Malformed user input to debugfs results in buffer overflow crashes. Adapt input string lengths to fit within internal buffers, leaving space for NULL terminators.
- https://git.kernel.org/stable/c/2d544e9d19c109dfe34b3dc1253a8b2971abe060
- https://git.kernel.org/stable/c/927907f1cbb3408cadde637fccfc17bb6b10a87d
- https://git.kernel.org/stable/c/b92506dc51f81741eb26609175ac206c20f06e0a
- https://git.kernel.org/stable/c/c29a4baaad38a332c0ae480cf6d6c5bf75ac1828
- https://git.kernel.org/stable/c/f8191d40aa612981ce897e66cda6a88db8df17bb
Modified: 2025-11-13
CVE-2022-50032
In the Linux kernel, the following vulnerability has been resolved: usb: renesas: Fix refcount leak bug In usbhs_rza1_hardware_init(), 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.
- https://git.kernel.org/stable/c/36b18b777dece704b7c2e9e7947ca41a9b0fb009
- https://git.kernel.org/stable/c/5c4b699193eba51f1bbf462d758d66f545fddd35
- https://git.kernel.org/stable/c/9790a5a4f07f38a5add85ec58c44797d3a7c3677
- https://git.kernel.org/stable/c/9d6d5303c39b8bc182475b22f45504106a07f086
- https://git.kernel.org/stable/c/cfa8f707a58d68b2341a9dd0b33cf048f0628b4d
- https://git.kernel.org/stable/c/fbdbd61a36d887e00114321c6758e359e9573a8e
Modified: 2025-11-13
CVE-2022-50033
In the Linux kernel, the following vulnerability has been resolved: usb: host: ohci-ppc-of: Fix refcount leak bug In ohci_hcd_ppc_of_probe(), of_find_compatible_node() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.
- https://git.kernel.org/stable/c/0334d23c56ecf1ee1563bb83e29cc5a51ed7fb4e
- https://git.kernel.org/stable/c/0fc62bbc95319bbd330e3645afc7c286acec9ef8
- https://git.kernel.org/stable/c/403132881e66db7aa98b55c6655daedd80d407fd
- https://git.kernel.org/stable/c/40a959d7042bb7711e404ad2318b30e9f92c6b9b
- https://git.kernel.org/stable/c/c5c5bd5cdcc6dc9f75f53d1c89af463d39a2bb96
- https://git.kernel.org/stable/c/cb5dd65e889163e723df1c2f02288cc527a57785
- https://git.kernel.org/stable/c/ec583e300aee9f152a64911445092d18e1c36729
- https://git.kernel.org/stable/c/fe6fe64403710287f0ae61a516954d8a4f7c9e3f
Modified: 2025-11-13
CVE-2022-50034
In the Linux kernel, the following vulnerability has been resolved: usb: cdns3 fix use-after-free at workaround 2 BUG: KFENCE: use-after-free read in __list_del_entry_valid+0x10/0xac cdns3_wa2_remove_old_request() { ... kfree(priv_req->request.buf); cdns3_gadget_ep_free_request(&priv_ep->endpoint, &priv_req->request); list_del_init(&priv_req->list); ^^^ use after free ... } cdns3_gadget_ep_free_request() free the space pointed by priv_req, but priv_req is used in the following list_del_init(). This patch move list_del_init() before cdns3_gadget_ep_free_request().
- https://git.kernel.org/stable/c/6d7ac60098b206d0472475b666cb09d556bec03d
- https://git.kernel.org/stable/c/6fd50446e7c9a98b4bcf96815f5c9602a16ea472
- https://git.kernel.org/stable/c/7d602f30149a117eea260208b1661bc404c21dfd
- https://git.kernel.org/stable/c/c3c1dbad3a2db32ecf371c97f2058491b8ba0f9a
- https://git.kernel.org/stable/c/e65d9b7147d7be3504893ca7dfb85286bda83d40
Modified: 2025-11-13
CVE-2022-50038
In the Linux kernel, the following vulnerability has been resolved: drm/meson: Fix refcount bugs in meson_vpu_has_available_connectors() In this function, there are two refcount leak bugs: (1) when breaking out of for_each_endpoint_of_node(), we need call the of_node_put() for the 'ep'; (2) we should call of_node_put() for the reference returned by of_graph_get_remote_port() when it is not used anymore.
- https://git.kernel.org/stable/c/3aa710e96747c8b4e52ba12ffe09edcb2755897c
- https://git.kernel.org/stable/c/6a758f0ba11699837af9e1a0f7cbac6ef765a23e
- https://git.kernel.org/stable/c/8dec38e19f6928235d4009ce55f7add8af34e5c7
- https://git.kernel.org/stable/c/91b3c8dbe898df158fd2a84675f3a284ff6666f7
- https://git.kernel.org/stable/c/d58ef256781398ad115aef44de0a02ad27ea6c3a
- https://git.kernel.org/stable/c/fc1fc2abfcb9235d0ece9a4d858426fb617cfa66
- https://git.kernel.org/stable/c/fe71d84c1a6c0d54657431e8eeaefc9d24895304
Modified: 2025-11-13
CVE-2022-50047
In the Linux kernel, the following vulnerability has been resolved: net: dsa: mv88e6060: prevent crash on an unused port If the port isn't a CPU port nor a user port, 'cpu_dp' is a null pointer and a crash happened on dereferencing it in mv88e6060_setup_port(): [ 9.575872] Unable to handle kernel NULL pointer dereference at virtual address 00000014 ... [ 9.942216] mv88e6060_setup from dsa_register_switch+0x814/0xe84 [ 9.948616] dsa_register_switch from mdio_probe+0x2c/0x54 [ 9.954433] mdio_probe from really_probe.part.0+0x98/0x2a0 [ 9.960375] really_probe.part.0 from driver_probe_device+0x30/0x10c [ 9.967029] driver_probe_device from __device_attach_driver+0xb8/0x13c [ 9.973946] __device_attach_driver from bus_for_each_drv+0x90/0xe0 [ 9.980509] bus_for_each_drv from __device_attach+0x110/0x184 [ 9.986632] __device_attach from bus_probe_device+0x8c/0x94 [ 9.992577] bus_probe_device from deferred_probe_work_func+0x78/0xa8 [ 9.999311] deferred_probe_work_func from process_one_work+0x290/0x73c [ 10.006292] process_one_work from worker_thread+0x30/0x4b8 [ 10.012155] worker_thread from kthread+0xd4/0x10c [ 10.017238] kthread from ret_from_fork+0x14/0x3c
- https://git.kernel.org/stable/c/246bbf2f977ea36aaf41f5d24370fef433250728
- https://git.kernel.org/stable/c/92dc64e8f591425ce4dabf7d479ebf6e67fb8853
- https://git.kernel.org/stable/c/cb1753bc689c7a7f94da6eee7efc1ae6d8abb36c
- https://git.kernel.org/stable/c/dd236b62d25e44ecfa26b0910a12f8d8251aff00
- https://git.kernel.org/stable/c/f3a4b55829617cad2d36fa6524367ef629566ba6
Modified: 2025-11-13
CVE-2022-50055
In the Linux kernel, the following vulnerability has been resolved: iavf: Fix adminq error handling iavf_alloc_asq_bufs/iavf_alloc_arq_bufs allocates with dma_alloc_coherent memory for VF mailbox. Free DMA regions for both ASQ and ARQ in case error happens during configuration of ASQ/ARQ registers. Without this change it is possible to see when unloading interface: 74626.583369: dma_debug_device_change: device driver has pending DMA allocations while released from device [count=32] One of leaked entries details: [device address=0x0000000b27ff9000] [size=4096 bytes] [mapped with DMA_BIDIRECTIONAL] [mapped as coherent]
- https://git.kernel.org/stable/c/35c63581fdefdcbaeae8cded18908523252353ad
- https://git.kernel.org/stable/c/419831617ed349992c84344dbd9e627f9e68f842
- https://git.kernel.org/stable/c/4fe80492d53971d9a49f39f3c86d2d67c6f3638a
- https://git.kernel.org/stable/c/dab6b551f5ba4c79a0dd4970dd8533c37a7b100f
- https://git.kernel.org/stable/c/ff289f2be5899efd0e897d2b434a78e36df2c69b
Modified: 2025-11-13
CVE-2022-50061
In the Linux kernel, the following vulnerability has been resolved: pinctrl: nomadik: Fix refcount leak in nmk_pinctrl_dt_subnode_to_map 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."
- https://git.kernel.org/stable/c/4b32e054335ea0ce50967f63a7bfd4db058b14b9
- https://git.kernel.org/stable/c/587ac8ac00a1a9f4572785229d9441870fd7b187
- https://git.kernel.org/stable/c/78d05103891d3e96144b846fbc39f2cfb3384eae
- https://git.kernel.org/stable/c/81abaab5a4b815c0ed9f4d2c9745777ac5cc395b
- https://git.kernel.org/stable/c/9272265f2f76629e1a67e6d49b3a4461b3da1a73
- https://git.kernel.org/stable/c/c26012a1e61c7bbd1b393d3bbae8dffdb6df65bb
- https://git.kernel.org/stable/c/c35f89a9021fa947ecede0584ae509368a52ec5a
- https://git.kernel.org/stable/c/f498542bc703bf1e5c6a1610e1ea493a437f0196
Modified: 2025-11-13
CVE-2022-50062
In the Linux kernel, the following vulnerability has been resolved:
net: bgmac: Fix a BUG triggered by wrong bytes_compl
On one of our machines we got:
kernel BUG at lib/dynamic_queue_limits.c:27!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
CPU: 0 PID: 1166 Comm: irq/41-bgmac Tainted: G W O 4.14.275-rt132 #1
Hardware name: BRCM XGS iProc
task: ee3415c0 task.stack: ee32a000
PC is at dql_completed+0x168/0x178
LR is at bgmac_poll+0x18c/0x6d8
pc : [
- https://git.kernel.org/stable/c/1b7680c6c1f6de9904f1d9b05c952f0c64a03350
- https://git.kernel.org/stable/c/ab2b55bb25db289ba0b68e3d58494476bdb1041d
- https://git.kernel.org/stable/c/ac6d4482f29ab992b605c1b4bd1347f1f679f4e4
- https://git.kernel.org/stable/c/c506c9a97120f43257e9b3ce7b1f9a24eafc3787
- https://git.kernel.org/stable/c/da1421a29d3b8681ba6a7f686bd0b40dda5acaf3
Modified: 2025-11-17
CVE-2022-50072
In the Linux kernel, the following vulnerability has been resolved: NFSv4/pnfs: Fix a use-after-free bug in open If someone cancels the open RPC call, then we must not try to free either the open slot or the layoutget operation arguments, since they are likely still in use by the hung RPC call.
- https://git.kernel.org/stable/c/0fffb46ff3d5ed4668aca96441ec7a25b793bd6f
- https://git.kernel.org/stable/c/2135e5d56278ffdb1c2e6d325dc6b87f669b9dac
- https://git.kernel.org/stable/c/76ffd2042438769298f34b76102b40dea89de616
- https://git.kernel.org/stable/c/a4cf3dadd1fa43609f7c6570c9116b0e0a9923d1
- https://git.kernel.org/stable/c/b03d1117e9be7c7da60e466eaf9beed85c5916c8
- https://git.kernel.org/stable/c/f7ee3b772d9de87387a725caa04bc041ac7fe5ec
Modified: 2025-11-17
CVE-2022-50074
In the Linux kernel, the following vulnerability has been resolved: apparmor: Fix memleak in aa_simple_write_to_buffer() When copy_from_user failed, the memory is freed by kvfree. however the management struct and data blob are allocated independently, so only kvfree(data) cause a memleak issue here. Use aa_put_loaddata(data) to fix this issue.
- https://git.kernel.org/stable/c/417ea9fe972d2654a268ad66e89c8fcae67017c3
- https://git.kernel.org/stable/c/6500eb3a48ac221051b1791818a1ac74744ef617
- https://git.kernel.org/stable/c/6583edbf459de2e06b9759f264c0ae27e452b97a
- https://git.kernel.org/stable/c/7db182a2ebeefded86fea542fcc5d6a68bb77f58
- https://git.kernel.org/stable/c/8aab4295582eb397a125d2788b829fa62b88dbf7
- https://git.kernel.org/stable/c/bf7ebebce2c25071c719fd8a2f1307e0c243c2d7
Modified: 2025-11-17
CVE-2022-50077
In the Linux kernel, the following vulnerability has been resolved: apparmor: fix reference count leak in aa_pivotroot() The aa_pivotroot() function has a reference counting bug in a specific path. When aa_replace_current_label() returns on success, the function forgets to decrement the reference count of “target”, which is increased earlier by build_pivotroot(), causing a reference leak. Fix it by decreasing the refcount of “target” in that path.
- https://git.kernel.org/stable/c/11c3627ec6b56c1525013f336f41b79a983b4d46
- https://git.kernel.org/stable/c/2ceeb3296e9dde1d5772348046affcefdea605e2
- https://git.kernel.org/stable/c/3ca40ad7afae144169a43988ef1a3f16182faf0a
- https://git.kernel.org/stable/c/64103ea357734b82384c925cba4758fdb909be0c
- https://git.kernel.org/stable/c/d53194707d2a1851be027cd74266b96ceff799d3
- https://git.kernel.org/stable/c/ef6fb6f0d0d8440595b45a7e53c6162c737177f4
- https://git.kernel.org/stable/c/f4d5c7796571624e3f380b447ada52834270a287
Modified: 2025-11-18
CVE-2022-50080
In the Linux kernel, the following vulnerability has been resolved: tee: add overflow check in register_shm_helper() With special lengths supplied by user space, register_shm_helper() has an integer overflow when calculating the number of pages covered by a supplied user space memory region. This causes internal_get_user_pages_fast() a helper function of pin_user_pages_fast() to do a NULL pointer dereference: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010 Modules linked in: CPU: 1 PID: 173 Comm: optee_example_a Not tainted 5.19.0 #11 Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 pc : internal_get_user_pages_fast+0x474/0xa80 Call trace: internal_get_user_pages_fast+0x474/0xa80 pin_user_pages_fast+0x24/0x4c register_shm_helper+0x194/0x330 tee_shm_register_user_buf+0x78/0x120 tee_ioctl+0xd0/0x11a0 __arm64_sys_ioctl+0xa8/0xec invoke_syscall+0x48/0x114 Fix this by adding an an explicit call to access_ok() in tee_shm_register_user_buf() to catch an invalid user space address early.
- https://git.kernel.org/stable/c/2f8e79a1a6128214cb9b205a9869341af5dfb16b
- https://git.kernel.org/stable/c/573ae4f13f630d6660008f1974c0a8a29c30e18a
- https://git.kernel.org/stable/c/578c349570d2a912401963783b36e0ec7a25c053
- https://git.kernel.org/stable/c/58c008d4d398f792ca67f35650610864725518fd
- https://git.kernel.org/stable/c/965333345fe952cc7eebc8e3a565ffc709441af2
- https://git.kernel.org/stable/c/b37e0f17653c00b586cdbcdf0dbca475358ecffd
- https://git.kernel.org/stable/c/c12f0e6126ad223806a365084e86370511654bf1
Modified: 2025-11-18
CVE-2022-50084
In the Linux kernel, the following vulnerability has been resolved:
dm raid: fix address sanitizer warning in raid_status
There is this warning when using a kernel with the address sanitizer
and running this testsuite:
https://gitlab.com/cki-project/kernel-tests/-/tree/main/storage/swraid/scsi_raid
==================================================================
BUG: KASAN: slab-out-of-bounds in raid_status+0x1747/0x2820 [dm_raid]
Read of size 4 at addr ffff888079d2c7e8 by task lvcreate/13319
CPU: 0 PID: 13319 Comm: lvcreate Not tainted 5.18.0-0.rc3.
- https://git.kernel.org/stable/c/1ae0ebfb576b72c2ef400917a5484ebe7892d80b
- https://git.kernel.org/stable/c/1fbeea217d8f297fe0e0956a1516d14ba97d0396
- https://git.kernel.org/stable/c/49dba30638e091120256a9e89125340795f034dc
- https://git.kernel.org/stable/c/4c233811a49578634d10a5e70a9dfa569d451e94
- https://git.kernel.org/stable/c/90b006da40dd42285b24dd3c940d2c32aca9a70b
- https://git.kernel.org/stable/c/b4c6c07c92b6cba2bf3cb2dfa722debeaf8a8abe
- https://git.kernel.org/stable/c/b856ce5f4b55f752144baf17e9d5c415072652c5
- https://git.kernel.org/stable/c/cb583ca6125ac64c98e9d65128e95ebb5be7d322
- https://git.kernel.org/stable/c/d8971b595d7adac3421c21f59918241f1574061e
Modified: 2025-11-18
CVE-2022-50085
In the Linux kernel, the following vulnerability has been resolved: dm raid: fix address sanitizer warning in raid_resume There is a KASAN warning in raid_resume when running the lvm test lvconvert-raid.sh. The reason for the warning is that mddev->raid_disks is greater than rs->raid_disks, so the loop touches one entry beyond the allocated length.
- https://git.kernel.org/stable/c/2a9faa704d83ff0b04387e385efd8ae21cd95af6
- https://git.kernel.org/stable/c/3bfdc95466f5be4d8d95db5a5b470d61641a7c24
- https://git.kernel.org/stable/c/50235d9a1f1f742619ed9963cb9f240e5b821d46
- https://git.kernel.org/stable/c/71f601c779b3cc1baf497796f5b922c3fe5d2a1e
- https://git.kernel.org/stable/c/74af83732a39ab7d3bc9b49219a535853e25679f
- https://git.kernel.org/stable/c/7dad24db59d2d2803576f2e3645728866a056dab
- https://git.kernel.org/stable/c/c2d47bef93fb74aa97d90f9a40ca657b8f376083
- https://git.kernel.org/stable/c/c2f075e729636a44e98d9722e3852c2fa6fa49b6
Modified: 2025-11-18
CVE-2022-50087
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.
- https://git.kernel.org/stable/c/08272646cd7c310642c39b7f54348fddd7987643
- https://git.kernel.org/stable/c/0c29e149b6bb498778ed8a1c9597b51acfba7856
- https://git.kernel.org/stable/c/18048cba444a7c41dbf42c180d6b46606fc24c51
- https://git.kernel.org/stable/c/4f2d7b46d6b53c07f44a4f8f8f4438888f0e9e87
- https://git.kernel.org/stable/c/5aa558232edc30468d1f35108826dd5b3ffe978f
- https://git.kernel.org/stable/c/689640efc0a2c4e07e6f88affe6d42cd40cc3f85
- https://git.kernel.org/stable/c/87c4896d5dd7fd9927c814cf3c6289f41de3b562
Modified: 2025-11-18
CVE-2022-50092
In the Linux kernel, the following vulnerability has been resolved:
dm thin: fix use-after-free crash in dm_sm_register_threshold_callback
Fault inject on pool metadata device reports:
BUG: KASAN: use-after-free in dm_pool_register_metadata_threshold+0x40/0x80
Read of size 8 at addr ffff8881b9d50068 by task dmsetup/950
CPU: 7 PID: 950 Comm: dmsetup Tainted: G W 5.19.0-rc6 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014
Call Trace:
- https://git.kernel.org/stable/c/05cef0999b3208b5a6ede1bfac855139e4de55ef
- https://git.kernel.org/stable/c/1a199fa9217d28511ff88529238fd9980ea64cf3
- https://git.kernel.org/stable/c/3534e5a5ed2997ca1b00f44a0378a075bd05e8a3
- https://git.kernel.org/stable/c/5e2cf705155a1514be3c96ea664a9cd356998ee7
- https://git.kernel.org/stable/c/e4dbe24f4bfd8377e7ba79fdcdb7c4d6eb1c6790
- https://git.kernel.org/stable/c/f83131a3071a0b61a4d7dca70f95adb3ffad920e
Modified: 2025-11-18
CVE-2022-50093
In the Linux kernel, the following vulnerability has been resolved:
iommu/vt-d: avoid invalid memory access via node_online(NUMA_NO_NODE)
KASAN reports:
[ 4.668325][ T0] BUG: KASAN: wild-memory-access in dmar_parse_one_rhsa (arch/x86/include/asm/bitops.h:214 arch/x86/include/asm/bitops.h:226 include/asm-generic/bitops/instrumented-non-atomic.h:142 include/linux/nodemask.h:415 drivers/iommu/intel/dmar.c:497)
[ 4.676149][ T0] Read of size 8 at addr 1fffffff85115558 by task swapper/0/0
[ 4.683454][ T0]
[ 4.685638][ T0] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.19.0-rc3-00004-g0e862838f290 #1
[ 4.694331][ T0] Hardware name: Supermicro SYS-5018D-FN4T/X10SDV-8C-TLN4F, BIOS 1.1 03/02/2016
[ 4.703196][ T0] Call Trace:
[ 4.706334][ T0]
- https://git.kernel.org/stable/c/0b4c0003aeda32a600f95df53b2848da8a5aa3fa
- https://git.kernel.org/stable/c/5659efdadf04b56707d58c1b758df16d2e0eff2c
- https://git.kernel.org/stable/c/73ce2046e04ad488cecc66757c36cbe1bdf089d4
- https://git.kernel.org/stable/c/b0b0b77ea611e3088e9523e60860f4f41b62b235
- https://git.kernel.org/stable/c/b12304984654d8e58a2b22ff94c4410906d6267f
- https://git.kernel.org/stable/c/c2304c50f4d94f56c2e326f25c9dc8cf2ba6f5fa
Modified: 2025-11-18
CVE-2022-50094
In the Linux kernel, the following vulnerability has been resolved: spmi: trace: fix stack-out-of-bound access in SPMI tracing functions trace_spmi_write_begin() and trace_spmi_read_end() both call memcpy() with a length of "len + 1". This leads to one extra byte being read beyond the end of the specified buffer. Fix this out-of-bound memory access by using a length of "len" instead. Here is a KASAN log showing the issue: BUG: KASAN: stack-out-of-bounds in trace_event_raw_event_spmi_read_end+0x1d0/0x234 Read of size 2 at addr ffffffc0265b7540 by task thermal@2.0-ser/1314 ... Call trace: dump_backtrace+0x0/0x3e8 show_stack+0x2c/0x3c dump_stack_lvl+0xdc/0x11c print_address_description+0x74/0x384 kasan_report+0x188/0x268 kasan_check_range+0x270/0x2b0 memcpy+0x90/0xe8 trace_event_raw_event_spmi_read_end+0x1d0/0x234 spmi_read_cmd+0x294/0x3ac spmi_ext_register_readl+0x84/0x9c regmap_spmi_ext_read+0x144/0x1b0 [regmap_spmi] _regmap_raw_read+0x40c/0x754 regmap_raw_read+0x3a0/0x514 regmap_bulk_read+0x418/0x494 adc5_gen3_poll_wait_hs+0xe8/0x1e0 [qcom_spmi_adc5_gen3] ... __arm64_sys_read+0x4c/0x60 invoke_syscall+0x80/0x218 el0_svc_common+0xec/0x1c8 ... addr ffffffc0265b7540 is located in stack of task thermal@2.0-ser/1314 at offset 32 in frame: adc5_gen3_poll_wait_hs+0x0/0x1e0 [qcom_spmi_adc5_gen3] this frame has 1 object: [32, 33) 'status' Memory state around the buggy address: ffffffc0265b7400: 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 ffffffc0265b7480: 04 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 >ffffffc0265b7500: 00 00 00 00 f1 f1 f1 f1 01 f3 f3 f3 00 00 00 00 ^ ffffffc0265b7580: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffffc0265b7600: f1 f1 f1 f1 01 f2 07 f2 f2 f2 01 f3 00 00 00 00 ==================================================================
- https://git.kernel.org/stable/c/1e0ca3d809c36ad3d1f542917718fc22ec6316e7
- https://git.kernel.org/stable/c/2af28b241eea816e6f7668d1954f15894b45d7e3
- https://git.kernel.org/stable/c/37690cb8662cec672cacda19e6e4fd2ca7b13f0b
- https://git.kernel.org/stable/c/504090815c1ad3fd3fa34618b54d706727f8911c
- https://git.kernel.org/stable/c/80f7c93e573ea9f524924bb529c2af8cb28b1c43
- https://git.kernel.org/stable/c/ac730c72bddc889f5610d51d8a7abf425e08da1a
- https://git.kernel.org/stable/c/bcc1b6b1ed3f42ed25858c1f1eb24a2f741db93f
- https://git.kernel.org/stable/c/dc6033a7761254e5a5ba7df36b64db787a53313c
- https://git.kernel.org/stable/c/dd02510fb43168310abfd0b9ccf49993a722fb91
Modified: 2025-11-19
CVE-2022-50097
In the Linux kernel, the following vulnerability has been resolved: video: fbdev: s3fb: Check the size of screen before memset_io() In the function s3fb_set_par(), the value of 'screen_size' is calculated by the user input. If the user provides the improper value, the value of 'screen_size' may larger than 'info->screen_size', which may cause the following bug: [ 54.083733] BUG: unable to handle page fault for address: ffffc90003000000 [ 54.083742] #PF: supervisor write access in kernel mode [ 54.083744] #PF: error_code(0x0002) - not-present page [ 54.083760] RIP: 0010:memset_orig+0x33/0xb0 [ 54.083782] Call Trace: [ 54.083788] s3fb_set_par+0x1ec6/0x4040 [ 54.083806] fb_set_var+0x604/0xeb0 [ 54.083836] do_fb_ioctl+0x234/0x670 Fix the this by checking the value of 'screen_size' before memset_io().
- https://git.kernel.org/stable/c/3c35a0dc2b4e7acf24c796043b64fa3eee799239
- https://git.kernel.org/stable/c/52461d387cc8c8f8dc40320caa2e9e101f73e7ba
- https://git.kernel.org/stable/c/574912261528589012b61f82d368256247c3a5a8
- https://git.kernel.org/stable/c/5e0da18956d38e7106664dc1d06367b22f06edd3
- https://git.kernel.org/stable/c/6ba592fa014f21f35a8ee8da4ca7b95a018f13e8
- https://git.kernel.org/stable/c/ce50d94afcb8690813c5522f24cd38737657db81
- https://git.kernel.org/stable/c/e2d7cacc6a2a1d77e7e20a492daf458a12cf19e0
- https://git.kernel.org/stable/c/eacb50f1733660911827d7c3720f4c5425d0cdda
Modified: 2025-11-19
CVE-2022-50099
In the Linux kernel, the following vulnerability has been resolved: video: fbdev: arkfb: Check the size of screen before memset_io() In the function arkfb_set_par(), the value of 'screen_size' is calculated by the user input. If the user provides the improper value, the value of 'screen_size' may larger than 'info->screen_size', which may cause the following bug: [ 659.399066] BUG: unable to handle page fault for address: ffffc90003000000 [ 659.399077] #PF: supervisor write access in kernel mode [ 659.399079] #PF: error_code(0x0002) - not-present page [ 659.399094] RIP: 0010:memset_orig+0x33/0xb0 [ 659.399116] Call Trace: [ 659.399122] arkfb_set_par+0x143f/0x24c0 [ 659.399130] fb_set_var+0x604/0xeb0 [ 659.399161] do_fb_ioctl+0x234/0x670 [ 659.399189] fb_ioctl+0xdd/0x130 Fix the this by checking the value of 'screen_size' before memset_io().
- https://git.kernel.org/stable/c/0701df594bc1d7ae55fed407fb65dd90a93f8a9c
- https://git.kernel.org/stable/c/09e733d6ac948e6fda4b16252e44ea46f98fc8b4
- https://git.kernel.org/stable/c/2ce61c39c2a0b8ec82f48e0f7136f0dac105ae75
- https://git.kernel.org/stable/c/352305ea50d682b8e081d826da53caf9e744d7d0
- https://git.kernel.org/stable/c/4a20c5510aa2c031a096a58deb356e91609781c9
- https://git.kernel.org/stable/c/53198b81930e567ad6b879812d88052a1e8ac79e
- https://git.kernel.org/stable/c/8bcb1a06e3091716b7cbebe0e91d1de9895068cd
- https://git.kernel.org/stable/c/96b550971c65d54d64728d8ba973487878a06454
Modified: 2025-11-19
CVE-2022-50101
In the Linux kernel, the following vulnerability has been resolved: video: fbdev: vt8623fb: Check the size of screen before memset_io() In the function vt8623fb_set_par(), the value of 'screen_size' is calculated by the user input. If the user provides the improper value, the value of 'screen_size' may larger than 'info->screen_size', which may cause the following bug: [ 583.339036] BUG: unable to handle page fault for address: ffffc90005000000 [ 583.339049] #PF: supervisor write access in kernel mode [ 583.339052] #PF: error_code(0x0002) - not-present page [ 583.339074] RIP: 0010:memset_orig+0x33/0xb0 [ 583.339110] Call Trace: [ 583.339118] vt8623fb_set_par+0x11cd/0x21e0 [ 583.339146] fb_set_var+0x604/0xeb0 [ 583.339181] do_fb_ioctl+0x234/0x670 [ 583.339209] fb_ioctl+0xdd/0x130 Fix the this by checking the value of 'screen_size' before memset_io().
- https://git.kernel.org/stable/c/4a3cef1eaced13ba9b55381d46bfad937a3dac2c
- https://git.kernel.org/stable/c/52ad9bfeb8a0e62de30de6d39e8a49a72dd78150
- https://git.kernel.org/stable/c/73280a184aa2e1a625ce54ce761042955cc79cd0
- https://git.kernel.org/stable/c/b17caec5127bba6f90af92bcc85871df54548ac0
- https://git.kernel.org/stable/c/bd8269e57621e5b38cc0b4bd2fa02e85c9f2a441
- https://git.kernel.org/stable/c/c7a3f41e4b133d4dd25bc996b69039b19a34d69d
- https://git.kernel.org/stable/c/d71528ccdc7ae8d7500d414091d27805c51407a2
- https://git.kernel.org/stable/c/ec0754c60217248fa77cc9005d66b2b55200ac06
Modified: 2025-11-19
CVE-2022-50102
In the Linux kernel, the following vulnerability has been resolved: video: fbdev: arkfb: Fix a divide-by-zero bug in ark_set_pixclock() 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 in: drivers/video/fbdev/arkfb.c:784: ark_set_pixclock(info, (hdiv * info->var.pixclock) / hmul); with hdiv=1, pixclock=1 and hmul=2 you end up with (1*1)/2 = (int) 0. and then in: drivers/video/fbdev/arkfb.c:504: rv = dac_set_freq(par->dac, 0, 1000000000 / pixclock); we'll get a division-by-zero. The following log can reveal it: divide error: 0000 [#1] PREEMPT SMP KASAN PTI RIP: 0010:ark_set_pixclock drivers/video/fbdev/arkfb.c:504 [inline] RIP: 0010:arkfb_set_par+0x10fc/0x24c0 drivers/video/fbdev/arkfb.c:784 Call Trace: fb_set_var+0x604/0xeb0 drivers/video/fbdev/core/fbmem.c:1034 do_fb_ioctl+0x234/0x670 drivers/video/fbdev/core/fbmem.c:1110 fb_ioctl+0xdd/0x130 drivers/video/fbdev/core/fbmem.c:1189 Fix this by checking the argument of ark_set_pixclock() first.
- https://git.kernel.org/stable/c/0288fa799e273b08839037499d704dc7bdc13e9a
- https://git.kernel.org/stable/c/15661642511b2b192077684a89f42a8d95d54286
- https://git.kernel.org/stable/c/236c1502520b7b08955467ec2e50b3232e34f1f9
- https://git.kernel.org/stable/c/2f1c4523f7a3aaabe7e53d3ebd378292947e95c8
- https://git.kernel.org/stable/c/76b3f0a0b56e53a960a14624a0f48b3d94b5e7e7
- https://git.kernel.org/stable/c/9ebc5031958c1f3a2795e4533b4091d77c738d14
- https://git.kernel.org/stable/c/a249e1b89ca25e1c34bdf96154e3f6224a91a9af
- https://git.kernel.org/stable/c/b9a66f23612b84617e04412169e155a4b92f632d
Modified: 2025-11-19
CVE-2022-50104
In the Linux kernel, the following vulnerability has been resolved: powerpc/xive: Fix refcount leak in xive_get_max_prio of_find_node_by_path() 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.
- https://git.kernel.org/stable/c/255b650cbec6849443ce2e0cdd187fd5e61c218c
- https://git.kernel.org/stable/c/2e18b869a8d574cfe9ee64df9c3d0a7ac7ed07a8
- https://git.kernel.org/stable/c/5ed9709d262bf026b2ff64979fbfe0f496287588
- https://git.kernel.org/stable/c/6d1e53f7f181a11a8a343def1e0d0209905b7c64
- https://git.kernel.org/stable/c/79b8eae24b7ee157bda07695d802be8576983fa8
- https://git.kernel.org/stable/c/d99733ad47a6c990b52e136608455643bfa708f2
- https://git.kernel.org/stable/c/ea494e8a9852abd0ba60f69b254ce0d7c38449e2
- https://git.kernel.org/stable/c/f658d5b528ce97a68efbb64ee54f6fe0909b189a
Modified: 2025-11-19
CVE-2022-50105
In the Linux kernel, the following vulnerability has been resolved: powerpc/spufs: Fix refcount leak in spufs_init_isolated_loader of_find_node_by_path() returns remote device nodepointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak.
- https://git.kernel.org/stable/c/0aa5de2547b7ccf0a31bc740d12f829fae243112
- https://git.kernel.org/stable/c/14329d29a048dc35aac2374fb3d588d8190095a2
- https://git.kernel.org/stable/c/4288eb035ba4ddb53245e9365c919bb51ac00c2c
- https://git.kernel.org/stable/c/43584490ee6c8a104797444af6bf89d0dafe95c0
- https://git.kernel.org/stable/c/69e9fa07b229badab808980e984a9fe824116f00
- https://git.kernel.org/stable/c/6ac059dacffa8ab2f7798f20e4bd3333890c541c
- https://git.kernel.org/stable/c/85aff6a9b7b7ec4e5c319f7946c9864c8d5e3d4a
- https://git.kernel.org/stable/c/d0cb99948c5f6d8fe56f6e69b8dd0a05ee5f9cec
Modified: 2025-11-19
CVE-2022-50106
In the Linux kernel, the following vulnerability has been resolved: powerpc/cell/axon_msi: Fix refcount leak in setup_msi_msg_address of_get_next_parent() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() in the error path to avoid refcount leak.
- https://git.kernel.org/stable/c/00dc7cbbb558955ff410fd392cc9b0366eb06df0
- https://git.kernel.org/stable/c/02ed44125d7a7238999750ca126b60f8dd7a88b1
- https://git.kernel.org/stable/c/51cf876b11fb6ca06f69e9d1de58f892d1522e9d
- https://git.kernel.org/stable/c/5eaa93caa63abf382b319dbe2f032232026740c2
- https://git.kernel.org/stable/c/6263ec8032c411b8ef6b7f00198cb18c855ee6cb
- https://git.kernel.org/stable/c/af41cff4ada533b1cf40de6c468ba164fd32c22d
- https://git.kernel.org/stable/c/df5d4b616ee76abc97e5bd348e22659c2b095b1c
- https://git.kernel.org/stable/c/f388643657cd5a04dc47a68d85321876c5b4c208
Modified: 2025-11-19
CVE-2022-50108
In the Linux kernel, the following vulnerability has been resolved: mfd: max77620: Fix refcount leak in max77620_initialise_fps of_get_child_by_name() 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.
- https://git.kernel.org/stable/c/1520669c8255bd637c6b248b2be910e2688d38dd
- https://git.kernel.org/stable/c/50d5fe8cb94c319cb4316f4d824570c075565354
- https://git.kernel.org/stable/c/a29c40814039535b950149311986a5f348b5db14
- https://git.kernel.org/stable/c/afdbadbf18c19779d7bc5df70d872924f9bbd76b
- https://git.kernel.org/stable/c/b948ff8a9e9ad46d4dff9127777caa14c8c2b53c
- https://git.kernel.org/stable/c/facd31bbc799f4d0cd25d9d688af7ca41e7f38ee
Modified: 2025-11-19
CVE-2022-50109
In the Linux kernel, the following vulnerability has been resolved: video: fbdev: amba-clcd: Fix refcount leak bugs In clcdfb_of_init_display(), we should call of_node_put() for the references returned by of_graph_get_next_endpoint() and of_graph_get_remote_port_parent() which have increased the refcount. Besides, we should call of_node_put() both in fail path or when the references are not used anymore.
- https://git.kernel.org/stable/c/2688df86c02da6bdc9866b62d974e169a2678883
- https://git.kernel.org/stable/c/26c2b7d9fac42eb8317f3ceefa4c1a9a9170ca69
- https://git.kernel.org/stable/c/29f06f1905c312671a09ee85ca92ac04a1d9f305
- https://git.kernel.org/stable/c/49a4c1a87ef884e43cdda58b142a2a30f2f09efc
- https://git.kernel.org/stable/c/a51519ebd0fdad3546463018b8f6bc3b0f4d3032
- https://git.kernel.org/stable/c/a88ab277cca99aeb9a3b2b7db358f1a6dd528b0c
- https://git.kernel.org/stable/c/a97ff8a949dbf41be89f436b2b1a2b3d794493df
- https://git.kernel.org/stable/c/da276dc288bf838ea0fd778b5441ec0f601c69f7
Modified: 2025-11-18
CVE-2022-50112
In the Linux kernel, the following vulnerability has been resolved: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done.
- https://git.kernel.org/stable/c/43e42c25a232a6862e7d2f292a069ac828559030
- https://git.kernel.org/stable/c/65382585f067d4256ba087934f30f85c9b6984de
- https://git.kernel.org/stable/c/8ee5d40ae29e63f6fd6cbf9dcfc0a48c474013db
- https://git.kernel.org/stable/c/9715809b9eeb85b3f9b083857a2f29a9e2351125
- https://git.kernel.org/stable/c/ae7fdbab97df6a2115eed6b7e39c278b805c9c7d
- https://git.kernel.org/stable/c/cb50423e46ea585620a6be307d7f7b71587936b7
- https://git.kernel.org/stable/c/ece6cfe62a103cc6032664983be557f1b5a1ff7e
Modified: 2025-11-18
CVE-2022-50122
In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8173-rt5650: Fix refcount leak in mt8173_rt5650_dev_probe of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Fix refcount leak in some error paths.
- https://git.kernel.org/stable/c/06ace427953f5036b64aed658f0055f65d76fd27
- https://git.kernel.org/stable/c/403d46971936f9f704b91cecffe66e44aa39e915
- https://git.kernel.org/stable/c/5ec83aa7a9e5bcca80ccd49978916feb4e0ffc07
- https://git.kernel.org/stable/c/79f566907d27abbd7600cebe51def5081d5796b5
- https://git.kernel.org/stable/c/994f2edeeb2114bb22b62741cb8fb030fc7e5441
- https://git.kernel.org/stable/c/e024a24fb264523149658c10c76bb363b3d0004d
- https://git.kernel.org/stable/c/e38e4952ac7a316c9002af30980d6aa850214474
- https://git.kernel.org/stable/c/efe2178d1a32492f99e7f1f2568eea5c88a85729
Modified: 2025-11-18
CVE-2022-50123
In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8173: Fix refcount leak in mt8173_rt5650_rt5676_dev_probe of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Fix missing of_node_put() in error paths.
- https://git.kernel.org/stable/c/540c7b7385fb110740703888b4b2bbfa06c7f79c
- https://git.kernel.org/stable/c/58567ed2878f70e0ded242cb529fb4a7618ea9f8
- https://git.kernel.org/stable/c/769399bce8825e1dcc5050dab78e15ab578baf4f
- https://git.kernel.org/stable/c/aa1214ece37944e4dbbb5cfb1d02bf37e4d89b02
- https://git.kernel.org/stable/c/aa668f8e93199cda8fa1612eb49ff70f5ecd8c92
- https://git.kernel.org/stable/c/ae4f11c1ed2d67192fdf3d89db719ee439827c11
- https://git.kernel.org/stable/c/d6d41f04640db0f946e2c3f7963bb2774afc7a0d
- https://git.kernel.org/stable/c/fab5eb31819a2693b0c3d6f3df6a0d193af9a089
Modified: 2025-11-18
CVE-2022-50124
In the Linux kernel, the following vulnerability has been resolved: ASoC: mt6797-mt6351: Fix refcount leak in mt6797_mt6351_dev_probe 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.
- https://git.kernel.org/stable/c/1042353bb67cd1c9109d7481ea182c7794336458
- https://git.kernel.org/stable/c/38dc6faef05f33b4c889be8b7d65878e465c1c4b
- https://git.kernel.org/stable/c/67a28402a9e8c229c7588f214d81d52903ea06ea
- https://git.kernel.org/stable/c/7472eb8d7dd12b6b9b1a4f4527719cc9c7f5965f
- https://git.kernel.org/stable/c/7dee72b1bcecb26bfff8d6360f2169f8656dbaf6
- https://git.kernel.org/stable/c/a0381a9f3e595988e83bac4c4dd1e45ed2b3c744
- https://git.kernel.org/stable/c/b488ceb2336905f071f80627bc8a7d657274e5de
Modified: 2025-11-18
CVE-2022-50126
In the Linux kernel, the following vulnerability has been resolved:
jbd2: fix assertion 'jh->b_frozen_data == NULL' failure when journal aborted
Following process will fail assertion 'jh->b_frozen_data == NULL' in
jbd2_journal_dirty_metadata():
jbd2_journal_commit_transaction
unlink(dir/a)
jh->b_transaction = trans1
jh->b_jlist = BJ_Metadata
journal->j_running_transaction = NULL
trans1->t_state = T_COMMIT
unlink(dir/b)
handle->h_trans = trans2
do_get_write_access
jh->b_modified = 0
jh->b_frozen_data = frozen_buffer
jh->b_next_transaction = trans2
jbd2_journal_dirty_metadata
is_handle_aborted
is_journal_aborted // return false
--> jbd2 abort <--
while (commit_transaction->t_buffers)
if (is_journal_aborted)
jbd2_journal_refile_buffer
__jbd2_journal_refile_buffer
WRITE_ONCE(jh->b_transaction,
jh->b_next_transaction)
WRITE_ONCE(jh->b_next_transaction, NULL)
__jbd2_journal_file_buffer(jh, BJ_Reserved)
J_ASSERT_JH(jh, jh->b_frozen_data == NULL) // assertion failure !
The reproducer (See detail in [Link]) reports:
------------[ cut here ]------------
kernel BUG at fs/jbd2/transaction.c:1629!
invalid opcode: 0000 [#1] PREEMPT SMP
CPU: 2 PID: 584 Comm: unlink Tainted: G W
5.19.0-rc6-00115-g4a57a8400075-dirty #697
RIP: 0010:jbd2_journal_dirty_metadata+0x3c5/0x470
RSP: 0018:ffffc90000be7ce0 EFLAGS: 00010202
Call Trace:
- https://git.kernel.org/stable/c/0f61c6dc4b714be9d79cf0782ca02ba01c1b7ac3
- https://git.kernel.org/stable/c/4a734f0869f970b8a9b65062ea40b09a5da9dba8
- https://git.kernel.org/stable/c/6073389db83b903678a0920554fa19f5bdc51c48
- https://git.kernel.org/stable/c/731c1662d838fe954c6759e3ee43229b0d928fe4
- https://git.kernel.org/stable/c/ddd896792e1718cb84c96f3e618270589b6886dc
- https://git.kernel.org/stable/c/e62f79827784f56499a50ea2e893c98317b5407b
- https://git.kernel.org/stable/c/f7161d0da975adc234161cd0641d0e484f5ce375
- https://git.kernel.org/stable/c/fa5b65d39332fef7a11ae99cb1f0696012a61527
Modified: 2025-11-18
CVE-2022-50127
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix error unwind in rxe_create_qp() In the function rxe_create_qp(), rxe_qp_from_init() is called to initialize qp, internally things like the spin locks are not setup until rxe_qp_init_req(). If an error occures before this point then the unwind will call rxe_cleanup() and eventually to rxe_qp_do_cleanup()/rxe_cleanup_task() which will oops when trying to access the uninitialized spinlock. Move the spinlock initializations earlier before any failures.
- https://git.kernel.org/stable/c/1a63f24e724f677db1ab21251f4d0011ae0bb5b5
- https://git.kernel.org/stable/c/2ceeb04252e621c0b128ecc8fedbca922d11adba
- https://git.kernel.org/stable/c/3c838ca6fbdb173102780d7bdf18f2f7d9e30979
- https://git.kernel.org/stable/c/3ef491b26c720a87fcfbd78b7dc8eb83d9753fe6
- https://git.kernel.org/stable/c/b348e204a53103f51070513a7494da7c62ecbdaa
- https://git.kernel.org/stable/c/db924bd8484c76558a4ac4c4b5aeb52e857f0341
- https://git.kernel.org/stable/c/f05b7cf02123aaf99db78abfe638efefdbe15555
- https://git.kernel.org/stable/c/fd5382c5805c4bcb50fd25b7246247d3f7114733
Modified: 2025-11-18
CVE-2022-50134
In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: fix potential memory leak in setup_base_ctxt() setup_base_ctxt() allocates a memory chunk for uctxt->groups with hfi1_alloc_ctxt_rcv_groups(). When init_user_ctxt() fails, uctxt->groups is not released, which will lead to a memory leak. We should release the uctxt->groups with hfi1_free_ctxt_rcv_groups() when init_user_ctxt() fails.
- https://git.kernel.org/stable/c/1750be1e9f18787cf717c24dbc5fa029fc372a22
- https://git.kernel.org/stable/c/2f90813f1c21c3d780585390af961bd17c8515ae
- https://git.kernel.org/stable/c/90ef48a718f88935d4af53d7dadd1ceafe103ce6
- https://git.kernel.org/stable/c/a85c7dd1edadcdeca24e603a6618153a3bcc81ca
- https://git.kernel.org/stable/c/a9055dfe437efae77e28e57205437c878a03ccb7
- https://git.kernel.org/stable/c/aa2a1df3a2c85f855af7d54466ac10bd48645d63
- https://git.kernel.org/stable/c/e25b828553aecb3185a8d8d0c4f9b4e133fb5db6
- https://git.kernel.org/stable/c/fc4de8009fd6c2ca51986c6757efa964040e7d02
Modified: 2025-11-18
CVE-2022-50136
In the Linux kernel, the following vulnerability has been resolved:
RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event
If siw_recv_mpa_rr returns -EAGAIN, it means that the MPA reply hasn't
been received completely, and should not report IW_CM_EVENT_CONNECT_REPLY
in this case. This may trigger a call trace in iw_cm. A simple way to
trigger this:
server: ib_send_lat
client: ib_send_lat -R
- https://git.kernel.org/stable/c/0066246d2d7e2619f3ecf3cf07333c59e6e7d84d
- https://git.kernel.org/stable/c/11edf0bba15ea9df49478affec7974f351bb2f6e
- https://git.kernel.org/stable/c/1434de50a5d9dab91c8ce031bc23b3e2178379c5
- https://git.kernel.org/stable/c/3056fc6c32e613b760422b94c7617ac9a24a4721
- https://git.kernel.org/stable/c/9ade92ddaf2347fb34298c02080caaa3cdd7c27b
- https://git.kernel.org/stable/c/f6e26e1a5f600b760dc32135d3fac846eabe09e7
Modified: 2025-11-18
CVE-2022-50140
In the Linux kernel, the following vulnerability has been resolved: memstick/ms_block: Fix a memory leak 'erased_blocks_bitmap' is never freed. As it is allocated at the same time as 'used_blocks_bitmap', it is likely that it should be freed also at the same time. Add the corresponding bitmap_free() in msb_data_clear().
- https://git.kernel.org/stable/c/16e07966638717416abf45393d6a80a5a1034429
- https://git.kernel.org/stable/c/37958980eb4cd71ae594ace093c11b6a91e165e8
- https://git.kernel.org/stable/c/39be95d1ff7b44c1e969af72ba9da7332dfcc1da
- https://git.kernel.org/stable/c/54eb7a55be6779c4d0c25eaf5056498a28595049
- https://git.kernel.org/stable/c/9260a154b3b5e387dbceec7c0ac441470646bc6f
- https://git.kernel.org/stable/c/961d7d12080fe70847f944d656e36cd0dd0214ba
- https://git.kernel.org/stable/c/9d8b911fe3c3ed788c66edba7c90e32a4a7a5f53
- https://git.kernel.org/stable/c/efd675246aec045507b9425c67b548cc2d782d8f
Modified: 2025-11-18
CVE-2022-50141
In the Linux kernel, the following vulnerability has been resolved: mmc: sdhci-of-esdhc: Fix refcount leak in esdhc_signal_voltage_switch 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. of_node_put() checks null pointer.
- https://git.kernel.org/stable/c/352377cf74710bc3368dddf78f17210dfe456933
- https://git.kernel.org/stable/c/4c472a2c9ed6ea9d272268d7f484d4303c549f1a
- https://git.kernel.org/stable/c/547db1dd98d1815574ebea7358015a17199a93bc
- https://git.kernel.org/stable/c/8b902840f6a3584f702bcb59834691b30f3d7c5a
- https://git.kernel.org/stable/c/a63d5d01e83b984b1b9c7ae8fc9c8c93697a3820
- https://git.kernel.org/stable/c/b074f1e8060836baeb0ee91181f4194b9a0ee16a
- https://git.kernel.org/stable/c/b305475df756256a186623f0991d05a816de881a
- https://git.kernel.org/stable/c/b5899a3e2f783a27b268e38d37f9b24c71bddf45
Modified: 2025-11-19
CVE-2022-50142
In the Linux kernel, the following vulnerability has been resolved:
intel_th: msu: Fix vmalloced buffers
After commit f5ff79fddf0e ("dma-mapping: remove CONFIG_DMA_REMAP") there's
a chance of DMA buffer getting allocated via vmalloc(), which messes up
the mmapping code:
> RIP: msc_mmap_fault [intel_th_msu]
> Call Trace:
>
- https://git.kernel.org/stable/c/0ed72c6bc632cbf8d979ac60f982ff84b7bb610a
- https://git.kernel.org/stable/c/4914c50670b6a531e2cb17cd984cc565b4681312
- https://git.kernel.org/stable/c/566887bad7ff2297d6b3f9659c702ba075f3d62d
- https://git.kernel.org/stable/c/6ae2881c1d1fa0e33f4763b7c786f8ef05a9c828
- https://git.kernel.org/stable/c/ac12ad3ccf6d386e64a9d6a890595a2509d24edd
- https://git.kernel.org/stable/c/b5d924cb4c7b952eaa61622f14427723a78137a3
Modified: 2025-11-20
CVE-2022-50143
In the Linux kernel, the following vulnerability has been resolved: intel_th: Fix a resource leak in an error handling path If an error occurs after calling 'pci_alloc_irq_vectors()', 'pci_free_irq_vectors()' must be called as already done in the remove function.
- https://git.kernel.org/stable/c/086c28ab7c5699256aced0049aae9c42f1410313
- https://git.kernel.org/stable/c/859342220accd0d332864fafbf4e3d2d0492bc3f
- https://git.kernel.org/stable/c/9b5469573a274729bdb04b60a8d71f8d09940a31
- https://git.kernel.org/stable/c/a8f3b78b1f8e959d06801ae82149f140a75724e8
- https://git.kernel.org/stable/c/ed4d5ecb7d7fd80336afb2f9ac6685651a6aa32f
- https://git.kernel.org/stable/c/fae9da7d4c2ccad3792de03e3cac1fe2bfabb73d
Modified: 2025-11-17
CVE-2022-50149
In the Linux kernel, the following vulnerability has been resolved:
driver core: fix potential deadlock in __driver_attach
In __driver_attach function, There are also AA deadlock problem,
like the commit b232b02bf3c2 ("driver core: fix deadlock in
__device_attach").
stack like commit b232b02bf3c2 ("driver core: fix deadlock in
__device_attach").
list below:
In __driver_attach function, The lock holding logic is as follows:
...
__driver_attach
if (driver_allows_async_probing(drv))
device_lock(dev) // get lock dev
async_schedule_dev(__driver_attach_async_helper, dev); // func
async_schedule_node
async_schedule_node_domain(func)
entry = kzalloc(sizeof(struct async_entry), GFP_ATOMIC);
/* when fail or work limit, sync to execute func, but
__driver_attach_async_helper will get lock dev as
will, which will lead to A-A deadlock. */
if (!entry || atomic_read(&entry_count) > MAX_WORK) {
func;
else
queue_work_node(node, system_unbound_wq, &entry->work)
device_unlock(dev)
As above show, when it is allowed to do async probes, because of
out of memory or work limit, async work is not be allowed, to do
sync execute instead. it will lead to A-A deadlock because of
__driver_attach_async_helper getting lock dev.
Reproduce:
and it can be reproduce by make the condition
(if (!entry || atomic_read(&entry_count) > MAX_WORK)) untenable, like
below:
[ 370.785650] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 370.787154] task:swapper/0 state:D stack: 0 pid: 1 ppid:
0 flags:0x00004000
[ 370.788865] Call Trace:
[ 370.789374]
- https://git.kernel.org/stable/c/37f908038402c9b8325763f306a1c65d88757e15
- https://git.kernel.org/stable/c/70fe758352cafdee72a7b13bf9db065f9613ced8
- https://git.kernel.org/stable/c/733ab0c19bf17f6ad7c2b580ede006e369d5ab1b
- https://git.kernel.org/stable/c/779b634714c51d05baaeff4868ce2fd9fc7399bf
- https://git.kernel.org/stable/c/8191b6cd9ada09b675f17446d5872eb1f77685cb
- https://git.kernel.org/stable/c/a93f33aeef4e6a94ae9c9d3f5b2f9085ad0572ec
Modified: 2025-11-20
CVE-2022-50152
In the Linux kernel, the following vulnerability has been resolved: usb: ohci-nxp: Fix refcount leak in ohci_hcd_nxp_probe 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.
- https://git.kernel.org/stable/c/302970b4cad3ebfda2c05ce06c322ccdc447d17e
- https://git.kernel.org/stable/c/4db00c2fa6f8c9876a7e20511dccf43b50be9006
- https://git.kernel.org/stable/c/50238c4b54c2ac6c2da7a84a4a2b0a570e3da0e2
- https://git.kernel.org/stable/c/59026d5cc615da28e0c9806a71bf07065c906464
- https://git.kernel.org/stable/c/591ab8dbf6c21927f23f83ddb90691f48b86d136
- https://git.kernel.org/stable/c/65d36ec409b635dfc2f95f0d7c5877c9d0cb7630
- https://git.kernel.org/stable/c/a0fbac3bf26a11f084233519ddf3fd5e5bb28939
- https://git.kernel.org/stable/c/d35903e9650f4fa79426ce390db8678dbf5ac432
Modified: 2025-11-25
CVE-2022-50153
In the Linux kernel, the following vulnerability has been resolved: usb: host: Fix refcount leak in ehci_hcd_ppc_of_probe 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.
- https://git.kernel.org/stable/c/038453b17fe30ea38f0f3c916e2ae2b7f8cef84e
- https://git.kernel.org/stable/c/3a50c917c67dd0bc39c14de4a8b75a1d50fdce66
- https://git.kernel.org/stable/c/585d22a5624ef2b540c337665c72fea8cd33db50
- https://git.kernel.org/stable/c/8cbc3870ff356366842af3228dd8e7bc278e5edd
- https://git.kernel.org/stable/c/8e51a512c1079109bec4c80915e647692d583e79
- https://git.kernel.org/stable/c/b5c5b13cb45e2c88181308186b0001992cb41954
- https://git.kernel.org/stable/c/b9c4a480cb0ada07154debf681454cbb55e30b59
- https://git.kernel.org/stable/c/c0a4b454486b23bb4d94ce49f490830ecc354040
Modified: 2025-11-25
CVE-2022-50156
In the Linux kernel, the following vulnerability has been resolved: HID: cp2112: prevent a buffer overflow in cp2112_xfer() Smatch warnings: drivers/hid/hid-cp2112.c:793 cp2112_xfer() error: __memcpy() 'data->block[1]' too small (33 vs 255) drivers/hid/hid-cp2112.c:793 cp2112_xfer() error: __memcpy() 'buf' too small (64 vs 255) The 'read_length' variable is provided by 'data->block[0]' which comes from user and it(read_length) can take a value between 0-255. Add an upper bound to 'read_length' variable to prevent a buffer overflow in memcpy().
- https://git.kernel.org/stable/c/26e427ac85c2b8d0d108cc80b6de34d33e2780c4
- https://git.kernel.org/stable/c/381583845d19cb4bd21c8193449385f3fefa9caf
- https://git.kernel.org/stable/c/3af7d60e9a6c17d6d41c4341f8020511887d372d
- https://git.kernel.org/stable/c/519ff31a6ddd87aa4905bd9bf3b92e8b88801614
- https://git.kernel.org/stable/c/8489a20ac481b08c0391608d81ed3796d373cfdf
- https://git.kernel.org/stable/c/e7028944e61014ae915e7fb74963d3835f2f761a
- https://git.kernel.org/stable/c/ebda3d6b004bb6127a66a616524a2de152302ca7
Modified: 2025-11-25
CVE-2022-50158
In the Linux kernel, the following vulnerability has been resolved: mtd: partitions: Fix refcount leak in parse_redboot_of of_get_child_by_name() 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.
- https://git.kernel.org/stable/c/55d0f7da66dec93c4d53d0886a1555618079a900
- https://git.kernel.org/stable/c/7ec48ac18d8f9e002ce9bfbad32741086739e499
- https://git.kernel.org/stable/c/8ea607579d300b2f7fc997f3dd20949114565fcd
- https://git.kernel.org/stable/c/9f7e62815cf3cbbcb1b8cb21649fb4dfdb3aa016
- https://git.kernel.org/stable/c/e24af43d0cbe9f6aaa413c15ccce50bbbfd61e0e
- https://git.kernel.org/stable/c/f3cc27198c5d78cdda60a55ae749f815cd1fe5eb
Modified: 2025-11-18
CVE-2022-50160
In the Linux kernel, the following vulnerability has been resolved: mtd: maps: Fix refcount leak in ap_flash_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.
- https://git.kernel.org/stable/c/77087a04c8fd554134bddcb8a9ff87b21f357926
- https://git.kernel.org/stable/c/80b1465b2ae81ebb59bbe62bcb7a7f7d4e9ece6f
- https://git.kernel.org/stable/c/941ef6997f9db704fe4fd62fc01e420fdd5048b2
- https://git.kernel.org/stable/c/995fb2874bb5696357846a91e59181c600e6aac8
- https://git.kernel.org/stable/c/a74322d4b897ddc268b340c4a397f6066c2f945d
- https://git.kernel.org/stable/c/babd7b0124650ab71a6487e38588b8659b3aa2dc
- https://git.kernel.org/stable/c/d10855876a6f47add6ff621cef25cc0171dac162
- https://git.kernel.org/stable/c/d5730780e9ea84e5476752a47c749036c6a74af5
Modified: 2025-11-18
CVE-2022-50161
In the Linux kernel, the following vulnerability has been resolved: mtd: maps: Fix refcount leak in of_flash_probe_versatile of_find_matching_node_and_match() 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.
- https://git.kernel.org/stable/c/33ec82a6d2b119938f26e5c8040ed5d92378eb54
- https://git.kernel.org/stable/c/3c8de6a838b7e0eb392754ac89dd66e698684342
- https://git.kernel.org/stable/c/4d67c8f74d804b20febf716ec96e9a475457ec60
- https://git.kernel.org/stable/c/52ae2b14f76ef2d490337ddc0037bc37125be7b8
- https://git.kernel.org/stable/c/5d5ddd8771fa9cabeb247fba5f6ab60d63f3fbce
- https://git.kernel.org/stable/c/79e57889aa0d92a6d769bad808fb105e7b6ea495
- https://git.kernel.org/stable/c/9124d51e01232a91da4034768a2a8d1688472179
- https://git.kernel.org/stable/c/f516fbb63873ee23cba5b7c3d239677c30f13df8
Modified: 2025-11-18
CVE-2022-50162
In the Linux kernel, the following vulnerability has been resolved: wifi: libertas: Fix possible refcount leak in if_usb_probe() usb_get_dev will be called before lbs_get_firmware_async which means that usb_put_dev need to be called when lbs_get_firmware_async fails.
- https://git.kernel.org/stable/c/00d0c4e59c0f8ad1f86874bb64b220394e687028
- https://git.kernel.org/stable/c/4c8e2f9ce1428e44cb103035eeced7aeb6b80980
- https://git.kernel.org/stable/c/5b92f406a5199b6b01dc664b9226d824ae2835f0
- https://git.kernel.org/stable/c/61b2ec97487399c58ae2e34f250f4884e671799b
- https://git.kernel.org/stable/c/6fd57e1d120bf13d4dc6c200a7cf914e6347a316
- https://git.kernel.org/stable/c/878e7f39803a9ab5bb9766956a7a04351d4bf99d
- https://git.kernel.org/stable/c/97e5d3e46a3a2100253a9717a4df98d68aeb10b8
- https://git.kernel.org/stable/c/d7365590d15bbd9008f424ef043d1778ffe29f42
Modified: 2025-11-18
CVE-2022-50164
In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: mvm: fix double list_add at iwl_mvm_mac_wake_tx_queue
After successfull station association, if station queues are disabled for
some reason, the related lists are not emptied. So if some new element is
added to the list in iwl_mvm_mac_wake_tx_queue, it can match with the old
one and produce a BUG like this:
[ 46.535263] list_add corruption. prev->next should be next (ffff94c1c318a360), but was 0000000000000000. (prev=ffff94c1d02d3388).
[ 46.535283] ------------[ cut here ]------------
[ 46.535284] kernel BUG at lib/list_debug.c:26!
[ 46.535290] invalid opcode: 0000 [#1] PREEMPT SMP PTI
[ 46.585304] CPU: 0 PID: 623 Comm: wpa_supplicant Not tainted 5.19.0-rc3+ #1
[ 46.592380] Hardware name: Dell Inc. Inspiron 660s/0478VN , BIOS A07 08/24/2012
[ 46.600336] RIP: 0010:__list_add_valid.cold+0x3d/0x3f
[ 46.605475] Code: f2 4c 89 c1 48 89 fe 48 c7 c7 c8 40 67 93 e8 20 cc fd ff 0f 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 70 40 67 93 e8 09 cc fd ff <0f> 0b 48 89 fe 48 c7 c7 00 41 67 93 e8 f8 cb fd ff 0f 0b 48 89 d1
[ 46.624469] RSP: 0018:ffffb20800ab76d8 EFLAGS: 00010286
[ 46.629854] RAX: 0000000000000075 RBX: ffff94c1c318a0e0 RCX: 0000000000000000
[ 46.637105] RDX: 0000000000000201 RSI: ffffffff9365e100 RDI: 00000000ffffffff
[ 46.644356] RBP: ffff94c1c5f43370 R08: 0000000000000075 R09: 3064316334396666
[ 46.651607] R10: 3364323064316334 R11: 39666666663d7665 R12: ffff94c1c5f43388
[ 46.658857] R13: ffff94c1d02d3388 R14: ffff94c1c318a360 R15: ffff94c1cf2289c0
[ 46.666108] FS: 00007f65634ff7c0(0000) GS:ffff94c1da200000(0000) knlGS:0000000000000000
[ 46.674331] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 46.680170] CR2: 00007f7dfe984460 CR3: 000000010e894003 CR4: 00000000000606f0
[ 46.687422] Call Trace:
[ 46.689906]
- https://git.kernel.org/stable/c/14a3aacf517a9de725dd3219dbbcf741e31763c4
- https://git.kernel.org/stable/c/182d3c1385f44ba7c508bf5b1292a7fe96ad4e9e
- https://git.kernel.org/stable/c/38d71acc15a2e72806b516380af0adb3830d4639
- https://git.kernel.org/stable/c/4a40af2b0b9517fca7ae2a030c9c0a16836303c0
- https://git.kernel.org/stable/c/5cca5f714fe6cedd2df9d8451ad8df21e6464f62
- https://git.kernel.org/stable/c/ff068c25bf90d26f0aee1751553f18076b797e8d
Modified: 2025-11-17
CVE-2022-50165
In the Linux kernel, the following vulnerability has been resolved: wifi: wil6210: debugfs: fix uninitialized variable use in `wil_write_file_wmi()` Commit 7a4836560a61 changes simple_write_to_buffer() with memdup_user() but it forgets to change the value to be returned that came from simple_write_to_buffer() call. It results in the following warning: warning: variable 'rc' is uninitialized when used here [-Wuninitialized] return rc; ^~ Remove rc variable and just return the passed in length if the memdup_user() succeeds.
- https://git.kernel.org/stable/c/409bd72e544fdf4809ea0dac337bb5a1f11a25a9
- https://git.kernel.org/stable/c/52b11a48cf073e0aab923ae809a765d756cecf13
- https://git.kernel.org/stable/c/689e5caf63e99e15d2f485ec297c1bf9243e0e28
- https://git.kernel.org/stable/c/6c5fee83bdbeffe8d607d1ab125122a75f40bd1a
- https://git.kernel.org/stable/c/b13c84e877d7a3095bacb14665db304b2c00e95f
- https://git.kernel.org/stable/c/c9fde3a44da566d8929070ab6bda4f0dfa9955d0
- https://git.kernel.org/stable/c/d4742c886043b69d2d058bfde3998ef333b66595
- https://git.kernel.org/stable/c/d578e0af3a003736f6c440188b156483d451b329
Modified: 2026-01-23
CVE-2022-50169
In the Linux kernel, the following vulnerability has been resolved: wifi: wil6210: debugfs: fix info leak in wil_write_file_wmi() The simple_write_to_buffer() function will succeed if even a single byte is initialized. However, we need to initialize the whole buffer to prevent information leaks. Just use memdup_user().
- https://git.kernel.org/stable/c/05ceda14ef7c73104e709c414c3680d8a59f51d4
- https://git.kernel.org/stable/c/074e865b37da55aa87baa16d68b96896f85f8adb
- https://git.kernel.org/stable/c/4615458db7793fadc6d546ac3564b36819e77a22
- https://git.kernel.org/stable/c/60c9983425167ec5073c628d83a6875760d18059
- https://git.kernel.org/stable/c/67470920cd3f3cb38699b1ad23234f96bead4d21
- https://git.kernel.org/stable/c/789edc1af9c1a2293956e8534bfef3d18d629de9
- https://git.kernel.org/stable/c/7a4836560a6198d245d5732e26f94898b12eb760
- https://git.kernel.org/stable/c/c1216e699a1ce83ea005510844bd7508d34c6cef
Modified: 2025-11-28
CVE-2022-50173
In the Linux kernel, the following vulnerability has been resolved: drm/msm/mdp5: Fix global state lock backoff We need to grab the lock after the early return for !hwpipe case. Otherwise, we could have hit contention yet still returned 0. Fixes an issue that the new CONFIG_DRM_DEBUG_MODESET_LOCK stuff flagged in CI: WARNING: CPU: 0 PID: 282 at drivers/gpu/drm/drm_modeset_lock.c:296 drm_modeset_lock+0xf8/0x154 Modules linked in: CPU: 0 PID: 282 Comm: kms_cursor_lega Tainted: G W 5.19.0-rc2-15930-g875cc8bc536a #1 Hardware name: Qualcomm Technologies, Inc. DB820c (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : drm_modeset_lock+0xf8/0x154 lr : drm_atomic_get_private_obj_state+0x84/0x170 sp : ffff80000cfab6a0 x29: ffff80000cfab6a0 x28: 0000000000000000 x27: ffff000083bc4d00 x26: 0000000000000038 x25: 0000000000000000 x24: ffff80000957ca58 x23: 0000000000000000 x22: ffff000081ace080 x21: 0000000000000001 x20: ffff000081acec18 x19: ffff80000cfabb80 x18: 0000000000000038 x17: 0000000000000000 x16: 0000000000000000 x15: fffffffffffea0d0 x14: 0000000000000000 x13: 284e4f5f4e524157 x12: 5f534b434f4c5f47 x11: ffff80000a386aa8 x10: 0000000000000029 x9 : ffff80000cfab610 x8 : 0000000000000029 x7 : 0000000000000014 x6 : 0000000000000000 x5 : 0000000000000001 x4 : ffff8000081ad904 x3 : 0000000000000029 x2 : ffff0000801db4c0 x1 : ffff80000cfabb80 x0 : ffff000081aceb58 Call trace: drm_modeset_lock+0xf8/0x154 drm_atomic_get_private_obj_state+0x84/0x170 mdp5_get_global_state+0x54/0x6c mdp5_pipe_release+0x2c/0xd4 mdp5_plane_atomic_check+0x2ec/0x414 drm_atomic_helper_check_planes+0xd8/0x210 drm_atomic_helper_check+0x54/0xb0 ... ---[ end trace 0000000000000000 ]--- drm_modeset_lock attempting to lock a contended lock without backoff: drm_modeset_lock+0x148/0x154 mdp5_get_global_state+0x30/0x6c mdp5_pipe_release+0x2c/0xd4 mdp5_plane_atomic_check+0x290/0x414 drm_atomic_helper_check_planes+0xd8/0x210 drm_atomic_helper_check+0x54/0xb0 drm_atomic_check_only+0x4b0/0x8f4 drm_atomic_commit+0x68/0xe0 Patchwork: https://patchwork.freedesktop.org/patch/492701/
- https://git.kernel.org/stable/c/0b07f28c23ff50a7fa5dbc3f6b3b6bd53ac9fc70
- https://git.kernel.org/stable/c/247f2934324f9a18d18df24ea4bfcc7d4631d0ef
- https://git.kernel.org/stable/c/2e34d6c8180a398de6448a93df25068bf3062042
- https://git.kernel.org/stable/c/2fdf5a54ef9376ff69149a48c5616f1141008c9f
- https://git.kernel.org/stable/c/92ef86ab513593c6329d04146e61f9a670e72fc5
- https://git.kernel.org/stable/c/bf386c955f35a0a01bef482b6035d40ff2f6cc75
- https://git.kernel.org/stable/c/f4e3a8c7e890049e7ba2b49ad0315dae841dfa55
Modified: 2025-11-25
CVE-2022-50176
In the Linux kernel, the following vulnerability has been resolved: drm/mcde: Fix refcount leak in mcde_dsi_bind Every iteration of for_each_available_child_of_node() decrements the reference counter of the previous node. There is no decrement when break out from the loop and results in refcount leak. Add missing of_node_put() to fix this.
- https://git.kernel.org/stable/c/3123ae6fdd4013d24a3a4877084b14e917faae5c
- https://git.kernel.org/stable/c/32c827e30bb44ae809950a9efab59e98e44d30e5
- https://git.kernel.org/stable/c/3a149169e4a2f9127022fec6ef5d71b4e804b3b9
- https://git.kernel.org/stable/c/7214902de5b1fb2b632a7b8b3b9540e41aabab38
- https://git.kernel.org/stable/c/87c35bbefdfa3c5edfb8c80f5c04717aaacc629d
- https://git.kernel.org/stable/c/f57699a9b66ea11f000f56d1f1179059239b8690
Modified: 2025-11-20
CVE-2022-50179
In the Linux kernel, the following vulnerability has been resolved:
ath9k: fix use-after-free in ath9k_hif_usb_rx_cb
Syzbot reported use-after-free Read in ath9k_hif_usb_rx_cb() [0]. The
problem was in incorrect htc_handle->drv_priv initialization.
Probable call trace which can trigger use-after-free:
ath9k_htc_probe_device()
/* htc_handle->drv_priv = priv; */
ath9k_htc_wait_for_target() <--- Failed
ieee80211_free_hw() <--- priv pointer is freed
- https://git.kernel.org/stable/c/03ca957c5f7b55660957eda20b5db4110319ac7a
- https://git.kernel.org/stable/c/0ac4827f78c7ffe8eef074bc010e7e34bc22f533
- https://git.kernel.org/stable/c/62bc1ea5c7401d77eaf73d0c6a15f3d2e742856e
- https://git.kernel.org/stable/c/6b14ab47937ba441e75e8dbb9fbfc9c55efa41c6
- https://git.kernel.org/stable/c/ab7a0ddf5f1cdec63cb21840369873806fc36d80
- https://git.kernel.org/stable/c/b66ebac40f64336ae2d053883bee85261060bd27
- https://git.kernel.org/stable/c/e9e21206b8ea62220b486310c61277e7ebfe7cec
- https://git.kernel.org/stable/c/eccd7c3e2596b574241a7670b5b53f5322f470e5
Modified: 2025-11-19
CVE-2022-50185
In the Linux kernel, the following vulnerability has been resolved: drm/radeon: fix potential buffer overflow in ni_set_mc_special_registers() The last case label can write two buffers 'mc_reg_address[j]' and 'mc_data[j]' with 'j' offset equal to SMC_NISLANDS_MC_REGISTER_ARRAY_SIZE since there are no checks for this value in both case labels after the last 'j++'. Instead of changing '>' to '>=' there, add the bounds check at the start of the second 'case' (the first one already has it). Also, remove redundant last checks for 'j' index bigger than array size. The expression is always false. Moreover, before or after the patch 'table->last' can be equal to SMC_NISLANDS_MC_REGISTER_ARRAY_SIZE and it seems it can be a valid value. Detected using the static analysis tool - Svace.
- https://git.kernel.org/stable/c/136f614931a2bb73616b292cf542da3a18daefd5
- https://git.kernel.org/stable/c/1f341053852be76f82610ce47a505d930512f05c
- https://git.kernel.org/stable/c/782e413e38dffd37cc85b08b1ccb982adb4a93ce
- https://git.kernel.org/stable/c/8508d6d23a247c29792ce2fc0df3f3404d6a6a80
- https://git.kernel.org/stable/c/9faff03617afeced1c4e5daa89e79b3906374342
- https://git.kernel.org/stable/c/db1a9add3f90ff1c641974d5bb910c16b87af4ef
- https://git.kernel.org/stable/c/deb603c5928e546609c0d5798e231d0205748943
- https://git.kernel.org/stable/c/ea73869df6ef386fc0feeb28ff66742ca835b18f
Modified: 2025-11-19
CVE-2022-50191
In the Linux kernel, the following vulnerability has been resolved: regulator: of: Fix refcount leak bug in of_get_regulation_constraints() We should call the of_node_put() for the reference returned by of_get_child_by_name() which has increased the refcount.
- https://git.kernel.org/stable/c/11ecb4f8735b0230d54a82c18b21ea778b695d61
- https://git.kernel.org/stable/c/332e555dca074c4eb2084898021c3676423814c3
- https://git.kernel.org/stable/c/35f9e861d9b9434903a8ede37a3561f78985826d
- https://git.kernel.org/stable/c/66efb665cd5ad69b27dca8571bf89fc6b9c628a4
- https://git.kernel.org/stable/c/a23098cc32860272dc6c3200ff20c34c65b7b694
- https://git.kernel.org/stable/c/b9ca8585c766616563cf3c062c6878f61f83cf00
- https://git.kernel.org/stable/c/c9df8ff290097aabd5c9200f7f729b0813d37b19
- https://git.kernel.org/stable/c/fc7b19f547bc9e622060a0a9a39da2330aa21c53
Modified: 2025-11-19
CVE-2022-50194
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.
- https://git.kernel.org/stable/c/053543ac1d095132fcfd1263805d6e25afbdc6a8
- https://git.kernel.org/stable/c/591f0697ccbac33760d3bb1ad96a5ba2b76ae9f0
- https://git.kernel.org/stable/c/97713ed9b6cc4abaa2dcc8357113c56520dc6d7f
- https://git.kernel.org/stable/c/bc73c72a856c26df7410ddf15f42257cb4960fe9
- https://git.kernel.org/stable/c/ca83c61a6ccf3934cf8d01d5ade30a5034993a86
- https://git.kernel.org/stable/c/e6e0951414a314e7db3e9e24fd924b3e15515288
Modified: 2025-11-19
CVE-2022-50197
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.
- https://git.kernel.org/stable/c/179034fb108e3655142f2af0c309cef171c34d68
- https://git.kernel.org/stable/c/22e6d8bcde8e66b64f46bf9bd2d3d0f88d40c39f
- https://git.kernel.org/stable/c/3b01353f1825151a29d08e0868b2bf01e1116ab5
- https://git.kernel.org/stable/c/a530fa52d4fdffc5f010f90c05ac63019b8ff5f8
- https://git.kernel.org/stable/c/d1ff2559cef0f6f8d97fba6337b28adb10689e16
- https://git.kernel.org/stable/c/dcbb974254d2a27240c2e50185afdde90f923feb
- https://git.kernel.org/stable/c/ecefd22d5db7ccb8bec2646e5d25e058fc33162a
- https://git.kernel.org/stable/c/f52c9be1779d70037ae300762d19b08fe3656237
Modified: 2025-11-19
CVE-2022-50198
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.
- https://git.kernel.org/stable/c/1bf747824a8ca4008879fd7d2ce6b03d7b428858
- https://git.kernel.org/stable/c/942228fbf5d4901112178b93d41225be7c0dd9de
- https://git.kernel.org/stable/c/c4f92af7fc8cecb8eb426ad187e39c7bcc6679c7
- https://git.kernel.org/stable/c/c652e0f51665f3fa575449909bbd9d7b45dfab1c
- https://git.kernel.org/stable/c/c9ec7993d00250a394d367c8a19fcfe8211c258b
- https://git.kernel.org/stable/c/d294d60dc68550fee0fbbe8a638d798dcd40b2c5
- https://git.kernel.org/stable/c/e5ab8a4967d68a8e9f8f4559d144207d085a8c02
Modified: 2025-11-19
CVE-2022-50199
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.
- https://git.kernel.org/stable/c/14bac0c7035bf920e190a63c7e1b113c72eadbf4
- https://git.kernel.org/stable/c/230ad40a59c9a9ee8f3822b9a7bec09404102ebc
- https://git.kernel.org/stable/c/507159facf002d113c4878fec67f37d62f187887
- https://git.kernel.org/stable/c/935035cf97c8cd6794044b500fb0a44a6d30ffa1
- https://git.kernel.org/stable/c/9705db1eff38d6b9114121f9e253746199b759c9
- https://git.kernel.org/stable/c/a32dc6829e33c54e751346aa3e08ddb6d0e1a6a0
Modified: 2025-11-19
CVE-2022-50200
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/15ec76fb29be31df2bccb30fc09875274cba2776
- https://git.kernel.org/stable/c/2dabe6a872a5744865372eb30ea51e8ccd21305a
- https://git.kernel.org/stable/c/477722f31ad73aa779154d1d7e00825538389f76
- https://git.kernel.org/stable/c/7363a69d8ca8f0086f8e1196c8ddaf0e168614b1
- https://git.kernel.org/stable/c/90bdf50ae70c5571a277b5601e4f5df210831e0a
- https://git.kernel.org/stable/c/9605f50157cae00eb299e1189a6d708c84935ad8
- https://git.kernel.org/stable/c/adbfdaacde18faf6cd4e490764045375266b3fbd
- https://git.kernel.org/stable/c/dedd558d9765b72c66e5a53948e9f5abc3ece1f6
Modified: 2025-11-19
CVE-2022-50202
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 function starts, and probe_count is decremented after the probe function completed. There are three cases that can prevent probe_count from dropping to 0. (a) A device being probed stopped responding (i.e. broken/malicious hardware). (b) A process emulating a USB device using /dev/raw-gadget interface stopped responding for some reason. (c) New device probe requests keeps coming in before existing device probe requests complete. The phenomenon syzbot is reporting is (b). A process which is holding system_transition_mutex and misc_mtx is waiting for probe_count to become 0 inside wait_for_device_probe(), but the probe function which is called from hub_event() work function is waiting for the processes which are blocked at mutex_lock(&misc_mtx) to respond via /dev/raw-gadget interface. This patch mitigates (b) by deferring wait_for_device_probe() from snapshot_open() to snapshot_write() and snapshot_ioctl(). Please note that the possibility of (b) remains as long as any thread which is emulating a USB device via /dev/raw-gadget interface can be blocked by uninterruptible blocking operations (e.g. mutex_lock()). Please also note that (a) and (c) are not addressed. Regarding (c), we should change the code to wait for only one device which contains the image for resuming from hibernation. I don't know how to address (a), for use of timeout for wait_for_device_probe() might result in loss of user data in the image. Maybe we should require the userland to wait for the image device before opening /dev/snapshot interface.
- https://git.kernel.org/stable/c/003a456ae6f70bb97e436e02fc5105be577c1570
- https://git.kernel.org/stable/c/2f0e18e0db42f4f8bc87d3d98333680065ceeff8
- https://git.kernel.org/stable/c/3c48d3067eaf878642276f053575a5c642600a50
- https://git.kernel.org/stable/c/5a283b59bce72c05c60e9f0fa92a28b5b850d8bb
- https://git.kernel.org/stable/c/8386c414e27caba8501119948e9551e52b527f59
- https://git.kernel.org/stable/c/8c90947e5f1801e6c7120021c6ea0f3ad6a4eb91
- https://git.kernel.org/stable/c/b8e1ae9433d7bd95f2dcc044a7a6f20a4c40d258
- https://git.kernel.org/stable/c/f7042cf9dd40733f387b7cac021e626c74b8856f
Modified: 2025-11-19
CVE-2022-50203
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.
- https://git.kernel.org/stable/c/0b4f96b47ff8dc2fa35d03c4116927248796d9af
- https://git.kernel.org/stable/c/2629d171f3d6451724549d8d10d14ac6da37a7be
- https://git.kernel.org/stable/c/3e505298a75f0bbdc96e923e76e5d45d6c8f64a7
- https://git.kernel.org/stable/c/496988a19d5c36fabf97c847db39167e42393c74
- https://git.kernel.org/stable/c/50b87a32a79bca6e275918a711fb8cc55e16d739
- https://git.kernel.org/stable/c/88d556029a78999b098d26a330bb6a7de166f426
- https://git.kernel.org/stable/c/a89a865dc9f0600fd146224e314775b9efc9d845
- https://git.kernel.org/stable/c/bdbdf69d5b78c5712c60c0004fa6aed12da36e26
Modified: 2025-11-19
CVE-2022-50205
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.
- https://git.kernel.org/stable/c/07303a9abe3a997d9864fb4315e34b5acfe8fc25
- https://git.kernel.org/stable/c/0bcdc31094a12b4baf59e241feabc9787cf635fa
- https://git.kernel.org/stable/c/5e63c5fe9123fa76ffaeff26c211308736ec3a07
- https://git.kernel.org/stable/c/7a48fdc88a3c35e046a6a0a38eba00f21c65b16e
- https://git.kernel.org/stable/c/96b18d3a1be0354ccce43f0ef61b5a3d7e432552
- https://git.kernel.org/stable/c/b3f423683818cfe15de14d5d9dff44148ff16bbf
- https://git.kernel.org/stable/c/d08bb199a406424a8ed0009efdf41710e6d849ee
- https://git.kernel.org/stable/c/fa78f336937240d1bc598db817d638086060e7e9
Modified: 2025-11-19
CVE-2022-50206
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_handler+0x9c/0xf8 | proc_sys_write+0x18/0x20 | __vfs_write+0x20/0x48 | vfs_write+0xe4/0x1d0 | ksys_write+0x70/0xf8 | __arm64_sys_write+0x20/0x28 | el0_svc_common.constprop.0+0x7c/0x1c0 | el0_svc_handler+0x2c/0xa0 | el0_svc+0x8/0x200 To fix this issue, keep the table->data as &insn->current_mode and use container_of() to retrieve the insn pointer. Another mutex is used to protect against the current_mode update but not for retrieving insn_emulation as table->data is no longer changing.
- https://git.kernel.org/stable/c/04549063d5701976034d8c2bfda3d3a8cbf0409f
- https://git.kernel.org/stable/c/07022e07017ee5540f5559b0aeb916e8383c1e1a
- https://git.kernel.org/stable/c/353b4673d01c512303c45cf2346f630cda73b5c9
- https://git.kernel.org/stable/c/6a2fd114678d7fc1b5a0f8865ae98f1c17787455
- https://git.kernel.org/stable/c/9d5fec6ba2e4117d196a8259ab54615ffe562460
- https://git.kernel.org/stable/c/af483947d472eccb79e42059276c4deed76f99a6
- https://git.kernel.org/stable/c/b51881b1da57fe9877125dfdd0aac5172958fcfd
- https://git.kernel.org/stable/c/cc69ef95988b9ef2fc730ec452a7441efb90ef5e
Modified: 2025-11-19
CVE-2022-50207
In the Linux kernel, the following vulnerability has been resolved: ARM: bcm: Fix refcount leak in bcm_kona_smc_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.
- https://git.kernel.org/stable/c/02b658bfb26452f2c13e4577a13ab802f89a6642
- https://git.kernel.org/stable/c/5afe042c889437de83f38a9d73d145742fb4f65f
- https://git.kernel.org/stable/c/62d719d31ec667276d7375b64542b080cf187797
- https://git.kernel.org/stable/c/75866df2b1d673df5b7781e565ada753a7895f04
- https://git.kernel.org/stable/c/91e7f04f53e680bc72f0a9a5c682ab652100b9c8
- https://git.kernel.org/stable/c/bc7f487395f208fd9af69e9a807815e10435aba7
- https://git.kernel.org/stable/c/c6964cb9ac7a43bf78e7d60126e2722992de2ea1
- https://git.kernel.org/stable/c/cb23389a2458c2e4bfd6c86a513cbbe1c4d35e76
Modified: 2025-11-19
CVE-2022-50209
In the Linux kernel, the following vulnerability has been resolved: meson-mx-socinfo: Fix refcount leak in meson_mx_socinfo_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.
- https://git.kernel.org/stable/c/0c1757480a6a61b8c3164ed371c359edb3928f12
- https://git.kernel.org/stable/c/2691b8780f88e1b8b3578a5bc78a0011741bbd74
- https://git.kernel.org/stable/c/69a64c77aafcf3c772264a36214937514e31ad82
- https://git.kernel.org/stable/c/6b28bf3e044f12db0fc18c42f58ae7fc3fa0144a
- https://git.kernel.org/stable/c/8a4a33b3e898b13c750b1c0c9643516c7bf6473f
- https://git.kernel.org/stable/c/a2106f38077e78afcb4bf98fdda3e162118cfb3d
- https://git.kernel.org/stable/c/e21744c6a0d4116a2d6ebccd947620ca4c952e92
Modified: 2025-11-19
CVE-2022-50210
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/0x5f0 [ 3.070072] Modules linked in: efivarfs autofs4 [ 3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052 [ 3.084034] Hardware name: Loongson Loongson-3A4000-7A1000-1w-V0.1-CRB/Loongson-LS3A4000-7A1000-1w-EVB-V1.21, BIOS Loongson-UDK2018-V2.0.04082-beta7 04/27 [ 3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000 [ 3.109127] 9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430 [ 3.118774] 90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff [ 3.128412] 0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890 [ 3.138056] 0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa [ 3.147711] ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000 [ 3.157364] 900000000101c998 0000000000000004 9000000000ef7430 0000000000000000 [ 3.167012] 0000000000000009 000000000000006c 0000000000000000 0000000000000000 [ 3.176641] 9000000000d3de08 9000000001639390 90000000002086d8 00007ffff0080286 [ 3.186260] 00000000000000b0 0000000000000004 0000000000000000 0000000000071c1c [ 3.195868] ... [ 3.199917] Call Trace: [ 3.203941] [<98000000002086d8>] show_stack+0x38/0x14c [ 3.210666] [<9800000000cf846c>] dump_stack_lvl+0x60/0x88 [ 3.217625] [<980000000023d268>] __warn+0xd0/0x100 [ 3.223958] [<9800000000cf3c90>] warn_slowpath_fmt+0x7c/0xcc [ 3.231150] [<9800000000210220>] show_cpuinfo+0x5e8/0x5f0 [ 3.238080] [<98000000004f578c>] seq_read_iter+0x354/0x4b4 [ 3.245098] [<98000000004c2e90>] new_sync_read+0x17c/0x1c4 [ 3.252114] [<98000000004c5174>] vfs_read+0x138/0x1d0 [ 3.258694] [<98000000004c55f8>] ksys_read+0x70/0x100 [ 3.265265] [<9800000000cfde9c>] do_syscall+0x7c/0x94 [ 3.271820] [<9800000000202fe4>] handle_syscall+0xc4/0x160 [ 3.281824] ---[ end trace 8b484262b4b8c24c ]---
- https://git.kernel.org/stable/c/274e44e2123417e0924c90d4b4531913b5f3aa2e
- https://git.kernel.org/stable/c/4cb392956ae392aec4aa06e661a0bb9146b0bace
- https://git.kernel.org/stable/c/7d305823e02217b29d41fca67e3cef87fd7bd688
- https://git.kernel.org/stable/c/807adf6ffa8c3beedcd63b20f5a59c7d061df7d2
- https://git.kernel.org/stable/c/8916ec149c79cb21f5454fa7840ad96f99cf51cf
- https://git.kernel.org/stable/c/98aaa511957667ba26d6dabe28dfa210a8f53a63
- https://git.kernel.org/stable/c/d3ac4e47510ec0753ebe1e418a334ad202784aa8
- https://git.kernel.org/stable/c/e1a534f5d074db45ae5cbac41d8912b98e96a006
- https://git.kernel.org/stable/c/e41db8a9ce696a3382a4f098878fd4d14bccd201
Modified: 2025-11-19
CVE-2022-50211
In the Linux kernel, the following vulnerability has been resolved:
md-raid10: fix KASAN warning
There's a KASAN warning in raid10_remove_disk when running the lvm
test lvconvert-raid-reshape.sh. We fix this warning by verifying that the
value "number" is valid.
BUG: KASAN: slab-out-of-bounds in raid10_remove_disk+0x61/0x2a0 [raid10]
Read of size 8 at addr ffff889108f3d300 by task mdX_raid10/124682
CPU: 3 PID: 124682 Comm: mdX_raid10 Not tainted 5.19.0-rc6 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
Call Trace:
- https://git.kernel.org/stable/c/0f4d18cbea4a6e37a05fd8ee2887439f85211110
- https://git.kernel.org/stable/c/5f57843565131bb782388f9d993f9ee8f453dee1
- https://git.kernel.org/stable/c/5fd4ffa2372a41361d2bdd27ea5730e4e673240c
- https://git.kernel.org/stable/c/75fbd370a2cec9e92f48285bd90735ed0c837f52
- https://git.kernel.org/stable/c/7a6ccc8fa192fd357c2d5d4c6ce67c834a179e23
- https://git.kernel.org/stable/c/bcbdc26a44aba488d2f7122f2d66801bccb74733
- https://git.kernel.org/stable/c/bf30b9ba09b0ac2a10f04dce2b0835ec4d178aa6
- https://git.kernel.org/stable/c/ce839b9331c11780470f3d727b6fe3c2794a4620
- https://git.kernel.org/stable/c/d17f744e883b2f8d13cca252d71cfe8ace346f7d
Modified: 2025-11-19
CVE-2022-50213
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: do not allow SET_ID to refer to another table When doing lookups for sets on the same batch by using its ID, a set from a different table can be used. Then, when the table is removed, a reference to the set may be kept after the set is freed, leading to a potential use-after-free. When looking for sets by ID, use the table that was used for the lookup by name, and only return sets belonging to that same table. This fixes CVE-2022-2586, also reported as ZDI-CAN-17470.
- https://git.kernel.org/stable/c/0d07039397527361850c554c192e749cfc879ea9
- https://git.kernel.org/stable/c/1a4b18b1ff11ba26f9a852019d674fde9d1d1cff
- https://git.kernel.org/stable/c/470ee20e069a6d05ae549f7d0ef2bdbcee6a81b2
- https://git.kernel.org/stable/c/77d3b5038b7462318f5183e2ad704b01d57215a2
- https://git.kernel.org/stable/c/f4fa03410f7c5f5bd8f90e9c11e9a8c4b526ff6f
- https://git.kernel.org/stable/c/faafd9286f1355c76fe9ac3021c280297213330e
- https://git.kernel.org/stable/c/fab2f61cc3b0e441b1749f017cfee75f9bbaded7
Modified: 2025-11-19
CVE-2022-50214
In the Linux kernel, the following vulnerability has been resolved: coresight: Clear the connection field properly coresight devices track their connections (output connections) and hold a reference to the fwnode. When a device goes away, we walk through the devices on the coresight bus and make sure that the references are dropped. This happens both ways: a) For all output connections from the device, drop the reference to the target device via coresight_release_platform_data() b) Iterate over all the devices on the coresight bus and drop the reference to fwnode if *this* device is the target of the output connection, via coresight_remove_conns()->coresight_remove_match(). However, the coresight_remove_match() doesn't clear the fwnode field, after dropping the reference, this causes use-after-free and additional refcount drops on the fwnode. e.g., if we have two devices, A and B, with a connection, A -> B. If we remove B first, B would clear the reference on B, from A via coresight_remove_match(). But when A is removed, it still has a connection with fwnode still pointing to B. Thus it tries to drops the reference in coresight_release_platform_data(), raising the bells like : [ 91.990153] ------------[ cut here ]------------ [ 91.990163] refcount_t: addition on 0; use-after-free. [ 91.990212] WARNING: CPU: 0 PID: 461 at lib/refcount.c:25 refcount_warn_saturate+0xa0/0x144 [ 91.990260] Modules linked in: coresight_funnel coresight_replicator coresight_etm4x(-) crct10dif_ce coresight ip_tables x_tables ipv6 [last unloaded: coresight_cpu_debug] [ 91.990398] CPU: 0 PID: 461 Comm: rmmod Tainted: G W T 5.19.0-rc2+ #53 [ 91.990418] Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform, BIOS EDK II Feb 1 2019 [ 91.990434] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 91.990454] pc : refcount_warn_saturate+0xa0/0x144 [ 91.990476] lr : refcount_warn_saturate+0xa0/0x144 [ 91.990496] sp : ffff80000c843640 [ 91.990509] x29: ffff80000c843640 x28: ffff800009957c28 x27: ffff80000c8439a8 [ 91.990560] x26: ffff00097eff1990 x25: ffff8000092b6ad8 x24: ffff00097eff19a8 [ 91.990610] x23: ffff80000c8439a8 x22: 0000000000000000 x21: ffff80000c8439c2 [ 91.990659] x20: 0000000000000000 x19: ffff00097eff1a10 x18: ffff80000ab99c40 [ 91.990708] x17: 0000000000000000 x16: 0000000000000000 x15: ffff80000abf6fa0 [ 91.990756] x14: 000000000000001d x13: 0a2e656572662d72 x12: 657466612d657375 [ 91.990805] x11: 203b30206e6f206e x10: 6f69746964646120 x9 : ffff8000081aba28 [ 91.990854] x8 : 206e6f206e6f6974 x7 : 69646461203a745f x6 : 746e756f63666572 [ 91.990903] x5 : ffff00097648ec58 x4 : 0000000000000000 x3 : 0000000000000027 [ 91.990952] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00080260ba00 [ 91.991000] Call trace: [ 91.991012] refcount_warn_saturate+0xa0/0x144 [ 91.991034] kobject_get+0xac/0xb0 [ 91.991055] of_node_get+0x2c/0x40 [ 91.991076] of_fwnode_get+0x40/0x60 [ 91.991094] fwnode_handle_get+0x3c/0x60 [ 91.991116] fwnode_get_nth_parent+0xf4/0x110 [ 91.991137] fwnode_full_name_string+0x48/0xc0 [ 91.991158] device_node_string+0x41c/0x530 [ 91.991178] pointer+0x320/0x3ec [ 91.991198] vsnprintf+0x23c/0x750 [ 91.991217] vprintk_store+0x104/0x4b0 [ 91.991238] vprintk_emit+0x8c/0x360 [ 91.991257] vprintk_default+0x44/0x50 [ 91.991276] vprintk+0xcc/0xf0 [ 91.991295] _printk+0x68/0x90 [ 91.991315] of_node_release+0x13c/0x14c [ 91.991334] kobject_put+0x98/0x114 [ 91.991354] of_node_put+0x24/0x34 [ 91.991372] of_fwnode_put+0x40/0x5c [ 91.991390] fwnode_handle_put+0x38/0x50 [ 91.991411] coresight_release_platform_data+0x74/0xb0 [coresight] [ 91.991472] coresight_unregister+0x64/0xcc [coresight] [ 91.991525] etm4_remove_dev+0x64/0x78 [coresight_etm4x] [ 91.991563] etm4_remove_amba+0x1c/0x2c [coresight_etm4x] [ 91.991598] amba_remove+0x3c/0x19c ---truncated---
- https://git.kernel.org/stable/c/2af89ebacf299b7fba5f3087d35e8a286ec33706
- https://git.kernel.org/stable/c/847b9273dd61567fb77617eabc5fa002594db062
- https://git.kernel.org/stable/c/b49b29ee113a87997bcca0bb0585bb46582846c1
- https://git.kernel.org/stable/c/bc57850fcb7e4cb91b6321d0ce83357cefd55c54
- https://git.kernel.org/stable/c/d43e967963c4d1b2b49f894d2f1b12865f87b098
- https://git.kernel.org/stable/c/e9205d8dd1cafb7cff689ef9ddf06276a68f54a4
Modified: 2025-11-19
CVE-2022-50215
In the Linux kernel, the following vulnerability has been resolved: scsi: sg: Allow waiting for commands to complete on removed device When a SCSI device is removed while in active use, currently sg will immediately return -ENODEV on any attempt to wait for active commands that were sent before the removal. This is problematic for commands that use SG_FLAG_DIRECT_IO since the data buffer may still be in use by the kernel when userspace frees or reuses it after getting ENODEV, leading to corrupted userspace memory (in the case of READ-type commands) or corrupted data being sent to the device (in the case of WRITE-type commands). This has been seen in practice when logging out of a iscsi_tcp session, where the iSCSI driver may still be processing commands after the device has been marked for removal. Change the policy to allow userspace to wait for active sg commands even when the device is being removed. Return -ENODEV only when there are no more responses to read.
- https://git.kernel.org/stable/c/03d8241112d5e3cccce1a01274a221099f07d2e1
- https://git.kernel.org/stable/c/3455607fd7be10b449f5135c00dc306b85dc0d21
- https://git.kernel.org/stable/c/35e60ec39e862159cb92923eefd5230d4a873cb9
- https://git.kernel.org/stable/c/408bfa1489a3cfe7150b81ab0b0df99b23dd5411
- https://git.kernel.org/stable/c/8c004b7dbb340c1e5889f5fb9e5baa6f6e5303e8
- https://git.kernel.org/stable/c/bbc118acf7baf9e93c5e1314d14f481301af4d0f
- https://git.kernel.org/stable/c/ed9afd967cbfe7da2dc0d5e52c62a778dfe9f16b
- https://git.kernel.org/stable/c/f135c65085eed869d10e4e7923ce1015288618da
- https://git.kernel.org/stable/c/f5e61d9b4a699dd16f32d5f39eb1cf98d84c92ed
Modified: 2025-11-19
CVE-2022-50218
In the Linux kernel, the following vulnerability has been resolved: iio: light: isl29028: Fix the warning in isl29028_remove() The driver use the non-managed form of the register function in isl29028_remove(). To keep the release order as mirroring the ordering in probe, the driver should use non-managed form in probe, too. The following log reveals it: [ 32.374955] isl29028 0-0010: remove [ 32.376861] general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] PREEMPT SMP KASAN PTI [ 32.377676] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037] [ 32.379432] RIP: 0010:kernfs_find_and_get_ns+0x28/0xe0 [ 32.385461] Call Trace: [ 32.385807] sysfs_unmerge_group+0x59/0x110 [ 32.386110] dpm_sysfs_remove+0x58/0xc0 [ 32.386391] device_del+0x296/0xe50 [ 32.386959] cdev_device_del+0x1d/0xd0 [ 32.387231] devm_iio_device_unreg+0x27/0xb0 [ 32.387542] devres_release_group+0x319/0x3d0 [ 32.388162] i2c_device_remove+0x93/0x1f0
- https://git.kernel.org/stable/c/06674fc7c003b9d0aa1d37fef7ab2c24802cc6ad
- https://git.kernel.org/stable/c/359f3b150eab30805fe0e4e9d616887d7257a625
- https://git.kernel.org/stable/c/4f0ebfb4b9bfad2326c0b2c3cc7e37f4b9ee9eba
- https://git.kernel.org/stable/c/a1135205b0affd255510775a27df571aca84ab4b
- https://git.kernel.org/stable/c/ca63d5abf404d2934e2ac03545350de7bb8c8e96
- https://git.kernel.org/stable/c/ed43fb20d3d1fca9d79db0d5faf4321a4dd58c23
- https://git.kernel.org/stable/c/fac589fb764699a4bcd288f6656b8cd0408ea968
- https://git.kernel.org/stable/c/fb1888205c0782f287e5dd4ffff1f665332e868c
Modified: 2025-11-19
CVE-2022-50220
In the Linux kernel, the following vulnerability has been resolved: usbnet: Fix linkwatch use-after-free on disconnect usbnet uses the work usbnet_deferred_kevent() to perform tasks which may sleep. On disconnect, completion of the work was originally awaited in ->ndo_stop(). But in 2003, that was moved to ->disconnect() by historic commit "[PATCH] USB: usbnet, prevent exotic rtnl deadlock": https://git.kernel.org/tglx/history/c/0f138bbfd83c The change was made because back then, the kernel's workqueue implementation did not allow waiting for a single work. One had to wait for completion of *all* work by calling flush_scheduled_work(), and that could deadlock when waiting for usbnet_deferred_kevent() with rtnl_mutex held in ->ndo_stop(). The commit solved one problem but created another: It causes a use-after-free in USB Ethernet drivers aqc111.c, asix_devices.c, ax88179_178a.c, ch9200.c and smsc75xx.c: * If the drivers receive a link change interrupt immediately before disconnect, they raise EVENT_LINK_RESET in their (non-sleepable) ->status() callback and schedule usbnet_deferred_kevent(). * usbnet_deferred_kevent() invokes the driver's ->link_reset() callback, which calls netif_carrier_{on,off}(). * That in turn schedules the work linkwatch_event(). Because usbnet_deferred_kevent() is awaited after unregister_netdev(), netif_carrier_{on,off}() may operate on an unregistered netdev and linkwatch_event() may run after free_netdev(), causing a use-after-free. In 2010, usbnet was changed to only wait for a single instance of usbnet_deferred_kevent() instead of *all* work by commit 23f333a2bfaf ("drivers/net: don't use flush_scheduled_work()"). Unfortunately the commit neglected to move the wait back to ->ndo_stop(). Rectify that omission at long last.
- https://git.kernel.org/stable/c/135199a2edd459d2b123144efcd7f9bcd95128e4
- https://git.kernel.org/stable/c/635fd8953e4309b54ca6a81bed1d4a87668694f4
- https://git.kernel.org/stable/c/7f77dcbc030c2faa6d8e8a594985eeb34018409e
- https://git.kernel.org/stable/c/8b4588b8b00b299be16a35be67b331d8fdba03f3
- https://git.kernel.org/stable/c/a69e617e533edddf3fa3123149900f36e0a6dc74
- https://git.kernel.org/stable/c/d2d6b530d89b0a912148018027386aa049f0a309
- https://git.kernel.org/stable/c/d49bb8cf9bfaa06aa527eb30f1a52a071da2e32f
- https://git.kernel.org/stable/c/db3b738ae5f726204876f4303c49cfdf4311403f
- https://git.kernel.org/stable/c/e2a521a7dcc463c5017b4426ca0804e151faeff7
Modified: 2025-11-19
CVE-2022-50222
In the Linux kernel, the following vulnerability has been resolved:
tty: vt: initialize unicode screen buffer
syzbot reports kernel infoleak at vcs_read() [1], for buffer can be read
immediately after resize operation. Initialize buffer using kzalloc().
----------
#include
- https://git.kernel.org/stable/c/446f123aa6021e5f75a20789f05ff3f7ae51a42f
- https://git.kernel.org/stable/c/5c6c65681f39bf71bc72ed589dec3b8b20e75cac
- https://git.kernel.org/stable/c/777a462e1ae50a01fc4a871efa8e34d596a1e17d
- https://git.kernel.org/stable/c/af77c56aa35325daa2bc2bed5c2ebf169be61b86
- https://git.kernel.org/stable/c/cc9e874dace0c89ae535230c7da19b764746811e
- https://git.kernel.org/stable/c/e02fa87e572bb7d90dcdbce9c0f519f1eb992e96
- https://git.kernel.org/stable/c/e0ef23e9b0ad18b9fd3741b0f1ad2282e4a18def
Modified: 2025-11-19
CVE-2022-50228
In the Linux kernel, the following vulnerability has been resolved:
KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0
Don't BUG/WARN on interrupt injection due to GIF being cleared,
since it's trivial for userspace to force the situation via
KVM_SET_VCPU_EVENTS (even if having at least a WARN there would be correct
for KVM internally generated injections).
kernel BUG at arch/x86/kvm/svm/svm.c:3386!
invalid opcode: 0000 [#1] SMP
CPU: 15 PID: 926 Comm: smm_test Not tainted 5.17.0-rc3+ #264
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
RIP: 0010:svm_inject_irq+0xab/0xb0 [kvm_amd]
Code: <0f> 0b 0f 1f 00 0f 1f 44 00 00 80 3d ac b3 01 00 00 55 48 89 f5 53
RSP: 0018:ffffc90000b37d88 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff88810a234ac0 RCX: 0000000000000006
RDX: 0000000000000000 RSI: ffffc90000b37df7 RDI: ffff88810a234ac0
RBP: ffffc90000b37df7 R08: ffff88810a1fa410 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffff888109571000 R14: ffff88810a234ac0 R15: 0000000000000000
FS: 0000000001821380(0000) GS:ffff88846fdc0000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f74fc550008 CR3: 000000010a6fe000 CR4: 0000000000350ea0
Call Trace:
- https://git.kernel.org/stable/c/2c49adeb020995236e63722ef6d0bee14372f471
- https://git.kernel.org/stable/c/2eee1dba70f57148fc7f8252613bfae6bd4b04e3
- https://git.kernel.org/stable/c/3d4e2d884da6312df7c9b85fbf671de49204ead6
- https://git.kernel.org/stable/c/68e1313bb8809e8addcd9431f2bfea0e8ddbca80
- https://git.kernel.org/stable/c/6afe88fbb40eac3291a8728688d61fdc745d8008
- https://git.kernel.org/stable/c/6fcbab82ccbcde915644085f73d3487938bda42d
- https://git.kernel.org/stable/c/8bb683490278005b4caf61e22b0828a04d282e86
- https://git.kernel.org/stable/c/c3396c1c8b87510f2ac2a674948156577559d42d
- https://git.kernel.org/stable/c/f17c31c48e5cde9895a491d91c424eeeada3e134
Modified: 2025-11-19
CVE-2022-50229
In the Linux kernel, the following vulnerability has been resolved: ALSA: bcd2000: Fix a UAF bug on the error path of probing When the driver fails in snd_card_register() at probe time, it will free the 'bcd2k->midi_out_urb' before killing it, which may cause a UAF bug. The following log can reveal it: [ 50.727020] BUG: KASAN: use-after-free in bcd2000_input_complete+0x1f1/0x2e0 [snd_bcd2000] [ 50.727623] Read of size 8 at addr ffff88810fab0e88 by task swapper/4/0 [ 50.729530] Call Trace: [ 50.732899] bcd2000_input_complete+0x1f1/0x2e0 [snd_bcd2000] Fix this by adding usb_kill_urb() before usb_free_urb().
- https://git.kernel.org/stable/c/05e0bb8c3c4dde3e21b9c1cf9395afb04e8b24db
- https://git.kernel.org/stable/c/1d6a246cf97c380f2da76591f03019dd9c9599c3
- https://git.kernel.org/stable/c/348620464a5c127399ac09b266f494f393661952
- https://git.kernel.org/stable/c/4fc41f7ebb7efca282f1740ea934d16f33c1d109
- https://git.kernel.org/stable/c/5e7338f4dd92b2f8915a82abfa1dd3ad3464bea0
- https://git.kernel.org/stable/c/64ca7f50ad96c2c65ae390b954925a36eabe04aa
- https://git.kernel.org/stable/c/a718eba7e458e2f40531be3c6b6a0028ca7fcace
- https://git.kernel.org/stable/c/b0d4af0a4763ddc02344789ef2a281c494bc330d
- https://git.kernel.org/stable/c/ffb2759df7efbc00187bfd9d1072434a13a54139
Package kernel-image-un-def updated to version 5.10.139-alt1 for branch p9 in task 305950.
Closed vulnerabilities
Modified: 2025-01-29
BDU:2022-06616
Уязвимость функции devlink_param_set/devlink_param_get (net/core/devlink.c) компонента IPsec ядра операционной системы Linux, позволяющая нарушителю выполнить произвольный код
Modified: 2024-09-30
BDU:2023-04272
Уязвимость функции idt77252_exit() в модуле drivers/atm/idt77252.c сетевого драйвера ATM idt77252 операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-01522
Уязвимость функции raid5_end_write_request() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-01523
Уязвимость функций lpfc_debugfs_multixripools_write() и lpfc_debugfs_nvmestat_write() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02366
Уязвимость функции ext4_resize_fs() в модуле fs/ext4/resize.c файловой системы Ext4 ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-02576
Уязвимость функции cdns3_wa2_remove_old_request() в модуле drivers/usb/cdns3/cdns3-gadget.c драйвера устройств шины USB ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02580
Уязвимость функций iavf_init_asq() и iavf_init_arq() в модуле drivers/net/ethernet/intel/iavf/iavf_adminq.c драйвера сетевых адаптеров Ethernet Intel ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02582
Уязвимость функции early_init_devtree() в модуле arch/powerpc/kernel/prom.c поддержки платформы PowerPC ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02660
Уязвимость функции f2fs_new_node_page() в модуле fs/f2fs/node.c файловой системы F2FS ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02662
Уязвимость функции sun6i_dsi_setup_timings() в модуле drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c драйвера инфраструктуры прямого рендеринга (DRI) ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02663
Уязвимость функции sja1105_setup_devlink_regions() в модуле drivers/net/dsa/sja1105/sja1105_devlink.c драйвера коммутаторов семейства NXP SJA1105 ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02664
Уязвимость функции mv88e6060_setup_port() в модуле drivers/net/dsa/mv88e6060.c драйвера DSA ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-02791
Уязвимость функции meson_vpu_has_available_connectors() модуля drivers/gpu/drm/meson/meson_drv.c драйвера инфраструктуры прямого рендеринга (DRI) ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-02802
Уязвимость функции afu_allocate_irqs() модуля drivers/misc/cxl/irq.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03123
Уязвимость функции intel_eth_pci_remove() модуля drivers/net/ethernet/stmicro/stmmac/dwmac-intel.c драйвера сетевых адаптеров Ethernet STMicroelectronics ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03178
Уязвимость функций aq_nic_service_timer_cb() и aq_nic_get_stats() модуля drivers/net/ethernet/aquantia/atlantic/aq_nic.c драйвера сетевых адаптеров Ethernet с чипсетом aQuantia Atlantic ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-03374
Уязвимость функции soc_info() модуля drivers/tty/serial/ucc_uart.c драйвера консоли TTY на последовательном порте ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03401
Уязвимость функции netlink_policy_dump_add_policy() модуля net/netlink/policy.c поддержки интерфейса мониторинга сокетов NETLINK ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03403
Уязвимость функции ohci_hcd_ppc_of_probe() модуля drivers/usb/host/ohci-ppc-of.c драйвера устройств шины USB ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03474
Уязвимость функции aa_pivotroot() модуля security/apparmor/mount.c компонента обеспечения безопасности AppArmor ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-03482
Уязвимость функции handle_cap_grant() модуля fs/ceph/caps.c поддержки распределенной файловой системы Ceph ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04503
Уязвимость функции i740fb_decode_var() модуля drivers/video/fbdev/i740fb.c драйвера устройств кадрового буфера ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04505
Уязвимость функции octeon2_usb_clocks_start() модуля arch/mips/cavium-octeon/octeon-platform.c поддержки архитектуры MIPS ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04507
Уязвимость функции ep_io() модуля drivers/usb/gadget/legacy/inode.c драйвера гаджетов USB ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04508
Уязвимость функции clk_branch_wait() модуля drivers/clk/qcom/clk-branch.c драйвера контроллера тактовой частоты Samsung Exynos ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04509
Уязвимость функции usbhs_rza1_hardware_init() модуля drivers/usb/renesas_usbhs/rza.c драйвера устройств шины USB ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-04875
Уязвимость функции bgmac_dma_tx_add() модуля drivers/net/ethernet/broadcom/bgmac.c драйвера сетевых адаптеров Ethernet Broadcom ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-04897
Уязвимость функций get_phb_number() и pcibios_alloc_controller() модуля arch/powerpc/kernel/pci-common.c поддержки платформы PowerPC ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-05721
Уязвимость функции receive_mergeable() в модуле drivers/net/virtio_net.c драйвера сетевых устройств ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
Modified: 2024-11-21
CVE-2022-3625
A vulnerability was found in Linux Kernel. It has been classified as critical. This affects the function devlink_param_set/devlink_param_get of the file net/core/devlink.c of the component IPsec. The manipulation leads to use after free. It is recommended to apply a patch to fix this issue. The identifier VDB-211929 was assigned to this vulnerability.
- https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git/commit/?id=6b4db2e528f650c7fb712961aac36455468d5902
- https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html
- https://vuldb.com/?id.211929
- https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git/commit/?id=6b4db2e528f650c7fb712961aac36455468d5902
- https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html
- https://vuldb.com/?id.211929
Modified: 2024-11-21
CVE-2022-3635
A vulnerability, which was classified as critical, has been found in Linux Kernel. Affected by this issue is the function tst_timer of the file drivers/atm/idt77252.c of the component IPsec. The manipulation leads to use after free. It is recommended to apply a patch to fix this issue. VDB-211934 is the identifier assigned to this vulnerability.
- https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git/commit/?id=3f4093e2bf4673f218c0bf17d8362337c400e77b
- https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html
- https://vuldb.com/?id.211934
- https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git/commit/?id=3f4093e2bf4673f218c0bf17d8362337c400e77b
- https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html
- https://vuldb.com/?id.211934
Modified: 2025-11-14
CVE-2022-50010
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 / I740_RFREQ_FIX))); The following log can reveal it: divide error: 0000 [#1] PREEMPT SMP KASAN PTI RIP: 0010:i740_calc_vclk drivers/video/fbdev/i740fb.c:353 [inline] RIP: 0010:i740fb_decode_var drivers/video/fbdev/i740fb.c:646 [inline] RIP: 0010:i740fb_set_par+0x163f/0x3b70 drivers/video/fbdev/i740fb.c:742 Call Trace: fb_set_var+0x604/0xeb0 drivers/video/fbdev/core/fbmem.c:1034 do_fb_ioctl+0x234/0x670 drivers/video/fbdev/core/fbmem.c:1110 fb_ioctl+0xdd/0x130 drivers/video/fbdev/core/fbmem.c:1189 Fix this by checking the argument of i740_calc_vclk() first.
- https://git.kernel.org/stable/c/2b7f559152a33c55f51b569b22efbe5e24886798
- https://git.kernel.org/stable/c/40bf722f8064f50200b8c4f8946cd625b441dda9
- https://git.kernel.org/stable/c/4b20c61365140d432dee7da7aa294215e7b900d9
- https://git.kernel.org/stable/c/59cefb583c984c0da8cf21a4c57d26d5a20dff5c
- https://git.kernel.org/stable/c/656689cb03ada4650016c153346939a1c334b1ae
- https://git.kernel.org/stable/c/d2d375eb68b4b8de6ea7460483a26fa9de56b443
- https://git.kernel.org/stable/c/e740e787f06671455b59d1e498c9945f7b4e7b3b
- https://git.kernel.org/stable/c/f350812e2d15278f1d867eeb997407782234fb3c
Modified: 2025-12-23
CVE-2022-50012
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 static_key_enable_cpuslocked+0xfc/0x120 ... NIP static_key_enable_cpuslocked+0xfc/0x120 LR static_key_enable_cpuslocked+0xf8/0x120 Call Trace: static_key_enable_cpuslocked+0xf8/0x120 (unreliable) static_key_enable+0x30/0x50 setup_forced_irqthreads+0x28/0x40 do_early_param+0xa0/0x108 parse_args+0x290/0x4e0 parse_early_options+0x48/0x5c parse_early_param+0x58/0x84 early_init_devtree+0xd4/0x518 early_setup+0xb4/0x214 So call jump_label_init() just before parse_early_param() in early_init_devtree(). [mpe: Add call trace to change log and minor wording edits.]
Modified: 2025-11-14
CVE-2022-50013
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
- https://git.kernel.org/stable/c/141170b759e03958f296033bb7001be62d1d363b
- https://git.kernel.org/stable/c/29e734ec33ae4bd7de4018fb0fb0eec808c36b92
- https://git.kernel.org/stable/c/43ce0a0bda2c54dad91d5a1943554eed9e050f55
- https://git.kernel.org/stable/c/5a01e45b925a0bc9718eccd33e5920f1a4e44caf
- https://git.kernel.org/stable/c/800ba8979111184d5194f4233cc83afe683efc54
- https://git.kernel.org/stable/c/fbfad62b29e9f8f1c1026a806c9e064ec2a7c342
Modified: 2025-11-13
CVE-2022-50017
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.
- https://git.kernel.org/stable/c/1b49707df679b5510ed06ace7378ddc2aec5c3fb
- https://git.kernel.org/stable/c/1e39037e44d7fa3728686af146f9285ea197097d
- https://git.kernel.org/stable/c/7822d994eb9579a1df4cdbc315db090a041e50f3
- https://git.kernel.org/stable/c/7a9f743ceead60ed454c46fbc3085ee9a79cbebb
- https://git.kernel.org/stable/c/9d1afa0169a84dcd5b79901d792edeb8403684ab
- https://git.kernel.org/stable/c/a80016c40cc797c7f3e5a705b8e12ae447280335
- https://git.kernel.org/stable/c/af87a469695dc2b2419b2fdff0bf41db5265b325
- https://git.kernel.org/stable/c/c06166a484eece51916dd700a870e53356b7e1bc
Modified: 2025-11-13
CVE-2022-50019
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.
- https://git.kernel.org/stable/c/17c32546166d8a7d2579c4b57c8b16241f94a66b
- https://git.kernel.org/stable/c/59bc4c19d53bdac61ec952c01c6e864f5f0f8367
- https://git.kernel.org/stable/c/81939c4fbc2d5c754d0f1c1f05149d4b70d751ed
- https://git.kernel.org/stable/c/8245e7d1d7f75a9255ad1e8146752e5051d528b8
- https://git.kernel.org/stable/c/ca3fc1c38e4253bc019881301a28ea60b8b0bca3
- https://git.kernel.org/stable/c/d24d7bb2cd947676f9b71fb944d045e09b8b282f
- https://git.kernel.org/stable/c/ec56f886f3bf0f15f7a3844d4c025e165b8e8de7
- https://git.kernel.org/stable/c/f6ed634eedb1a8a6a8cb110a7695c7abb70ffcbf
Modified: 2025-12-23
CVE-2022-50020
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.
- https://git.kernel.org/stable/c/0082e99a9074ff88eff729c70c93454c8588d8e1
- https://git.kernel.org/stable/c/69cb8e9d8cd97cdf5e293b26d70a9dee3e35e6bd
- https://git.kernel.org/stable/c/72b850a2a996f72541172e7cf686d54a2b29bcd8
- https://git.kernel.org/stable/c/7bdfb01fc5f6b3696728aeb527c50386e0ee09a1
- https://git.kernel.org/stable/c/80288883294c5b4ed18bae0d8bd9c4a12f297074
- https://git.kernel.org/stable/c/a6805b3dcf5cd41f2ae3a03dca43411135b99849
Modified: 2025-11-13
CVE-2022-50022
In the Linux kernel, the following vulnerability has been resolved: drivers:md:fix a potential use-after-free bug In line 2884, "raid5_release_stripe(sh);" drops the reference to sh and may cause sh to be released. However, sh is subsequently used in lines 2886 "if (sh->batch_head && sh != sh->batch_head)". This may result in an use-after-free bug. It can be fixed by moving "raid5_release_stripe(sh);" to the bottom of the function.
- https://git.kernel.org/stable/c/09cf99bace7789d91caa8d10fbcfc8b2fb35857f
- https://git.kernel.org/stable/c/104212471b1c1817b311771d817fb692af983173
- https://git.kernel.org/stable/c/5d8325fd15892c8ab1146edc1d7ed8463de39636
- https://git.kernel.org/stable/c/7470a4314b239e9a9580f248fdf4c9a92805490e
- https://git.kernel.org/stable/c/d9b94c3ace549433de8a93eeb27b0391fc8ac406
- https://git.kernel.org/stable/c/e5b3dd2d92c4511e81f6e4ec9c5bb7ad25e03d13
- https://git.kernel.org/stable/c/eb3a4f73f43f839df981dda5859e8e075067a360
- https://git.kernel.org/stable/c/f5d46f1b47f65da1faf468277b261eb78c8e25b5
Modified: 2025-11-13
CVE-2022-50025
In the Linux kernel, the following vulnerability has been resolved: cxl: Fix a memory leak in an error handling path A bitmap_zalloc() must be balanced by a corresponding bitmap_free() in the error handling path of afu_allocate_irqs().
- https://git.kernel.org/stable/c/3a15b45b5454da862376b5d69a4967f5c6fa1368
- https://git.kernel.org/stable/c/4be138bcd6d68cec0ce47051b117541061f5141a
- https://git.kernel.org/stable/c/6544ff559315498ad6c0a311359ca44987f9ca07
- https://git.kernel.org/stable/c/695af60af755873399ce01cb97176768828bc1fd
- https://git.kernel.org/stable/c/89d51dc6878c47b6400922fac21b6a33f9d1a588
- https://git.kernel.org/stable/c/addff638c41753639368c252d0c5ba0d8fe9ed97
- https://git.kernel.org/stable/c/c2557780ee7818b701681c226fa4cb7c0b171665
- https://git.kernel.org/stable/c/c2c7a29f99788e9e5dfe41d16868ea33da7cc235
Modified: 2025-11-13
CVE-2022-50028
In the Linux kernel, the following vulnerability has been resolved: gadgetfs: ep_io - wait until IRQ finishes after usb_ep_queue() if wait_for_completion_interruptible() is interrupted we need to wait until IRQ gets finished. Otherwise complete() from epio_complete() can corrupt stack.
- https://git.kernel.org/stable/c/04cb742d4d8f30dc2e83b46ac317eec09191c68e
- https://git.kernel.org/stable/c/118d967ce00a3d128bf731b35e4e2cb0facf5f00
- https://git.kernel.org/stable/c/2b06d5d97c0e067108a122986767731d40742138
- https://git.kernel.org/stable/c/67a4874461422e633236a0286a01b483cd647113
- https://git.kernel.org/stable/c/77040efe59a141286d090c8a0d37c65a355a1832
- https://git.kernel.org/stable/c/94aadba8d000d5de56af4ce8da3f334f21bf7a79
- https://git.kernel.org/stable/c/9ac14f973cb91f0c01776517e6d50981f32b8038
- https://git.kernel.org/stable/c/ca06b4cde54f8ec8be3aa53fd339bd56e62c12b3
Modified: 2025-11-13
CVE-2022-50029
In the Linux kernel, the following vulnerability has been resolved: clk: qcom: ipq8074: dont disable gcc_sleep_clk_src Once the usb sleep clocks are disabled, clock framework is trying to disable the sleep clock source also. However, it seems that it cannot be disabled and trying to do so produces: [ 245.436390] ------------[ cut here ]------------ [ 245.441233] gcc_sleep_clk_src status stuck at 'on' [ 245.441254] WARNING: CPU: 2 PID: 223 at clk_branch_wait+0x130/0x140 [ 245.450435] Modules linked in: xhci_plat_hcd xhci_hcd dwc3 dwc3_qcom leds_gpio [ 245.456601] CPU: 2 PID: 223 Comm: sh Not tainted 5.18.0-rc4 #215 [ 245.463889] Hardware name: Xiaomi AX9000 (DT) [ 245.470050] pstate: 204000c5 (nzCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 245.474307] pc : clk_branch_wait+0x130/0x140 [ 245.481073] lr : clk_branch_wait+0x130/0x140 [ 245.485588] sp : ffffffc009f2bad0 [ 245.489838] x29: ffffffc009f2bad0 x28: ffffff8003e6c800 x27: 0000000000000000 [ 245.493057] x26: 0000000000000000 x25: 0000000000000000 x24: ffffff800226ef20 [ 245.500175] x23: ffffffc0089ff550 x22: 0000000000000000 x21: ffffffc008476ad0 [ 245.507294] x20: 0000000000000000 x19: ffffffc00965ac70 x18: fffffffffffc51a7 [ 245.514413] x17: 68702e3030303837 x16: 3a6d726f6674616c x15: ffffffc089f2b777 [ 245.521531] x14: ffffffc0095c9d18 x13: 0000000000000129 x12: 0000000000000129 [ 245.528649] x11: 00000000ffffffea x10: ffffffc009621d18 x9 : 0000000000000001 [ 245.535767] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 : 0000000000000001 [ 245.542885] x5 : ffffff803fdca6d8 x4 : 0000000000000000 x3 : 0000000000000027 [ 245.550002] x2 : 0000000000000027 x1 : 0000000000000023 x0 : 0000000000000026 [ 245.557122] Call trace: [ 245.564229] clk_branch_wait+0x130/0x140 [ 245.566490] clk_branch2_disable+0x2c/0x40 [ 245.570656] clk_core_disable+0x60/0xb0 [ 245.574561] clk_core_disable+0x68/0xb0 [ 245.578293] clk_disable+0x30/0x50 [ 245.582113] dwc3_qcom_remove+0x60/0xc0 [dwc3_qcom] [ 245.585588] platform_remove+0x28/0x60 [ 245.590361] device_remove+0x4c/0x80 [ 245.594179] device_release_driver_internal+0x1dc/0x230 [ 245.597914] device_driver_detach+0x18/0x30 [ 245.602861] unbind_store+0xec/0x110 [ 245.607027] drv_attr_store+0x24/0x40 [ 245.610847] sysfs_kf_write+0x44/0x60 [ 245.614405] kernfs_fop_write_iter+0x128/0x1c0 [ 245.618052] new_sync_write+0xc0/0x130 [ 245.622391] vfs_write+0x1d4/0x2a0 [ 245.626123] ksys_write+0x58/0xe0 [ 245.629508] __arm64_sys_write+0x1c/0x30 [ 245.632895] invoke_syscall.constprop.0+0x5c/0x110 [ 245.636890] do_el0_svc+0xa0/0x150 [ 245.641488] el0_svc+0x18/0x60 [ 245.644872] el0t_64_sync_handler+0xa4/0x130 [ 245.647914] el0t_64_sync+0x174/0x178 [ 245.652340] ---[ end trace 0000000000000000 ]--- So, add CLK_IS_CRITICAL flag to the clock so that the kernel won't try to disable the sleep clock.
- https://git.kernel.org/stable/c/17d58499dc9c7e059dab7d170e9bae1e7e9c561b
- https://git.kernel.org/stable/c/1bf7305e79aab095196131bdc87a97796e0e3fac
- https://git.kernel.org/stable/c/38cee0d2b65eed42a44052de1bfdc0177b6c3f05
- https://git.kernel.org/stable/c/4203b76abe539f3cac258d4cf1e16e2dd95ea60f
- https://git.kernel.org/stable/c/459411b9f0180e3f382d7abfa3028dd3285984c3
- https://git.kernel.org/stable/c/6b90ab952401bd6c1a321dcfc0e0df080f2bc905
- https://git.kernel.org/stable/c/d401611a93b332914cf91eb9bc0b63fa1bdc17e9
Modified: 2025-11-13
CVE-2022-50030
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input Malformed user input to debugfs results in buffer overflow crashes. Adapt input string lengths to fit within internal buffers, leaving space for NULL terminators.
- https://git.kernel.org/stable/c/2d544e9d19c109dfe34b3dc1253a8b2971abe060
- https://git.kernel.org/stable/c/927907f1cbb3408cadde637fccfc17bb6b10a87d
- https://git.kernel.org/stable/c/b92506dc51f81741eb26609175ac206c20f06e0a
- https://git.kernel.org/stable/c/c29a4baaad38a332c0ae480cf6d6c5bf75ac1828
- https://git.kernel.org/stable/c/f8191d40aa612981ce897e66cda6a88db8df17bb
Modified: 2025-11-13
CVE-2022-50032
In the Linux kernel, the following vulnerability has been resolved: usb: renesas: Fix refcount leak bug In usbhs_rza1_hardware_init(), 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.
- https://git.kernel.org/stable/c/36b18b777dece704b7c2e9e7947ca41a9b0fb009
- https://git.kernel.org/stable/c/5c4b699193eba51f1bbf462d758d66f545fddd35
- https://git.kernel.org/stable/c/9790a5a4f07f38a5add85ec58c44797d3a7c3677
- https://git.kernel.org/stable/c/9d6d5303c39b8bc182475b22f45504106a07f086
- https://git.kernel.org/stable/c/cfa8f707a58d68b2341a9dd0b33cf048f0628b4d
- https://git.kernel.org/stable/c/fbdbd61a36d887e00114321c6758e359e9573a8e
Modified: 2025-11-13
CVE-2022-50033
In the Linux kernel, the following vulnerability has been resolved: usb: host: ohci-ppc-of: Fix refcount leak bug In ohci_hcd_ppc_of_probe(), of_find_compatible_node() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.
- https://git.kernel.org/stable/c/0334d23c56ecf1ee1563bb83e29cc5a51ed7fb4e
- https://git.kernel.org/stable/c/0fc62bbc95319bbd330e3645afc7c286acec9ef8
- https://git.kernel.org/stable/c/403132881e66db7aa98b55c6655daedd80d407fd
- https://git.kernel.org/stable/c/40a959d7042bb7711e404ad2318b30e9f92c6b9b
- https://git.kernel.org/stable/c/c5c5bd5cdcc6dc9f75f53d1c89af463d39a2bb96
- https://git.kernel.org/stable/c/cb5dd65e889163e723df1c2f02288cc527a57785
- https://git.kernel.org/stable/c/ec583e300aee9f152a64911445092d18e1c36729
- https://git.kernel.org/stable/c/fe6fe64403710287f0ae61a516954d8a4f7c9e3f
Modified: 2025-11-13
CVE-2022-50034
In the Linux kernel, the following vulnerability has been resolved: usb: cdns3 fix use-after-free at workaround 2 BUG: KFENCE: use-after-free read in __list_del_entry_valid+0x10/0xac cdns3_wa2_remove_old_request() { ... kfree(priv_req->request.buf); cdns3_gadget_ep_free_request(&priv_ep->endpoint, &priv_req->request); list_del_init(&priv_req->list); ^^^ use after free ... } cdns3_gadget_ep_free_request() free the space pointed by priv_req, but priv_req is used in the following list_del_init(). This patch move list_del_init() before cdns3_gadget_ep_free_request().
- https://git.kernel.org/stable/c/6d7ac60098b206d0472475b666cb09d556bec03d
- https://git.kernel.org/stable/c/6fd50446e7c9a98b4bcf96815f5c9602a16ea472
- https://git.kernel.org/stable/c/7d602f30149a117eea260208b1661bc404c21dfd
- https://git.kernel.org/stable/c/c3c1dbad3a2db32ecf371c97f2058491b8ba0f9a
- https://git.kernel.org/stable/c/e65d9b7147d7be3504893ca7dfb85286bda83d40
Modified: 2025-11-13
CVE-2022-50036
In the Linux kernel, the following vulnerability has been resolved: drm/sun4i: dsi: Prevent underflow when computing packet sizes Currently, the packet overhead is subtracted using unsigned arithmetic. With a short sync pulse, this could underflow and wrap around to near the maximal u16 value. Fix this by using signed subtraction. The call to max() will correctly handle any negative numbers that are produced. Apply the same fix to the other timings, even though those subtractions are less likely to underflow.
Modified: 2025-11-13
CVE-2022-50038
In the Linux kernel, the following vulnerability has been resolved: drm/meson: Fix refcount bugs in meson_vpu_has_available_connectors() In this function, there are two refcount leak bugs: (1) when breaking out of for_each_endpoint_of_node(), we need call the of_node_put() for the 'ep'; (2) we should call of_node_put() for the reference returned by of_graph_get_remote_port() when it is not used anymore.
- https://git.kernel.org/stable/c/3aa710e96747c8b4e52ba12ffe09edcb2755897c
- https://git.kernel.org/stable/c/6a758f0ba11699837af9e1a0f7cbac6ef765a23e
- https://git.kernel.org/stable/c/8dec38e19f6928235d4009ce55f7add8af34e5c7
- https://git.kernel.org/stable/c/91b3c8dbe898df158fd2a84675f3a284ff6666f7
- https://git.kernel.org/stable/c/d58ef256781398ad115aef44de0a02ad27ea6c3a
- https://git.kernel.org/stable/c/fc1fc2abfcb9235d0ece9a4d858426fb617cfa66
- https://git.kernel.org/stable/c/fe71d84c1a6c0d54657431e8eeaefc9d24895304
Modified: 2025-11-13
CVE-2022-50039
In the Linux kernel, the following vulnerability has been resolved: stmmac: intel: Add a missing clk_disable_unprepare() call in intel_eth_pci_remove() Commit 09f012e64e4b ("stmmac: intel: Fix clock handling on error and remove paths") removed this clk_disable_unprepare() This was partly revert by commit ac322f86b56c ("net: stmmac: Fix clock handling on remove path") which removed this clk_disable_unprepare() because: " While unloading the dwmac-intel driver, clk_disable_unprepare() is being called twice in stmmac_dvr_remove() and intel_eth_pci_remove(). This causes kernel panic on the second call. " However later on, commit 5ec55823438e8 ("net: stmmac: add clocks management for gmac driver") has updated stmmac_dvr_remove() which do not call clk_disable_unprepare() anymore. So this call should now be called from intel_eth_pci_remove().
Modified: 2025-11-13
CVE-2022-50040
In the Linux kernel, the following vulnerability has been resolved: net: dsa: sja1105: fix buffer overflow in sja1105_setup_devlink_regions() If an error occurs in dsa_devlink_region_create(), then 'priv->regions' array will be accessed by negative index '-1'. Found by Linux Verification Center (linuxtesting.org) with SVACE.
Modified: 2025-11-13
CVE-2022-50042
In the Linux kernel, the following vulnerability has been resolved: net: genl: fix error path memory leak in policy dumping If construction of the array of policies fails when recording non-first policy we need to unwind. netlink_policy_dump_add_policy() itself also needs fixing as it currently gives up on error without recording the allocated pointer in the pstate pointer.
Modified: 2025-11-13
CVE-2022-50045
In the Linux kernel, the following vulnerability has been resolved: powerpc/pci: Fix get_phb_number() locking The recent change to get_phb_number() causes a DEBUG_ATOMIC_SLEEP warning on some systems: BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper preempt_count: 1, expected: 0 RCU nest depth: 0, expected: 0 1 lock held by swapper/1: #0: c157efb0 (hose_spinlock){+.+.}-{2:2}, at: pcibios_alloc_controller+0x64/0x220 Preemption disabled at: [<00000000>] 0x0 CPU: 0 PID: 1 Comm: swapper Not tainted 5.19.0-yocto-standard+ #1 Call Trace: [d101dc90] [c073b264] dump_stack_lvl+0x50/0x8c (unreliable) [d101dcb0] [c0093b70] __might_resched+0x258/0x2a8 [d101dcd0] [c0d3e634] __mutex_lock+0x6c/0x6ec [d101dd50] [c0a84174] of_alias_get_id+0x50/0xf4 [d101dd80] [c002ec78] pcibios_alloc_controller+0x1b8/0x220 [d101ddd0] [c140c9dc] pmac_pci_init+0x198/0x784 [d101de50] [c140852c] discover_phbs+0x30/0x4c [d101de60] [c0007fd4] do_one_initcall+0x94/0x344 [d101ded0] [c1403b40] kernel_init_freeable+0x1a8/0x22c [d101df10] [c00086e0] kernel_init+0x34/0x160 [d101df30] [c001b334] ret_from_kernel_thread+0x5c/0x64 This is because pcibios_alloc_controller() holds hose_spinlock but of_alias_get_id() takes of_mutex which can sleep. The hose_spinlock protects the phb_bitmap, and also the hose_list, but it doesn't need to be held while get_phb_number() calls the OF routines, because those are only looking up information in the device tree. So fix it by having get_phb_number() take the hose_spinlock itself, only where required, and then dropping the lock before returning. pcibios_alloc_controller() then needs to take the lock again before the list_add() but that's safe, the order of the list is not important.
- https://git.kernel.org/stable/c/1d9e75c3d8cdf7c96a94cb77450d4ee070279e6a
- https://git.kernel.org/stable/c/5db5ce0f1963c6c8275719a80cb65e9c98d32726
- https://git.kernel.org/stable/c/6f75057c21eab12c6ccb7f06f859641a6edfab99
- https://git.kernel.org/stable/c/8d48562a2729742f767b0fdd994d6b2a56a49c63
- https://git.kernel.org/stable/c/90f195c01a2e8d8da6281791617e21109719c981
- https://git.kernel.org/stable/c/a868f771ee41c97a25a04b8c632a7f06689b307b
- https://git.kernel.org/stable/c/ccb0a42d3f40c436295e0fef57ab613ae5b925a4
Modified: 2025-11-13
CVE-2022-50047
In the Linux kernel, the following vulnerability has been resolved: net: dsa: mv88e6060: prevent crash on an unused port If the port isn't a CPU port nor a user port, 'cpu_dp' is a null pointer and a crash happened on dereferencing it in mv88e6060_setup_port(): [ 9.575872] Unable to handle kernel NULL pointer dereference at virtual address 00000014 ... [ 9.942216] mv88e6060_setup from dsa_register_switch+0x814/0xe84 [ 9.948616] dsa_register_switch from mdio_probe+0x2c/0x54 [ 9.954433] mdio_probe from really_probe.part.0+0x98/0x2a0 [ 9.960375] really_probe.part.0 from driver_probe_device+0x30/0x10c [ 9.967029] driver_probe_device from __device_attach_driver+0xb8/0x13c [ 9.973946] __device_attach_driver from bus_for_each_drv+0x90/0xe0 [ 9.980509] bus_for_each_drv from __device_attach+0x110/0x184 [ 9.986632] __device_attach from bus_probe_device+0x8c/0x94 [ 9.992577] bus_probe_device from deferred_probe_work_func+0x78/0xa8 [ 9.999311] deferred_probe_work_func from process_one_work+0x290/0x73c [ 10.006292] process_one_work from worker_thread+0x30/0x4b8 [ 10.012155] worker_thread from kthread+0xd4/0x10c [ 10.017238] kthread from ret_from_fork+0x14/0x3c
- https://git.kernel.org/stable/c/246bbf2f977ea36aaf41f5d24370fef433250728
- https://git.kernel.org/stable/c/92dc64e8f591425ce4dabf7d479ebf6e67fb8853
- https://git.kernel.org/stable/c/cb1753bc689c7a7f94da6eee7efc1ae6d8abb36c
- https://git.kernel.org/stable/c/dd236b62d25e44ecfa26b0910a12f8d8251aff00
- https://git.kernel.org/stable/c/f3a4b55829617cad2d36fa6524367ef629566ba6
Modified: 2025-11-13
CVE-2022-50055
In the Linux kernel, the following vulnerability has been resolved: iavf: Fix adminq error handling iavf_alloc_asq_bufs/iavf_alloc_arq_bufs allocates with dma_alloc_coherent memory for VF mailbox. Free DMA regions for both ASQ and ARQ in case error happens during configuration of ASQ/ARQ registers. Without this change it is possible to see when unloading interface: 74626.583369: dma_debug_device_change: device driver has pending DMA allocations while released from device [count=32] One of leaked entries details: [device address=0x0000000b27ff9000] [size=4096 bytes] [mapped with DMA_BIDIRECTIONAL] [mapped as coherent]
- https://git.kernel.org/stable/c/35c63581fdefdcbaeae8cded18908523252353ad
- https://git.kernel.org/stable/c/419831617ed349992c84344dbd9e627f9e68f842
- https://git.kernel.org/stable/c/4fe80492d53971d9a49f39f3c86d2d67c6f3638a
- https://git.kernel.org/stable/c/dab6b551f5ba4c79a0dd4970dd8533c37a7b100f
- https://git.kernel.org/stable/c/ff289f2be5899efd0e897d2b434a78e36df2c69b
Modified: 2025-11-13
CVE-2022-50059
In the Linux kernel, the following vulnerability has been resolved: ceph: don't leak snap_rwsem in handle_cap_grant When handle_cap_grant is called on an IMPORT op, then the snap_rwsem is held and the function is expected to release it before returning. It currently fails to do that in all cases which could lead to a deadlock.
Modified: 2025-11-13
CVE-2022-50061
In the Linux kernel, the following vulnerability has been resolved: pinctrl: nomadik: Fix refcount leak in nmk_pinctrl_dt_subnode_to_map 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."
- https://git.kernel.org/stable/c/4b32e054335ea0ce50967f63a7bfd4db058b14b9
- https://git.kernel.org/stable/c/587ac8ac00a1a9f4572785229d9441870fd7b187
- https://git.kernel.org/stable/c/78d05103891d3e96144b846fbc39f2cfb3384eae
- https://git.kernel.org/stable/c/81abaab5a4b815c0ed9f4d2c9745777ac5cc395b
- https://git.kernel.org/stable/c/9272265f2f76629e1a67e6d49b3a4461b3da1a73
- https://git.kernel.org/stable/c/c26012a1e61c7bbd1b393d3bbae8dffdb6df65bb
- https://git.kernel.org/stable/c/c35f89a9021fa947ecede0584ae509368a52ec5a
- https://git.kernel.org/stable/c/f498542bc703bf1e5c6a1610e1ea493a437f0196
Modified: 2025-11-13
CVE-2022-50062
In the Linux kernel, the following vulnerability has been resolved:
net: bgmac: Fix a BUG triggered by wrong bytes_compl
On one of our machines we got:
kernel BUG at lib/dynamic_queue_limits.c:27!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
CPU: 0 PID: 1166 Comm: irq/41-bgmac Tainted: G W O 4.14.275-rt132 #1
Hardware name: BRCM XGS iProc
task: ee3415c0 task.stack: ee32a000
PC is at dql_completed+0x168/0x178
LR is at bgmac_poll+0x18c/0x6d8
pc : [
- https://git.kernel.org/stable/c/1b7680c6c1f6de9904f1d9b05c952f0c64a03350
- https://git.kernel.org/stable/c/ab2b55bb25db289ba0b68e3d58494476bdb1041d
- https://git.kernel.org/stable/c/ac6d4482f29ab992b605c1b4bd1347f1f679f4e4
- https://git.kernel.org/stable/c/c506c9a97120f43257e9b3ce7b1f9a24eafc3787
- https://git.kernel.org/stable/c/da1421a29d3b8681ba6a7f686bd0b40dda5acaf3
Modified: 2025-11-17
CVE-2022-50065
In the Linux kernel, the following vulnerability has been resolved: virtio_net: fix memory leak inside XPD_TX with mergeable When we call xdp_convert_buff_to_frame() to get xdpf, if it returns NULL, we should check if xdp_page was allocated by xdp_linearize_page(). If it is newly allocated, it should be freed here alone. Just like any other "goto err_xdp".
Modified: 2025-11-17
CVE-2022-50066
In the Linux kernel, the following vulnerability has been resolved:
net: atlantic: fix aq_vec index out of range error
The final update statement of the for loop exceeds the array range, the
dereference of self->aq_vec[i] is not checked and then leads to the
index out of range error.
Also fixed this kind of coding style in other for loop.
[ 97.937604] UBSAN: array-index-out-of-bounds in drivers/net/ethernet/aquantia/atlantic/aq_nic.c:1404:48
[ 97.937607] index 8 is out of range for type 'aq_vec_s *[8]'
[ 97.937608] CPU: 38 PID: 3767 Comm: kworker/u256:18 Not tainted 5.19.0+ #2
[ 97.937610] Hardware name: Dell Inc. Precision 7865 Tower/, BIOS 1.0.0 06/12/2022
[ 97.937611] Workqueue: events_unbound async_run_entry_fn
[ 97.937616] Call Trace:
[ 97.937617]
Modified: 2025-11-17
CVE-2022-50072
In the Linux kernel, the following vulnerability has been resolved: NFSv4/pnfs: Fix a use-after-free bug in open If someone cancels the open RPC call, then we must not try to free either the open slot or the layoutget operation arguments, since they are likely still in use by the hung RPC call.
- https://git.kernel.org/stable/c/0fffb46ff3d5ed4668aca96441ec7a25b793bd6f
- https://git.kernel.org/stable/c/2135e5d56278ffdb1c2e6d325dc6b87f669b9dac
- https://git.kernel.org/stable/c/76ffd2042438769298f34b76102b40dea89de616
- https://git.kernel.org/stable/c/a4cf3dadd1fa43609f7c6570c9116b0e0a9923d1
- https://git.kernel.org/stable/c/b03d1117e9be7c7da60e466eaf9beed85c5916c8
- https://git.kernel.org/stable/c/f7ee3b772d9de87387a725caa04bc041ac7fe5ec
Modified: 2025-11-17
CVE-2022-50074
In the Linux kernel, the following vulnerability has been resolved: apparmor: Fix memleak in aa_simple_write_to_buffer() When copy_from_user failed, the memory is freed by kvfree. however the management struct and data blob are allocated independently, so only kvfree(data) cause a memleak issue here. Use aa_put_loaddata(data) to fix this issue.
- https://git.kernel.org/stable/c/417ea9fe972d2654a268ad66e89c8fcae67017c3
- https://git.kernel.org/stable/c/6500eb3a48ac221051b1791818a1ac74744ef617
- https://git.kernel.org/stable/c/6583edbf459de2e06b9759f264c0ae27e452b97a
- https://git.kernel.org/stable/c/7db182a2ebeefded86fea542fcc5d6a68bb77f58
- https://git.kernel.org/stable/c/8aab4295582eb397a125d2788b829fa62b88dbf7
- https://git.kernel.org/stable/c/bf7ebebce2c25071c719fd8a2f1307e0c243c2d7
Modified: 2025-11-17
CVE-2022-50077
In the Linux kernel, the following vulnerability has been resolved: apparmor: fix reference count leak in aa_pivotroot() The aa_pivotroot() function has a reference counting bug in a specific path. When aa_replace_current_label() returns on success, the function forgets to decrement the reference count of “target”, which is increased earlier by build_pivotroot(), causing a reference leak. Fix it by decreasing the refcount of “target” in that path.
- https://git.kernel.org/stable/c/11c3627ec6b56c1525013f336f41b79a983b4d46
- https://git.kernel.org/stable/c/2ceeb3296e9dde1d5772348046affcefdea605e2
- https://git.kernel.org/stable/c/3ca40ad7afae144169a43988ef1a3f16182faf0a
- https://git.kernel.org/stable/c/64103ea357734b82384c925cba4758fdb909be0c
- https://git.kernel.org/stable/c/d53194707d2a1851be027cd74266b96ceff799d3
- https://git.kernel.org/stable/c/ef6fb6f0d0d8440595b45a7e53c6162c737177f4
- https://git.kernel.org/stable/c/f4d5c7796571624e3f380b447ada52834270a287
Modified: 2025-11-19
CVE-2022-50219
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix KASAN use-after-free Read in compute_effective_progs Syzbot found a Use After Free bug in compute_effective_progs(). The reproducer creates a number of BPF links, and causes a fault injected alloc to fail, while calling bpf_link_detach on them. Link detach triggers the link to be freed by bpf_link_free(), which calls __cgroup_bpf_detach() and update_effective_progs(). If the memory allocation in this function fails, the function restores the pointer to the bpf_cgroup_link on the cgroup list, but the memory gets freed just after it returns. After this, every subsequent call to update_effective_progs() causes this already deallocated pointer to be dereferenced in prog_list_length(), and triggers KASAN UAF error. To fix this issue don't preserve the pointer to the prog or link in the list, but remove it and replace it with a dummy prog without shrinking the table. The subsequent call to __cgroup_bpf_detach() or __cgroup_bpf_detach() will correct it.
- https://git.kernel.org/stable/c/1f8ca9c40e6222ce431e9ba5dae3cccce8ef9443
- https://git.kernel.org/stable/c/3527e3cbb84d8868c4d4e91ba55915f96d39ec3d
- https://git.kernel.org/stable/c/4c46091ee985ae84c60c5e95055d779fcd291d87
- https://git.kernel.org/stable/c/6336388715afa419cc97d0255bda3bba1b96b7ca
- https://git.kernel.org/stable/c/be001f9da71eaa3b61e186fb88bde3279728bdca
