Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
call_64+0x43/0x55 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fa99f6e689b References: - https://git.kernel.org/stable/c/065e83ac83c0c0e615b96947145c85c4bd76c09a - https://git.kernel.org/stable/c/5abc81a138f873ab55223ec674afc3a3f945d60f - https://git.kernel.org/stable/c/683a4647a7a3044868cfdc14c117525091b9fa0c
CVE ID: CVE-2022-50179 State: PUBLISHED Published: 2025-06-18T11:03:28.841Z Last Updated: 2025-06-18T11:03:28.841Z Vendors: Linux Products: Linux Description: 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 <IRQ> ... ath9k_hif_usb_rx_cb() ath9k_hif_usb_rx_stream() RX_STAT_INC() <--- htc_handle->dr
) <--- priv pointer is freed <IRQ> ... ath9k_hif_usb_rx_cb() ath9k_hif_usb_rx_stream() RX_STAT_INC() <--- htc_handle->drv_priv access In order to not add fancy protection for drv_priv we can move htc_handle->drv_priv initialization at the end of the ath9k_htc_probe_device() and add helper macro to make all *_STAT_* macros NULL safe, since syzbot has reported related NULL deref in that macros [1] References: - https://git.kernel.org/stable/c/62bc1ea5c7401d77eaf73d0c6a15f3d2e742856e - https://git.kernel.org/stable/c/ab7a0ddf5f1cdec63cb21840369873806fc36d80 - https://git.kernel.org/stable/c/e9e21206b8ea62220b486310c61277e7ebfe7cec - https://git.kernel.org/stable/c/eccd7c3e2596b574241a7670b5b53f
l.org/stable/c/e9e21206b8ea62220b486310c61277e7ebfe7cec - https://git.kernel.org/stable/c/eccd7c3e2596b574241a7670b5b53f5322f470e5 - https://git.kernel.org/stable/c/03ca957c5f7b55660957eda20b5db4110319ac7a - https://git.kernel.org/stable/c/6b14ab47937ba441e75e8dbb9fbfc9c55efa41c6 - https://git.kernel.org/stable/c/b66ebac40f64336ae2d053883bee85261060bd27 - https://git.kernel.org/stable/c/0ac4827f78c7ffe8eef074bc010e7e34bc22f533
CVE ID: CVE-2022-50180 State: REJECTED Published: 2025-06-18T11:03:29.488Z Last Updated: 2025-06-18T13:50:59.712Z Description: No description available.
CVE ID: CVE-2022-50181 State: PUBLISHED Published: 2025-06-18T11:03:30.273Z Last Updated: 2025-06-18T11:03:30.273Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: virtio-gpu: fix a missing check to avoid NULL dereference 'cache_ent' could be set NULL inside virtio_gpu_cmd_get_capset() and it will lead to a NULL dereference by a lately use of it (i.e., ptr = cache_ent->caps_cache). Fix it with a NULL check. [ kraxel: minor codestyle fixup ] References: - https://git.kernel.org/stable/c/259773fc874258606c0121767a4a27466ff337eb - https://git.kernel.org/stable/c/39caef09666c1d8274abf9472c72bcac236dc5fb - https://git.kernel.org/stabl
4a27466ff337eb - https://git.kernel.org/stable/c/39caef09666c1d8274abf9472c72bcac236dc5fb - https://git.kernel.org/stable/c/adbdd21983fa292e53aec3eab97306b2961ea887 - https://git.kernel.org/stable/c/367882a5a9448b5e1ba756125308092d614cb96c - https://git.kernel.org/stable/c/bd63f11f4c3c46afec07d821f74736161ff6e526
CVE ID: CVE-2022-50182 State: PUBLISHED Published: 2025-06-18T11:03:30.943Z Last Updated: 2025-06-18T11:03:30.943Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: media: imx-jpeg: Align upwards buffer size The hardware can support any image size WxH, with arbitrary W (image width) and H (image height) dimensions. Align upwards buffer size for both encoder and decoder. and leave the picture resolution unchanged. For decoder, the risk of memory out of bounds can be avoided. For both encoder and decoder, the driver will lift the limitation of resolution alignment. For example, the decoder can support jpeg whose resolution is 227x14
r will lift the limitation of resolution alignment. For example, the decoder can support jpeg whose resolution is 227x149 the encoder can support nv12 1080P, won't change it to 1920x1072. References: - https://git.kernel.org/stable/c/9ae2d729de6350c53a06c57782751d84eb2c08d9 - https://git.kernel.org/stable/c/73d1836ed7911953182b787745cb8c5857a2661c - https://git.kernel.org/stable/c/447795ffb17cd60bb544e0abfc9399e180a14a2f - https://git.kernel.org/stable/c/9e7aa76cdb02923ee23a0ddd48f38bdc3512f92b
CVE ID: CVE-2022-50183 State: PUBLISHED Published: 2025-06-18T11:03:31.531Z Last Updated: 2025-06-18T11:03:31.531Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/meson: encoder_cvbs: Fix refcount leak in meson_encoder_cvbs_init of_graph_get_remote_node() 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. References: - https://git.kernel.org/stable/c/51c36411ae27bf5f06c43462d2de2d4947ed33ea - https://git.kernel.org/stable/c/bb5ac08d5bd8626c318bd80a5063263daab8fdb6 - https://git.kernel.org/stable/c/7d255ddbbf679aa47e041cbf
.kernel.org/stable/c/bb5ac08d5bd8626c318bd80a5063263daab8fdb6 - https://git.kernel.org/stable/c/7d255ddbbf679aa47e041cbf68520fd985ed2279
CVE ID: CVE-2022-50184 State: PUBLISHED Published: 2025-06-18T11:03:32.214Z Last Updated: 2025-06-18T11:03:32.214Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/meson: encoder_hdmi: Fix refcount leak in meson_encoder_hdmi_init of_graph_get_remote_node() 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. References: - https://git.kernel.org/stable/c/275fed7142fff5b27e176e53508196715043de5c - https://git.kernel.org/stable/c/994bc82df85564d948037f1dfdd47c907e8a084b - https://git.kernel.org/stable/c/013e67e7dd898170cbf54981
.kernel.org/stable/c/994bc82df85564d948037f1dfdd47c907e8a084b - https://git.kernel.org/stable/c/013e67e7dd898170cbf54981cf1ed7616f822566 - https://git.kernel.org/stable/c/d82a5a4aae9d0203234737caed1bf470aa317568
CVE ID: CVE-2022-50185 State: PUBLISHED Published: 2025-06-18T11:03:32.843Z Last Updated: 2025-06-18T11:03:32.843Z Vendors: Linux Products: Linux Description: 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
heck 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. References: - https://git.kernel.org/stable/c/ea73869df6ef386fc0feeb28ff66742ca835b18f - https://git.kernel.org/stable/c/1f341053852be76f82610ce47a505d930512f05c - https://git.kernel.org/stable/c/db1a9add3f90ff1c641974d5bb910c16b87af4ef - https://git.kernel.org/stable/c/8508d6d23a247c29792ce2fc0df3f3404d6a6a80 - https://git.kernel.or
974d5bb910c16b87af4ef - https://git.kernel.org/stable/c/8508d6d23a247c29792ce2fc0df3f3404d6a6a80 - https://git.kernel.org/stable/c/deb603c5928e546609c0d5798e231d0205748943 - https://git.kernel.org/stable/c/782e413e38dffd37cc85b08b1ccb982adb4a93ce - https://git.kernel.org/stable/c/9faff03617afeced1c4e5daa89e79b3906374342 - https://git.kernel.org/stable/c/136f614931a2bb73616b292cf542da3a18daefd5
CVE ID: CVE-2022-50186 State: PUBLISHED Published: 2025-06-18T11:03:33.552Z Last Updated: 2025-06-18T11:03:33.552Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ath11k: fix missing skb drop on htc_tx_completion error On htc_tx_completion error the skb is not dropped. This is wrong since the completion_handler logic expect the skb to be consumed anyway even when an error is triggered. Not freeing the skb on error is a memory leak since the skb won't be freed anywere else. Correctly free the packet on eid >= ATH11K_HTC_EP_COUNT before returning. Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.5.0.1-01208-QCAHKSWPL_SILICONZ-1 References:
H11K_HTC_EP_COUNT before returning. Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.5.0.1-01208-QCAHKSWPL_SILICONZ-1 References: - https://git.kernel.org/stable/c/dda25326839d6e6b1fe59e79616149e44ea4eaa4 - https://git.kernel.org/stable/c/1f1483361585ae7556492f50f83f038bbdf8c294 - https://git.kernel.org/stable/c/e5646fe3b7ef739c392e59da7db6adf5e1fdef42
CVE ID: CVE-2022-50187 State: PUBLISHED Published: 2025-06-18T11:03:34.265Z Last Updated: 2025-06-18T11:03:34.265Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ath11k: fix netdev open race Make sure to allocate resources needed before registering the device. This specifically avoids having a racing open() trigger a BUG_ON() in mod_timer() when ath11k_mac_op_start() is called before the mon_reap_timer as been set up. I did not see this issue with next-20220310, but I hit it on every probe with next-20220511. Perhaps some timing changed in between. Here's the backtrace: [ 51.346947] kernel BUG at kernel/time/timer.c:990! [ 51.3
Perhaps some timing changed in between. Here's the backtrace: [ 51.346947] kernel BUG at kernel/time/timer.c:990! [ 51.346958] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ... [ 51.578225] Call trace: [ 51.583293] __mod_timer+0x298/0x390 [ 51.589518] mod_timer+0x14/0x20 [ 51.595368] ath11k_mac_op_start+0x41c/0x4a0 [ath11k] [ 51.603165] drv_start+0x38/0x60 [mac80211] [ 51.610110] ieee80211_do_open+0x29c/0x7d0 [mac80211] [ 51.617945] ieee80211_open+0x60/0xb0 [mac80211] [ 51.625311] __dev_open+0x100/0x1c0 [ 51.631420] __dev_change_flags+0x194/0x210 [ 51.638214] dev_change_flags+0x24/0x70 [ 51.644646] do_setlink+0x228/0xdb0 [ 51.650723] __rtnl_newlink+0x460/0x830 [ 51.657162] rtnl_newlink+0x4c
ags+0x24/0x70 [ 51.644646] do_setlink+0x228/0xdb0 [ 51.650723] __rtnl_newlink+0x460/0x830 [ 51.657162] rtnl_newlink+0x4c/0x80 [ 51.663229] rtnetlink_rcv_msg+0x124/0x390 [ 51.669917] netlink_rcv_skb+0x58/0x130 [ 51.676314] rtnetlink_rcv+0x18/0x30 [ 51.682460] netlink_unicast+0x250/0x310 [ 51.688960] netlink_sendmsg+0x19c/0x3e0 [ 51.695458] ____sys_sendmsg+0x220/0x290 [ 51.701938] ___sys_sendmsg+0x7c/0xc0 [ 51.708148] __sys_sendmsg+0x68/0xd0 [ 51.714254] __arm64_sys_sendmsg+0x28/0x40 [ 51.720900] invoke_syscall+0x48/0x120 Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3 References: - https://git.kernel.org/stable/c/a2c45f8c3d18269e641f0c7da2dde47ef8414034 - http
SWPL_V1_V2_SILICONZ_LITE-3 References: - https://git.kernel.org/stable/c/a2c45f8c3d18269e641f0c7da2dde47ef8414034 - https://git.kernel.org/stable/c/eaff3946a86fc63280a30158a4ae1e141449817c - https://git.kernel.org/stable/c/abb7dc8fbb27c15dcc927df56190f3c5ede58bd5 - https://git.kernel.org/stable/c/307ce58270b3b50ca21cfcc910568429b06803f7 - https://git.kernel.org/stable/c/d4ba1ff87b17e81686ada8f429300876f55f95ad
CVE ID: CVE-2022-50188 State: PUBLISHED Published: 2025-06-18T11:03:34.887Z Last Updated: 2025-06-18T11:03:34.887Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/meson: Fix refcount leak in meson_encoder_hdmi_init of_find_device_by_node() takes reference, we should use put_device() to release it when not need anymore. Add missing put_device() in error path to avoid refcount leak. References: - https://git.kernel.org/stable/c/50446ac34545580d073ff0dd154b796726772668 - https://git.kernel.org/stable/c/79b15eb0aa059b3a5bc60364ce82eb2cefac80db - https://git.kernel.org/stable/c/bfcca6234b2a36d213f0cc1c127becc17680f7df - https://g
0aa059b3a5bc60364ce82eb2cefac80db - https://git.kernel.org/stable/c/bfcca6234b2a36d213f0cc1c127becc17680f7df - https://git.kernel.org/stable/c/7381076809586528e2a812a709e2758916318a99
CVE ID: CVE-2022-50189 State: PUBLISHED Published: 2025-06-18T11:03:35.532Z Last Updated: 2025-06-18T11:03:35.532Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: tools/power turbostat: Fix file pointer leak Currently if a fscanf fails then an early return leaks an open file pointer. Fix this by fclosing the file before the return. Detected using static analysis with cppcheck: tools/power/x86/turbostat/turbostat.c:2039:3: error: Resource leak: fp [resourceLeak] References: - https://git.kernel.org/stable/c/2ebf6f5946817f33fb33e613e359229e98164eb3 - https://git.kernel.org/stable/c/5e5fd36c58d6c820f7292ee492c3731c9a104a41
CVE ID: CVE-2022-50190 State: PUBLISHED Published: 2025-06-18T11:03:36.320Z Last Updated: 2025-06-18T11:03:36.320Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: spi: Fix simplification of devm_spi_register_controller This reverts commit 59ebbe40fb51 ("spi: simplify devm_spi_register_controller"). If devm_add_action() fails in devm_add_action_or_reset(), devm_spi_unregister() will be called, it decreases the refcount of 'ctlr->dev' to 0, then it will cause uaf in the drivers that calling spi_put_controller() in error path. References: - https://git.kernel.org/stable/c/445fb9c19cf45bd9472fd9babaa31c5e6c7d2720 - https://git.kerne
n error path. References: - https://git.kernel.org/stable/c/445fb9c19cf45bd9472fd9babaa31c5e6c7d2720 - https://git.kernel.org/stable/c/34bab623ebfc08398499e463396b81abb4abe01e - https://git.kernel.org/stable/c/3c6bd448442b6c3f6843ac70d57201a13478dd47 - https://git.kernel.org/stable/c/43cc5a0afe4184a7fafe1eba32b5a11bb69c9ce0
CVE ID: CVE-2022-50191 State: PUBLISHED Published: 2025-06-18T11:03:36.928Z Last Updated: 2025-06-18T11:03:36.928Z Vendors: Linux Products: Linux Description: 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. References: - https://git.kernel.org/stable/c/a23098cc32860272dc6c3200ff20c34c65b7b694 - https://git.kernel.org/stable/c/b9ca8585c766616563cf3c062c6878f61f83cf00 - https://git.kernel.org/stable/c/35f9e861d9b9434903a8ede37a3561f78985826d - https://git.kernel.org/stable/c/332e555dca
- https://git.kernel.org/stable/c/35f9e861d9b9434903a8ede37a3561f78985826d - https://git.kernel.org/stable/c/332e555dca074c4eb2084898021c3676423814c3 - https://git.kernel.org/stable/c/c9df8ff290097aabd5c9200f7f729b0813d37b19 - https://git.kernel.org/stable/c/11ecb4f8735b0230d54a82c18b21ea778b695d61 - https://git.kernel.org/stable/c/fc7b19f547bc9e622060a0a9a39da2330aa21c53 - https://git.kernel.org/stable/c/66efb665cd5ad69b27dca8571bf89fc6b9c628a4
CVE ID: CVE-2022-50192 State: PUBLISHED Published: 2025-06-18T11:03:37.549Z Last Updated: 2025-06-18T11:03:37.549Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: spi: tegra20-slink: fix UAF in tegra_slink_remove() After calling spi_unregister_master(), the refcount of master will be decrease to 0, and it will be freed in spi_controller_release(), the device data also will be freed, so it will lead a UAF when using 'tspi'. To fix this, get the master before unregister and put it when finish using it. References: - https://git.kernel.org/stable/c/415b4ce61308f24583912d887772dfcbf97f1d20 - https://git.kernel.org/stable/c/800c7767e
: - https://git.kernel.org/stable/c/415b4ce61308f24583912d887772dfcbf97f1d20 - https://git.kernel.org/stable/c/800c7767e05d29656713e04532823a752e57e037 - https://git.kernel.org/stable/c/67f77172644260482fdafc03b6025847944701e5 - https://git.kernel.org/stable/c/7e9984d183bb1e99e766c5c2b950ff21f7f7b6c0
CVE ID: CVE-2022-50193 State: PUBLISHED Published: 2025-06-18T11:03:38.262Z Last Updated: 2025-06-18T11:03:38.262Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: erofs: wake up all waiters after z_erofs_lzma_head ready When the user mounts the erofs second times, the decompression thread may hung. The problem happens due to a sequence of steps like the following: 1) Task A called z_erofs_load_lzma_config which obtain all of the node from the z_erofs_lzma_head. 2) At this time, task B called the z_erofs_lzma_decompress and wanted to get a node. But the z_erofs_lzma_head was empty, the Task B had to sleep. 3) Task A release nodes
compress and wanted to get a node. But the z_erofs_lzma_head was empty, the Task B had to sleep. 3) Task A release nodes and push nodes into the z_erofs_lzma_head. But task B was still sleeping. One example report when the hung happens: task:kworker/u3:1 state:D stack:14384 pid: 86 ppid: 2 flags:0x00004000 Workqueue: erofs_unzipd z_erofs_decompressqueue_work Call Trace: <TASK> __schedule+0x281/0x760 schedule+0x49/0xb0 z_erofs_lzma_decompress+0x4bc/0x580 ? cpu_core_flags+0x10/0x10 z_erofs_decompress_pcluster+0x49b/0xba0 ? __update_load_avg_se+0x2b0/0x330 ? __update_load_avg_se+0x2b0/0x330 ? update_load_avg+0x5f/0x690 ? update_load_avg+0x5f/0x690 ? set_next_entity+0xbd/0x110 ? _raw_spin_unlock
se+0x2b0/0x330 ? update_load_avg+0x5f/0x690 ? update_load_avg+0x5f/0x690 ? set_next_entity+0xbd/0x110 ? _raw_spin_unlock+0xd/0x20 z_erofs_decompress_queue.isra.0+0x2e/0x50 z_erofs_decompressqueue_work+0x30/0x60 process_one_work+0x1d3/0x3a0 worker_thread+0x45/0x3a0 ? process_one_work+0x3a0/0x3a0 kthread+0xe2/0x110 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK> References: - https://git.kernel.org/stable/c/2478e36ec437a27f8a05bea9e4269a68c554e21f - https://git.kernel.org/stable/c/96aa2a6a89618d850ef082e4268007e840c28769 - https://git.kernel.org/stable/c/2df7c4bd7c1d2bc5ece5e9ed19dbd386810c2a65
CVE ID: CVE-2022-50194 State: PUBLISHED Published: 2025-06-18T11:03:38.954Z Last Updated: 2025-06-18T11:03:38.954Z Vendors: Linux Products: Linux Description: 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. References: - https://git.kernel.org/stable/c/bc73c72a856c26df7410ddf15f42257cb4960fe9 - https://git.kernel.org/stable/c/
eferences: - https://git.kernel.org/stable/c/bc73c72a856c26df7410ddf15f42257cb4960fe9 - https://git.kernel.org/stable/c/97713ed9b6cc4abaa2dcc8357113c56520dc6d7f - https://git.kernel.org/stable/c/053543ac1d095132fcfd1263805d6e25afbdc6a8 - https://git.kernel.org/stable/c/ca83c61a6ccf3934cf8d01d5ade30a5034993a86 - https://git.kernel.org/stable/c/591f0697ccbac33760d3bb1ad96a5ba2b76ae9f0 - https://git.kernel.org/stable/c/e6e0951414a314e7db3e9e24fd924b3e15515288
CVE ID: CVE-2022-50195 State: PUBLISHED Published: 2025-06-18T11:03:39.550Z Last Updated: 2025-06-18T11:03:39.550Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ARM: dts: qcom: replace gcc PXO with pxo_board fixed clock Replace gcc PXO phandle to pxo_board fixed clock declared in the dts. gcc driver doesn't provide PXO_SRC as it's a fixed-clock. This cause a kernel panic if any driver actually try to use it. References: - https://git.kernel.org/stable/c/0a4fa4ce697987b71eafce17bb198961ed9070bd - https://git.kernel.org/stable/c/eb9e93937756a05787977875830c0dc482cb57e0
CVE ID: CVE-2022-50196 State: PUBLISHED Published: 2025-06-18T11:03:40.150Z Last Updated: 2025-06-18T11:03:40.150Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: soc: qcom: ocmem: Fix refcount leak in of_get_ocmem 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. of_node_put() will check NULL pointer. References: - https://git.kernel.org/stable/c/07aea6819d569d1e172227486655e4fb5bd4cdb9 - https://git.kernel.org/stable/c/84a928b44cb303d5756e3bff2734921de8dce4f6 - https://git.kernel.org/stable/c/a1e4243c0d
- https://git.kernel.org/stable/c/84a928b44cb303d5756e3bff2734921de8dce4f6 - https://git.kernel.org/stable/c/a1e4243c0dddeafb4ace6d9906d3f5129b81a9fe - https://git.kernel.org/stable/c/ed40a48d0a9166edb22e2b8efafea822e93dd79a - https://git.kernel.org/stable/c/92a563fcf14b3093226fb36f12e9b5cf630c5a5d
CVE ID: CVE-2022-50197 State: PUBLISHED Published: 2025-06-18T11:03:40.779Z Last Updated: 2025-06-18T11:03:40.779Z Vendors: Linux Products: Linux Description: 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. References: - https://git.kernel.org/stable/c/f52c9be1779d70037ae300762d19b08fe3656237 - https://git.kernel.org/stable/c/dcbb974254d2a27240c2e50185afdde90f923feb - https://git.kernel.org/stable/c/a530fa52d4fdffc5f010f90c05ac63019b8ff5f8 - https://g
254d2a27240c2e50185afdde90f923feb - https://git.kernel.org/stable/c/a530fa52d4fdffc5f010f90c05ac63019b8ff5f8 - https://git.kernel.org/stable/c/22e6d8bcde8e66b64f46bf9bd2d3d0f88d40c39f - https://git.kernel.org/stable/c/179034fb108e3655142f2af0c309cef171c34d68 - https://git.kernel.org/stable/c/ecefd22d5db7ccb8bec2646e5d25e058fc33162a - https://git.kernel.org/stable/c/3b01353f1825151a29d08e0868b2bf01e1116ab5 - https://git.kernel.org/stable/c/d1ff2559cef0f6f8d97fba6337b28adb10689e16
CVE ID: CVE-2022-50198 State: PUBLISHED Published: 2025-06-18T11:03:41.422Z Last Updated: 2025-06-18T11:03:41.422Z Vendors: Linux Products: Linux Description: 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. References: - https://git.kernel.org/stable/c/c9ec7993d00250a394d367c8a19fcfe8211c258b - https://git.kernel.org/stable/c/c4f92af7fc8cecb8eb426ad187e39c7bcc6679c7 - https://git.kernel.org/stable/c/d294d60dc68550fee0fbbe8a638d798dcd40b2c
ble/c/c4f92af7fc8cecb8eb426ad187e39c7bcc6679c7 - https://git.kernel.org/stable/c/d294d60dc68550fee0fbbe8a638d798dcd40b2c5 - https://git.kernel.org/stable/c/1bf747824a8ca4008879fd7d2ce6b03d7b428858 - https://git.kernel.org/stable/c/e5ab8a4967d68a8e9f8f4559d144207d085a8c02 - https://git.kernel.org/stable/c/c652e0f51665f3fa575449909bbd9d7b45dfab1c - https://git.kernel.org/stable/c/942228fbf5d4901112178b93d41225be7c0dd9de
CVE ID: CVE-2022-50199 State: PUBLISHED Published: 2025-06-18T11:03:42.033Z Last Updated: 2025-06-18T11:03:42.033Z Vendors: Linux Products: Linux Description: 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. References: - https://git.kernel.org/stable/c/935035cf97c8cd6794044b500fb0a44a6d30ffa1 - https://git.kernel.org/stable/c/14bac0c7035bf920e190a63c7e1b113c72eadbf