CVSS: 9.0EPSS: 0%CPEs: 5EXPL: 0CVE-2022-50580 – blk-throttle: prevent overflow while calculating wait time
https://notcve.org/view.php?id=CVE-2022-50580
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: blk-throttle: prevent overflow while calculating wait time There is a problem found by code review in tg_with_in_bps_limit() that 'bps_limit * jiffy_elapsed_rnd' might overflow. Fix the problem by calling mul_u64_u64_div_u64() instead. In the Linux kernel, the following vulnerability has been resolved: blk-throttle: prevent overflow while calculating wait time There is a problem found by code review in tg_with_in_bps_limit() that 'bps_limit... • https://git.kernel.org/stable/c/19c010ae44f0ce52b5436080492a61a092ee0cf4 •
CVSS: 7.1EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50579 – arm64: ftrace: fix module PLTs with mcount
https://notcve.org/view.php?id=CVE-2022-50579
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: arm64: ftrace: fix module PLTs with mcount Li Huafei reports that mcount-based ftrace with module PLTs was broken by commit: a6253579977e4c6f ("arm64: ftrace: consistently handle PLTs.") When a module PLTs are used and a module is loaded sufficiently far away from the kernel, we'll create PLTs for any branches which are out-of-range. These are separate from the special ftrace trampoline PLTs, which the module PLT code doesn't directly manip... • https://git.kernel.org/stable/c/bc28fde90937a920f7714ec4408269cac744f796 •
CVSS: 7.8EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50578 – class: fix possible memory leak in __class_register()
https://notcve.org/view.php?id=CVE-2022-50578
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: class: fix possible memory leak in __class_register() If class_add_groups() returns error, the 'cp->subsys' need be unregister, and the 'cp' need be freed. We can not call kset_unregister() here, because the 'cls' will be freed in callback function class_release() and it's also freed in caller's error path, it will cause double free. So fix this by calling kobject_del() and kfree_const(name) to cleanup kobject. Besides, call kfree() to free... • https://git.kernel.org/stable/c/ced6473e7486702f530a49f886b73195e4977734 •
CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50577 – ima: Fix memory leak in __ima_inode_hash()
https://notcve.org/view.php?id=CVE-2022-50577
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: ima: Fix memory leak in __ima_inode_hash() Commit f3cc6b25dcc5 ("ima: always measure and audit files in policy") lets measurement or audit happen even if the file digest cannot be calculated. As a result, iint->ima_hash could have been allocated despite ima_collect_measurement() returning an error. Since ima_hash belongs to a temporary inode metadata structure, declared at the beginning of __ima_inode_hash(), just add a kfree() call if ima_... • https://git.kernel.org/stable/c/280fe8367b0dc45b6ac5e04fad03e16e99540c0c •
CVSS: 7.1EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50576 – serial: pch: Fix PCI device refcount leak in pch_request_dma()
https://notcve.org/view.php?id=CVE-2022-50576
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: serial: pch: Fix PCI device refcount leak in pch_request_dma() As comment of pci_get_slot() says, it returns a pci_device with its refcount increased. The caller must decrement the reference count by calling pci_dev_put(). Since 'dma_dev' is only used to filter the channel in filter(), we can call pci_dev_put() before exiting from pch_request_dma(). Add the missing pci_dev_put() for the normal and error path. In the Linux kernel, the follow... • https://git.kernel.org/stable/c/3c6a483275f47a2ef7119309ad3d791c10cf30da •
CVSS: 7.1EPSS: 0%CPEs: 7EXPL: 0CVE-2022-50575 – xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
https://notcve.org/view.php?id=CVE-2022-50575
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource() As 'kdata.num' is user-controlled data, if user tries to allocate memory larger than(>=) MAX_ORDER, then kcalloc() will fail, it creates a stack trace and messes up dmesg with a warning. Call trace: -> privcmd_ioctl --> privcmd_ioctl_mmap_resource Add __GFP_NOWARN in order to avoid too large allocation warning. This is detected by static analysis using smatch. In the Linux... • https://git.kernel.org/stable/c/3ad0876554cafa368f574d4d408468510543e9ff •
CVSS: 7.1EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50574 – drm/omap: dss: Fix refcount leak bugs
https://notcve.org/view.php?id=CVE-2022-50574
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/omap: dss: Fix refcount leak bugs In dss_init_ports() and __dss_uninit_ports(), we should call of_node_put() for the reference returned by of_graph_get_port_by_id() in fail path or when it is not used anymore. In the Linux kernel, the following vulnerability has been resolved: drm/omap: dss: Fix refcount leak bugs In dss_init_ports() and __dss_uninit_ports(), we should call of_node_put() for the reference returned by of_graph_get_port_b... • https://git.kernel.org/stable/c/09bffa6e519256c6fa1552d6ba1f5d594337a464 •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-50573 – wifi: mt76: mt7915: fix mt7915_rate_txpower_get() resource leaks
https://notcve.org/view.php?id=CVE-2022-50573
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7915: fix mt7915_rate_txpower_get() resource leaks Coverity message: variable "buf" going out of scope leaks the storage. Addresses-Coverity-ID: 1527799 ("Resource leaks") • https://git.kernel.org/stable/c/e3296759f34752ea2562678706dbb5bf607af530 •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50572 – ASoC: audio-graph-card: fix refcount leak of cpu_ep in __graph_for_each_link()
https://notcve.org/view.php?id=CVE-2022-50572
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: ASoC: audio-graph-card: fix refcount leak of cpu_ep in __graph_for_each_link() The of_get_next_child() returns a node with refcount incremented, and decrements the refcount of prev. So in the error path of the while loop, of_node_put() needs be called for cpu_ep. In the Linux kernel, the following vulnerability has been resolved: ASoC: audio-graph-card: fix refcount leak of cpu_ep in __graph_for_each_link() The of_get_next_child() returns a... • https://git.kernel.org/stable/c/fce9b90c1ab7e915553c57353355700c79b39c86 •
CVSS: 7.1EPSS: 0%CPEs: 2EXPL: 0CVE-2022-50571 – btrfs: call __btrfs_remove_free_space_cache_locked on cache load failure
https://notcve.org/view.php?id=CVE-2022-50571
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: btrfs: call __btrfs_remove_free_space_cache_locked on cache load failure Now that lockdep is staying enabled through our entire CI runs I started seeing the following stack in generic/475 ------------[ cut here ]------------ WARNING: CPU: 1 PID: 2171864 at fs/btrfs/discard.c:604 btrfs_discard_update_discardable+0x98/0xb0 CPU: 1 PID: 2171864 Comm: kworker/u4:0 Not tainted 5.19.0-rc8+ #789 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), B... • https://git.kernel.org/stable/c/819a61301275dcc573e3f520be3dc2c8531bee2d •