CVE-2022-48888 – drm/msm/dpu: Fix memory leak in msm_mdss_parse_data_bus_icc_path
https://notcve.org/view.php?id=CVE-2022-48888
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: Fix memory leak in msm_mdss_parse_data_bus_icc_path of_icc_get() alloc resources for path1, we should release it when not need anymore. Early return when IS_ERR_OR_NULL(path0) may leak path1. Defer getting path1 to fix this. Patchwork: https://patchwork.freedesktop.org/patch/514264/ • https://git.kernel.org/stable/c/b9364eed9232f3d2a846f68c2307eb25c93cc2d0 https://git.kernel.org/stable/c/c6fa1de83fd87267ab24359e6fa52f98f5cee3f9 https://git.kernel.org/stable/c/45dac1352b55b1d8cb17f218936b2bc2bc1fb4ee •
CVE-2022-48887 – drm/vmwgfx: Remove rcu locks from user resources
https://notcve.org/view.php?id=CVE-2022-48887
In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Remove rcu locks from user resources User resource lookups used rcu to avoid two extra atomics. Unfortunately the rcu paths were buggy and it was easy to make the driver crash by submitting command buffers from two different threads. Because the lookups never show up in performance profiles replace them with a regular spin lock which fixes the races in accesses to those shared resources. Fixes kernel oops'es in IGT's vmwgfx execution_buffer stress test and seen crashes with apps using shared resources. • https://git.kernel.org/stable/c/e14c02e6b6990e9f6ee18a214a22ac26bae1b25e https://git.kernel.org/stable/c/7ac9578e45b20e3f3c0c8eb71f5417a499a7226a https://git.kernel.org/stable/c/a309c7194e8a2f8bd4539b9449917913f6c2cd50 •
CVE-2022-48886 – ice: Add check for kzalloc
https://notcve.org/view.php?id=CVE-2022-48886
In the Linux kernel, the following vulnerability has been resolved: ice: Add check for kzalloc Add the check for the return value of kzalloc in order to avoid NULL pointer dereference. Moreover, use the goto-label to share the clean code. • https://git.kernel.org/stable/c/d6b98c8d242aee40e7b8919dd07b593b0739e38d https://git.kernel.org/stable/c/96a9873188552ebb2afe76033d7329a5ecabef6e https://git.kernel.org/stable/c/40543b3d9d2c13227ecd3aa90a713c201d1d7f09 •
CVE-2022-48885 – ice: Fix potential memory leak in ice_gnss_tty_write()
https://notcve.org/view.php?id=CVE-2022-48885
In the Linux kernel, the following vulnerability has been resolved: ice: Fix potential memory leak in ice_gnss_tty_write() The ice_gnss_tty_write() return directly if the write_buf alloc failed, leaking the cmd_buf. Fix by free cmd_buf if write_buf alloc failed. • https://git.kernel.org/stable/c/d6b98c8d242aee40e7b8919dd07b593b0739e38d https://git.kernel.org/stable/c/500ca1da9d0876244eb4d1b0ece6fa0e9968d45d https://git.kernel.org/stable/c/f58985620f55580a07d40062c4115d8c9cf6ae27 https://access.redhat.com/security/cve/CVE-2022-48885 https://bugzilla.redhat.com/show_bug.cgi?id=2306406 • CWE-401: Missing Release of Memory after Effective Lifetime •
CVE-2022-48884 – net/mlx5: Fix command stats access after free
https://notcve.org/view.php?id=CVE-2022-48884
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix command stats access after free Command may fail while driver is reloading and can't accept FW commands till command interface is reinitialized. Such command failure is being logged to command stats. This results in NULL pointer access as command stats structure is being freed and reallocated during mlx5 devlink reload (see kernel log below). Fix it by making command stats statically allocated on driver probe. Kernel log: [ 2394.808802] BUG: unable to handle kernel paging request at 000000000002a9c0 [ 2394.810610] PGD 0 P4D 0 [ 2394.811811] Oops: 0002 [#1] SMP NOPTI ... [ 2394.815482] RIP: 0010:native_queued_spin_lock_slowpath+0x183/0x1d0 ... [ 2394.829505] Call Trace: [ 2394.830667] _raw_spin_lock_irq+0x23/0x26 [ 2394.831858] cmd_status_err+0x55/0x110 [mlx5_core] [ 2394.833020] mlx5_access_reg+0xe7/0x150 [mlx5_core] [ 2394.834175] mlx5_query_port_ptys+0x78/0xa0 [mlx5_core] [ 2394.835337] mlx5e_ethtool_get_link_ksettings+0x74/0x590 [mlx5_core] [ 2394.836454] ? kmem_cache_alloc_trace+0x140/0x1c0 [ 2394.837562] __rh_call_get_link_ksettings+0x33/0x100 [ 2394.838663] ? __rtnl_unlock+0x25/0x50 [ 2394.839755] __ethtool_get_link_ksettings+0x72/0x150 [ 2394.840862] duplex_show+0x6e/0xc0 [ 2394.841963] dev_attr_show+0x1c/0x40 [ 2394.843048] sysfs_kf_seq_show+0x9b/0x100 [ 2394.844123] seq_read+0x153/0x410 [ 2394.845187] vfs_read+0x91/0x140 [ 2394.846226] ksys_read+0x4f/0xb0 [ 2394.847234] do_syscall_64+0x5b/0x1a0 [ 2394.848228] entry_SYSCALL_64_after_hwframe+0x65/0xca • https://git.kernel.org/stable/c/34f46ae0d4b38e83cfb26fb6f06b5b5efea47fdc https://git.kernel.org/stable/c/ddf458641a511e7dff19f3bf0cbbc5dd9fe08ce5 https://git.kernel.org/stable/c/da2e552b469a0cd130ff70a88ccc4139da428a65 https://access.redhat.com/security/cve/CVE-2022-48884 https://bugzilla.redhat.com/show_bug.cgi?id=2306405 • CWE-416: Use After Free •