CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50481 – cxl: fix possible null-ptr-deref in cxl_guest_init_afu|adapter()
https://notcve.org/view.php?id=CVE-2022-50481
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: cxl: fix possible null-ptr-deref in cxl_guest_init_afu|adapter() If device_register() fails in cxl_register_afu|adapter(), the device is not added, device_unregister() can not be called in the error path, otherwise it will cause a null-ptr-deref because of removing not added device. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So split device_unregister() into device_del() and ... • https://git.kernel.org/stable/c/14baf4d9c739e6e69150512d2eb23c71fffcc192 •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50480 – memory: pl353-smc: Fix refcount leak bug in pl353_smc_probe()
https://notcve.org/view.php?id=CVE-2022-50480
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: memory: pl353-smc: Fix refcount leak bug in pl353_smc_probe() The break of for_each_available_child_of_node() needs a corresponding of_node_put() when the reference 'child' is not used anymore. Here we do not need to call of_node_put() in fail path as '!match' means no break. While the of_platform_device_create() will created a new reference by 'child' but it has considered the refcounting. In the Linux kernel, the following vulnerability h... • https://git.kernel.org/stable/c/fee10bd2267868f2a3e7ba008ef7665aac5e4412 •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-50479 – drm/amd: fix potential memory leak
https://notcve.org/view.php?id=CVE-2022-50479
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amd: fix potential memory leak This patch fix potential memory leak (clk_src) when function run into last return NULL. s/free/kfree/ - Alex In the Linux kernel, the following vulnerability has been resolved: drm/amd: fix potential memory leak This patch fix potential memory leak (clk_src) when function run into last return NULL. s/free/kfree/ - Alex The SUSE Linux Enterprise 15 SP5 RT kernel was updated to fix various security issues. • https://git.kernel.org/stable/c/3a83e4e64bb1522ddac67ffc787d1c38291e1a65 • CWE-772: Missing Release of Resource after Effective Lifetime •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50478 – nilfs2: fix shift-out-of-bounds/overflow in nilfs_sb2_bad_offset()
https://notcve.org/view.php?id=CVE-2022-50478
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix shift-out-of-bounds/overflow in nilfs_sb2_bad_offset() Patch series "nilfs2: fix UBSAN shift-out-of-bounds warnings on mount time". The first patch fixes a bug reported by syzbot, and the second one fixes the remaining bug of the same kind. Although they are triggered by the same super block data anomaly, I divided it into the above two because the details of the issues and how to fix it are different. Both are required to elimi... • https://git.kernel.org/stable/c/e339ad31f59925b48a92ee3947692fdf9758b8c7 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50477 – rtc: class: Fix potential memleak in devm_rtc_allocate_device()
https://notcve.org/view.php?id=CVE-2022-50477
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: rtc: class: Fix potential memleak in devm_rtc_allocate_device() devm_rtc_allocate_device() will alloc a rtc_device first, and then run dev_set_name(). If dev_set_name() failed, the rtc_device will memleak. Move devm_add_action_or_reset() in front of dev_set_name() to prevent memleak. unreferenced object 0xffff888110a53000 (size 2048): comm "python3", pid 470, jiffies 4296078308 (age 58.882s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 0... • https://git.kernel.org/stable/c/24d23181e43d72ca692a479e70dfe5b0b5dd33f1 • CWE-772: Missing Release of Resource after Effective Lifetime •
CVSS: 7.2EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50476 – ntb_netdev: Use dev_kfree_skb_any() in interrupt context
https://notcve.org/view.php?id=CVE-2022-50476
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: ntb_netdev: Use dev_kfree_skb_any() in interrupt context TX/RX callback handlers (ntb_netdev_tx_handler(), ntb_netdev_rx_handler()) can be called in interrupt context via the DMA framework when the respective DMA operations have completed. As such, any calls by these routines to free skb's, should use the interrupt context safe dev_kfree_skb_any() function. Previously, these callback handlers would call the interrupt unsafe version of dev_k... • https://git.kernel.org/stable/c/548c237c0a9972df5d1afaca38aa733ee577128d •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-50475 – RDMA/core: Make sure "ib_port" is valid when access sysfs node
https://notcve.org/view.php?id=CVE-2022-50475
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Make sure "ib_port" is valid when access sysfs node The "ib_port" structure must be set before adding the sysfs kobject, and reset after removing it, otherwise it may crash when accessing the sysfs node: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000050 Mem abort info: ESR = 0x96000006 Exception class = DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 Data abort info: ISV = 0, ... • https://git.kernel.org/stable/c/d8a5883814b9f7c08d7ff291070687d925b4f859 • CWE-825: Expired Pointer Dereference •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50474 – macintosh: fix possible memory leak in macio_add_one_device()
https://notcve.org/view.php?id=CVE-2022-50474
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: macintosh: fix possible memory leak in macio_add_one_device() Afer commit 1fa5ae857bb1 ("driver core: get rid of struct device's bus_id string array"), the name of device is allocated dynamically. It needs to be freed when of_device_register() fails. Call put_device() to give up the reference that's taken in device_initialize(), so that it can be freed in kobject_cleanup() when the refcount hits 0. macio device is freed in macio_release_dev... • https://git.kernel.org/stable/c/1fa5ae857bb14f6046205171d98506d8112dd74e •
CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2022-50473 – cpufreq: Init completion before kobject_init_and_add()
https://notcve.org/view.php?id=CVE-2022-50473
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: cpufreq: Init completion before kobject_init_and_add() In cpufreq_policy_alloc(), it will call uninitialed completion in cpufreq_sysfs_release() when kobject_init_and_add() fails. And that will cause a crash such as the following page fault in complete: BUG: unable to handle page fault for address: fffffffffffffff8 [..] RIP: 0010:complete+0x98/0x1f0 [..] Call Trace: kobject_put+0x1be/0x4c0 cpufreq_online.cold+0xee/0x1fd cpufreq_add_dev+0x18... • https://git.kernel.org/stable/c/4ebe36c94aed95de71a8ce6a6762226d31c938ee • CWE-909: Missing Initialization of Resource •
CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 0CVE-2022-50472 – IB/mad: Don't call to function that might sleep while in atomic context
https://notcve.org/view.php?id=CVE-2022-50472
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: IB/mad: Don't call to function that might sleep while in atomic context Tracepoints are not allowed to sleep, as such the following splat is generated due to call to ib_query_pkey() in atomic context. WARNING: CPU: 0 PID: 1888000 at kernel/trace/ring_buffer.c:2492 rb_commit+0xc1/0x220 CPU: 0 PID: 1888000 Comm: kworker/u9:0 Kdump: loaded Tainted: G OE --------- - - 4.18.0-305.3.1.el8.x86_64 #1 Hardware name: Red Hat KVM, BIOS 1.13.0-2.module... • https://git.kernel.org/stable/c/821bf1de45a1a084e2e11b1a2308777434194bfe • CWE-474: Use of Function with Inconsistent Implementations •