CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-49966 – drm/amd/pm: add missing ->fini_microcode interface for Sienna Cichlid
https://notcve.org/view.php?id=CVE-2022-49966
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: add missing ->fini_microcode interface for Sienna Cichlid To avoid any potential memory leak. • https://git.kernel.org/stable/c/60d522f317078381ff8a3599fe808f96fc256cd5 •
CVSS: 5.6EPSS: 0%CPEs: 2EXPL: 0CVE-2022-49965 – drm/amd/pm: add missing ->fini_xxxx interfaces for some SMU13 asics
https://notcve.org/view.php?id=CVE-2022-49965
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: add missing ->fini_xxxx interfaces for some SMU13 asics Without these, potential memory leak may be induced. • https://git.kernel.org/stable/c/22a75c616f1971c23838506b14971a4ef4a66bd7 •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-49964 – arm64: cacheinfo: Fix incorrect assignment of signed error value to unsigned fw_level
https://notcve.org/view.php?id=CVE-2022-49964
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: arm64: cacheinfo: Fix incorrect assignment of signed error value to unsigned fw_level Though acpi_find_last_cache_level() always returned signed value and the document states it will return any errors caused by lack of a PPTT table, it never returned negative values before. Commit 0c80f9e165f8 ("ACPI: PPTT: Leave the table mapped for the runtime usage") however changed it by returning -ENOENT if no PPTT was found. The value returned from ac... • https://git.kernel.org/stable/c/1668c38ef2e5bb80dbee88afcecfcdc3e7abc2aa •
CVSS: 7.1EPSS: 0%CPEs: 2EXPL: 0CVE-2022-49963 – drm/i915/ttm: fix CCS handling
https://notcve.org/view.php?id=CVE-2022-49963
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/i915/ttm: fix CCS handling Crucible + recent Mesa seems to sometimes hit: GEM_BUG_ON(num_ccs_blks > NUM_CCS_BLKS_PER_XFER) And it looks like we can also trigger this with gem_lmem_swapping, if we modify the test to use slightly larger object sizes. Looking closer it looks like we have the following issues in migrate_copy(): - We are using plain integer in various places, which we can easily overflow with a large object. - We pass the en... • https://git.kernel.org/stable/c/da0595ae91da837929a00470ab40546090e5b9ae •
CVSS: 7.8EPSS: 0%CPEs: 2EXPL: 0CVE-2022-49962 – xhci: Fix null pointer dereference in remove if xHC has only one roothub
https://notcve.org/view.php?id=CVE-2022-49962
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: xhci: Fix null pointer dereference in remove if xHC has only one roothub The remove path in xhci platform driver tries to remove and put both main and shared hcds even if only a main hcd exists (one roothub) This causes a null pointer dereference in reboot for those controllers. Check that the shared_hcd exists before trying to remove it. In the Linux kernel, the following vulnerability has been resolved: xhci: Fix null pointer dereference ... • https://git.kernel.org/stable/c/e0fe986972f5b6b12086c73569206dd29c520be9 •
CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-49961 – bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO
https://notcve.org/view.php?id=CVE-2022-49961
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated whenever we have an ARG_CONST_* style argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of states_equal check when such arguments refine the return value (in this case, set mem_size for PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value, and if the verifier incorrect... • https://git.kernel.org/stable/c/457f44363a8894135c85b7a9afd2bd8196db24ab •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-49960 – drm/i915: fix null pointer dereference
https://notcve.org/view.php?id=CVE-2022-49960
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/i915: fix null pointer dereference Asus chromebook CX550 crashes during boot on v5.17-rc1 kernel. The root cause is null pointer defeference of bi_next in tgl_get_bw_info() in drivers/gpu/drm/i915/display/intel_bw.c. BUG: kernel NULL pointer dereference, address: 000000000000002e PGD 0 P4D 0 Oops: 0002 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 1 Comm: swapper/0 Tainted: G U 5.17.0-rc1 Hardware name: Google Delbin/Delbin, BIOS Google_Delbin.136... • https://git.kernel.org/stable/c/c64a9a7c05beb2b71b7496d873654f88e1a08593 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2022-49959 – openvswitch: fix memory leak at failed datapath creation
https://notcve.org/view.php?id=CVE-2022-49959
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: openvswitch: fix memory leak at failed datapath creation ovs_dp_cmd_new()->ovs_dp_change()->ovs_dp_set_upcall_portids() allocates array via kmalloc. If for some reason new_vport() fails during ovs_dp_cmd_new() dp->upcall_portids must be freed. Add missing kfree. Kmemleak example: unreferenced object 0xffff88800c382500 (size 64): comm "dump_state", pid 323, jiffies 4294955418 (age 104.347s) hex dump (first 32 bytes): 5e c2 79 e4 1f 7a 38 c7 ... • https://git.kernel.org/stable/c/b83d23a2a38b1770da0491257ae81d52307f7816 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-49958 – net/sched: fix netdevice reference leaks in attach_default_qdiscs()
https://notcve.org/view.php?id=CVE-2022-49958
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: net/sched: fix netdevice reference leaks in attach_default_qdiscs() In attach_default_qdiscs(), if a dev has multiple queues and queue 0 fails to attach qdisc because there is no memory in attach_one_default_qdisc(). Then dev->qdisc will be noop_qdisc by default. But the other queues may be able to successfully attach to default qdisc. In this case, the fallback to noqueue process will be triggered. If the original attached qdisc is not rel... • https://git.kernel.org/stable/c/bf6dba76d278d296b385b436d3ac7de56c190d44 •
CVSS: 5.5EPSS: 0%CPEs: 10EXPL: 0CVE-2022-49957 – kcm: fix strp_init() order and cleanup
https://notcve.org/view.php?id=CVE-2022-49957
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: kcm: fix strp_init() order and cleanup strp_init() is called just a few lines above this csk->sk_user_data check, it also initializes strp->work etc., therefore, it is unnecessary to call strp_done() to cancel the freshly initialized work. And if sk_user_data is already used by KCM, psock->strp should not be touched, particularly strp->work state, so we need to move strp_init() after the csk->sk_user_data check. This also makes a lockdep wa... • https://git.kernel.org/stable/c/44890e9ff771ef11777b2d1ebf8589255eb12502 •