Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
9e - https://git.kernel.org/stable/c/c29642ba72f87c0a3d7449f7db5d6d76a7ed53c3 - https://git.kernel.org/stable/c/2add538e57a2825c61d639260386f385c75e4166 - https://git.kernel.org/stable/c/c7c0ec5a1dcc3eaa1e85c804c2ccf46e457788a3 - https://git.kernel.org/stable/c/524bb1da785a7ae43dd413cd392b5071c6c367f8
CVE ID: CVE-2022-49176 State: PUBLISHED Published: 2025-02-26T01:55:30.586Z Last Updated: 2025-05-04T08:31:38.713Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: bfq: fix use-after-free in bfq_dispatch_request KASAN reports a use-after-free report when doing normal scsi-mq test [69832.239032] ================================================================== [69832.241810] BUG: KASAN: use-after-free in bfq_dispatch_request+0x1045/0x44b0 [69832.243267] Read of size 8 at addr ffff88802622ba88 by task kworker/3:1H/155 [69832.244656] [69832.245007] CPU: 3 PID: 155 Comm: kworker/3:1H Not tainted 5.10.0-10295-g576c6382529e #8 [69832.
H/155 [69832.244656] [69832.245007] CPU: 3 PID: 155 Comm: kworker/3:1H Not tainted 5.10.0-10295-g576c6382529e #8 [69832.246626] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [69832.249069] Workqueue: kblockd blk_mq_run_work_fn [69832.250022] Call Trace: [69832.250541] dump_stack+0x9b/0xce [69832.251232] ? bfq_dispatch_request+0x1045/0x44b0 [69832.252243] print_address_description.constprop.6+0x3e/0x60 [69832.253381] ? __cpuidle_text_end+0x5/0x5 [69832.254211] ? vprintk_func+0x6b/0x120 [69832.254994] ? bfq_dispatch_request+0x1045/0x44b0 [69832.255952] ? bfq_dispatch_request+0x1045/0x44b0 [69832.256914] kasan_report.cold.9+0
_dispatch_request+0x1045/0x44b0 [69832.255952] ? bfq_dispatch_request+0x1045/0x44b0 [69832.256914] kasan_report.cold.9+0x22/0x3a [69832.257753] ? bfq_dispatch_request+0x1045/0x44b0 [69832.258755] check_memory_region+0x1c1/0x1e0 [69832.260248] bfq_dispatch_request+0x1045/0x44b0 [69832.261181] ? bfq_bfqq_expire+0x2440/0x2440 [69832.262032] ? blk_mq_delay_run_hw_queues+0xf9/0x170 [69832.263022] __blk_mq_do_dispatch_sched+0x52f/0x830 [69832.264011] ? blk_mq_sched_request_inserted+0x100/0x100 [69832.265101] __blk_mq_sched_dispatch_requests+0x398/0x4f0 [69832.266206] ? blk_mq_do_dispatch_ctx+0x570/0x570 [69832.267147] ? __switch_to+0x5f4/0xee0 [69832.267898] blk_mq_sched_dispatch_requests+0xdf/0x1
dispatch_ctx+0x570/0x570 [69832.267147] ? __switch_to+0x5f4/0xee0 [69832.267898] blk_mq_sched_dispatch_requests+0xdf/0x140 [69832.268946] __blk_mq_run_hw_queue+0xc0/0x270 [69832.269840] blk_mq_run_work_fn+0x51/0x60 [69832.278170] process_one_work+0x6d4/0xfe0 [69832.278984] worker_thread+0x91/0xc80 [69832.279726] ? __kthread_parkme+0xb0/0x110 [69832.280554] ? process_one_work+0xfe0/0xfe0 [69832.281414] kthread+0x32d/0x3f0 [69832.282082] ? kthread_park+0x170/0x170 [69832.282849] ret_from_fork+0x1f/0x30 [69832.283573] [69832.283886] Allocated by task 7725: [69832.284599] kasan_save_stack+0x19/0x40 [69832.285385] __kasan_kmalloc.constprop.2+0xc1/0xd0 [69832.286350] kmem_cache_alloc_node+0x13f/0x
_save_stack+0x19/0x40 [69832.285385] __kasan_kmalloc.constprop.2+0xc1/0xd0 [69832.286350] kmem_cache_alloc_node+0x13f/0x460 [69832.287237] bfq_get_queue+0x3d4/0x1140 [69832.287993] bfq_get_bfqq_handle_split+0x103/0x510 [69832.289015] bfq_init_rq+0x337/0x2d50 [69832.289749] bfq_insert_requests+0x304/0x4e10 [69832.290634] blk_mq_sched_insert_requests+0x13e/0x390 [69832.291629] blk_mq_flush_plug_list+0x4b4/0x760 [69832.292538] blk_flush_plug_list+0x2c5/0x480 [69832.293392] io_schedule_prepare+0xb2/0xd0 [69832.294209] io_schedule_timeout+0x13/0x80 [69832.295014] wait_for_common_io.constprop.1+0x13c/0x270 [69832.296137] submit_bio_wait+0x103/0x1a0 [69832.296932] blkdev_issue_discard+0xe6/0x160 [6
_io.constprop.1+0x13c/0x270 [69832.296137] submit_bio_wait+0x103/0x1a0 [69832.296932] blkdev_issue_discard+0xe6/0x160 [69832.297794] blk_ioctl_discard+0x219/0x290 [69832.298614] blkdev_common_ioctl+0x50a/0x1750 [69832.304715] blkdev_ioctl+0x470/0x600 [69832.305474] block_ioctl+0xde/0x120 [69832.306232] vfs_ioctl+0x6c/0xc0 [69832.306877] __se_sys_ioctl+0x90/0xa0 [69832.307629] do_syscall_64+0x2d/0x40 [69832.308362] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [69832.309382] [69832.309701] Freed by task 155: [69832.310328] kasan_save_stack+0x19/0x40 [69832.311121] kasan_set_track+0x1c/0x30 [69832.311868] kasan_set_free_info+0x1b/0x30 [69832.312699] __kasan_slab_free+0x111/0x160 [69832.313524] kmem
+0x1c/0x30 [69832.311868] kasan_set_free_info+0x1b/0x30 [69832.312699] __kasan_slab_free+0x111/0x160 [69832.313524] kmem_cache_free+0x94/0x460 [69832.314367] bfq_put_queue+0x582/0x940 [69832.315112] __bfq_bfqd_reset_in_service+0x166/0x1d0 [69832.317275] bfq_bfqq_expire+0xb27/0x2440 [69832.318084] bfq_dispatch_request+0x697/0x44b0 [69832.318991] __blk_mq_do_dispatch_sched+0x52f/0x830 [69832.319984] __blk_mq_sched_dispatch_requests+0x398/0x4f0 [69832.321087] blk_mq_sched_dispatch_requests+0xdf/0x140 [69832.322225] __blk_mq_run_hw_queue+0xc0/0x270 [69832.323114] blk_mq_run_work_fn+0x51/0x6 ---truncated--- Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/st
k_fn+0x51/0x6 ---truncated--- Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/74e610b5ee0d95e751280567100509eb11517efa - https://git.kernel.org/stable/c/5117c9ff4c2ebae0f5c2c262d42a25a8fbc086e6 - https://git.kernel.org/stable/c/df6e00b1a53c57dca82c63b5ecbcad5452231bc7 - https://git.kernel.org/stable/c/080665e2c3cbfc68359b9a348a3546ed9b908e7a - https://git.kernel.org/stable/c/5687958bf18f84384d809f521210d0f5deed03b0 - https://git.kernel.org/stable/c/40b4ba0030e0b02cbacd424ebb9f4c8b0976c786 - https://git.kernel.org/stable/c/ab552fcb17cc9e4afe0e4ac4df95fc7b30e8490a
CVE ID: CVE-2022-49177 State: PUBLISHED Published: 2025-02-26T01:55:31.078Z Last Updated: 2025-10-01T19:56:59.997Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: hwrng: cavium - fix NULL but dereferenced coccicheck error Fix following coccicheck warning: ./drivers/char/hw_random/cavium-rng-vf.c:182:17-20: ERROR: pdev is NULL but dereferenced. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/e47b12f9415169eceda6770fcf45802e0c8d2a66 - https://git.kernel.org/stable/c/e6205ad58a7ac194abfb33897585b38687d797fa
CVE ID: CVE-2022-49178 State: PUBLISHED Published: 2025-02-26T01:55:31.574Z Last Updated: 2025-05-04T08:31:41.270Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: memstick/mspro_block: fix handling of read-only devices Use set_disk_ro to propagate the read-only state to the block layer instead of checking for it in ->open and leaking a reference in case of a read-only device. References: - https://git.kernel.org/stable/c/057b53c4f87690d626203acef8b63d52a9bf2f43 - https://git.kernel.org/stable/c/6a0725b9d78ff6efdc95a37e4f05072e79c63918 - https://git.kernel.org/stable/c/6dab421bfe06a59bf8f212a72e34673e8acf2018
CVE ID: CVE-2022-49179 State: PUBLISHED Published: 2025-02-26T01:55:32.100Z Last Updated: 2025-05-04T08:31:42.491Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: block, bfq: don't move oom_bfqq Our test report a UAF: [ 2073.019181] ================================================================== [ 2073.019188] BUG: KASAN: use-after-free in __bfq_put_async_bfqq+0xa0/0x168 [ 2073.019191] Write of size 8 at addr ffff8000ccf64128 by task rmmod/72584 [ 2073.019192] [ 2073.019196] CPU: 0 PID: 72584 Comm: rmmod Kdump: loaded Not tainted 4.19.90-yk #5 [ 2073.019198] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 207
mp: loaded Not tainted 4.19.90-yk #5 [ 2073.019198] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 2073.019200] Call trace: [ 2073.019203] dump_backtrace+0x0/0x310 [ 2073.019206] show_stack+0x28/0x38 [ 2073.019210] dump_stack+0xec/0x15c [ 2073.019216] print_address_description+0x68/0x2d0 [ 2073.019220] kasan_report+0x238/0x2f0 [ 2073.019224] __asan_store8+0x88/0xb0 [ 2073.019229] __bfq_put_async_bfqq+0xa0/0x168 [ 2073.019233] bfq_put_async_queues+0xbc/0x208 [ 2073.019236] bfq_pd_offline+0x178/0x238 [ 2073.019240] blkcg_deactivate_policy+0x1f0/0x420 [ 2073.019244] bfq_exit_queue+0x128/0x178 [ 2073.019249] blk_mq_exit_sched+0x12c/0x160 [ 2073.019252] elevator_exit+0xc8/0xd0 [
019244] bfq_exit_queue+0x128/0x178 [ 2073.019249] blk_mq_exit_sched+0x12c/0x160 [ 2073.019252] elevator_exit+0xc8/0xd0 [ 2073.019256] blk_exit_queue+0x50/0x88 [ 2073.019259] blk_cleanup_queue+0x228/0x3d8 [ 2073.019267] null_del_dev+0xfc/0x1e0 [null_blk] [ 2073.019274] null_exit+0x90/0x114 [null_blk] [ 2073.019278] __arm64_sys_delete_module+0x358/0x5a0 [ 2073.019282] el0_svc_common+0xc8/0x320 [ 2073.019287] el0_svc_handler+0xf8/0x160 [ 2073.019290] el0_svc+0x10/0x218 [ 2073.019291] [ 2073.019294] Allocated by task 14163: [ 2073.019301] kasan_kmalloc+0xe0/0x190 [ 2073.019305] kmem_cache_alloc_node_trace+0x1cc/0x418 [ 2073.019308] bfq_pd_alloc+0x54/0x118 [ 2073.019313] blkcg_activate_policy+0x2
kmem_cache_alloc_node_trace+0x1cc/0x418 [ 2073.019308] bfq_pd_alloc+0x54/0x118 [ 2073.019313] blkcg_activate_policy+0x250/0x460 [ 2073.019317] bfq_create_group_hierarchy+0x38/0x110 [ 2073.019321] bfq_init_queue+0x6d0/0x948 [ 2073.019325] blk_mq_init_sched+0x1d8/0x390 [ 2073.019330] elevator_switch_mq+0x88/0x170 [ 2073.019334] elevator_switch+0x140/0x270 [ 2073.019338] elv_iosched_store+0x1a4/0x2a0 [ 2073.019342] queue_attr_store+0x90/0xe0 [ 2073.019348] sysfs_kf_write+0xa8/0xe8 [ 2073.019351] kernfs_fop_write+0x1f8/0x378 [ 2073.019359] __vfs_write+0xe0/0x360 [ 2073.019363] vfs_write+0xf0/0x270 [ 2073.019367] ksys_write+0xdc/0x1b8 [ 2073.019371] __arm64_sys_write+0x50/0x60 [ 2073.019375] el0
vfs_write+0xf0/0x270 [ 2073.019367] ksys_write+0xdc/0x1b8 [ 2073.019371] __arm64_sys_write+0x50/0x60 [ 2073.019375] el0_svc_common+0xc8/0x320 [ 2073.019380] el0_svc_handler+0xf8/0x160 [ 2073.019383] el0_svc+0x10/0x218 [ 2073.019385] [ 2073.019387] Freed by task 72584: [ 2073.019391] __kasan_slab_free+0x120/0x228 [ 2073.019394] kasan_slab_free+0x10/0x18 [ 2073.019397] kfree+0x94/0x368 [ 2073.019400] bfqg_put+0x64/0xb0 [ 2073.019404] bfqg_and_blkg_put+0x90/0xb0 [ 2073.019408] bfq_put_queue+0x220/0x228 [ 2073.019413] __bfq_put_async_bfqq+0x98/0x168 [ 2073.019416] bfq_put_async_queues+0xbc/0x208 [ 2073.019420] bfq_pd_offline+0x178/0x238 [ 2073.019424] blkcg_deactivate_policy+0x1f0/0x420 [ 2073.
c_queues+0xbc/0x208 [ 2073.019420] bfq_pd_offline+0x178/0x238 [ 2073.019424] blkcg_deactivate_policy+0x1f0/0x420 [ 2073.019429] bfq_exit_queue+0x128/0x178 [ 2073.019433] blk_mq_exit_sched+0x12c/0x160 [ 2073.019437] elevator_exit+0xc8/0xd0 [ 2073.019440] blk_exit_queue+0x50/0x88 [ 2073.019443] blk_cleanup_queue+0x228/0x3d8 [ 2073.019451] null_del_dev+0xfc/0x1e0 [null_blk] [ 2073.019459] null_exit+0x90/0x114 [null_blk] [ 2073.019462] __arm64_sys_delete_module+0x358/0x5a0 [ 2073.019467] el0_svc_common+0xc8/0x320 [ 2073.019471] el0_svc_handler+0xf8/0x160 [ 2073.019474] el0_svc+0x10/0x218 [ 2073.019475] [ 2073.019479] The buggy address belongs to the object at ffff8000ccf63f00 which belongs to th
0x10/0x218 [ 2073.019475] [ 2073.019479] The buggy address belongs to the object at ffff8000ccf63f00 which belongs to the cache kmalloc-1024 of size 1024 [ 2073.019484] The buggy address is located 552 bytes inside of 1024-byte region [ffff8000ccf63f00, ffff8000ccf64300) [ 2073.019486] The buggy address belongs to the page: [ 2073.019492] page:ffff7e000333d800 count:1 mapcount:0 mapping:ffff8000c0003a00 index:0x0 compound_mapcount: 0 [ 2073.020123] flags: 0x7ffff0000008100(slab|head) [ 2073.020403] raw: 07ffff0000008100 ffff7e0003334c08 ffff7e00001f5a08 ffff8000c0003a00 [ 2073.020409] ra ---truncated--- Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/s
073.020409] ra ---truncated--- Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/c4f5a678add58a8a0e7ee5e038496b376ea6d205 - https://git.kernel.org/stable/c/7507ead1e9d42957c2340f2c4a0e9d00034e3366 - https://git.kernel.org/stable/c/8f34dea99cd7761156a146a5258a67d045d862f7 - https://git.kernel.org/stable/c/87fdfe8589d43e471dffb4c60f75eeb6f37afc4c - https://git.kernel.org/stable/c/c01fced8d38fbccc82787065229578006f28e020 - https://git.kernel.org/stable/c/8410f70977734f21b8ed45c37e925d311dfda2e7
CVE ID: CVE-2022-49180 State: PUBLISHED Published: 2025-02-26T01:55:32.590Z Last Updated: 2025-05-04T08:31:43.686Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: LSM: general protection fault in legacy_parse_param The usual LSM hook "bail on fail" scheme doesn't work for cases where a security module may return an error code indicating that it does not recognize an input. In this particular case Smack sees a mount option that it recognizes, and returns 0. A call to a BPF hook follows, which returns -ENOPARAM, which confuses the caller because Smack has processed its data. The SELinux hook incorrectly returns 1 on success. There
which confuses the caller because Smack has processed its data. The SELinux hook incorrectly returns 1 on success. There was a time when this was correct, however the current expectation is that it return 0 on success. This is repaired. References: - https://git.kernel.org/stable/c/ddcdda888e14ca451b3ee83d11b65b2a9c8e783b - https://git.kernel.org/stable/c/2784604c8c6fc523248f8f80a421c313a9d790b7 - https://git.kernel.org/stable/c/f3f93a1aaafc3032e0a9655fb43deccfb3e953a3 - https://git.kernel.org/stable/c/00fc07fa0b4a004711b6e1a944f0d2e46f7093b7 - https://git.kernel.org/stable/c/cadae7c5e477aaafcba819b8e4a3d1c1a1503b62 - https://git.kernel.org/stable/c/ecff30575b5ad0eda149aadad247b7f75411fd47
CVE ID: CVE-2022-49181 State: REJECTED Published: 2025-02-26T01:55:33.094Z Last Updated: 2025-02-26T11:30:08.128Z Description: No description available.
CVE ID: CVE-2022-49182 State: PUBLISHED Published: 2025-02-26T01:55:33.574Z Last Updated: 2025-05-04T08:31:45.489Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: hns3: add vlan list lock to protect vlan list When adding port base VLAN, vf VLAN need to remove from HW and modify the vlan state in vf VLAN list as false. If the periodicity task is freeing the same node, it may cause "use after free" error. This patch adds a vlan list lock to protect the vlan list. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/30f0ff7176efe8ac6c55f85bce26ed58bb608758 - https://git.kernel.org/st
ment: References: - https://git.kernel.org/stable/c/30f0ff7176efe8ac6c55f85bce26ed58bb608758 - https://git.kernel.org/stable/c/09e383ca97e798f9954189b741af54b5c51e7a97 - https://git.kernel.org/stable/c/f58af41deeab0f45c9c80adf5f2de489ebbac3dd - https://git.kernel.org/stable/c/1932a624ab88ff407d1a1d567fe581faa15dc725
CVE ID: CVE-2022-49183 State: PUBLISHED Published: 2025-02-26T01:55:34.041Z Last Updated: 2025-10-01T19:56:59.861Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net/sched: act_ct: fix ref leak when switching zones When switching zones or network namespaces without doing a ct clear in between, it is now leaking a reference to the old ct entry. That's because tcf_ct_skb_nfct_cached() returns false and tcf_ct_flow_table_lookup() may simply overwrite it. The fix is to, as the ct entry is not reusable, free it already at tcf_ct_skb_nfct_cached(). Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.or
eady at tcf_ct_skb_nfct_cached(). Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/bcbf4e5c3b5b373cd61528392dd1ec8e9c0fd33d - https://git.kernel.org/stable/c/4bb42d73def9411e5cad885b9811987d72431df1 - https://git.kernel.org/stable/c/b24793a37d91aacad7cb9893b226a7924a89636a - https://git.kernel.org/stable/c/bcb74e132a76ce0502bb33d5b65533a4ed72d159
CVE ID: CVE-2022-49184 State: PUBLISHED Published: 2025-02-26T01:55:34.554Z Last Updated: 2025-10-01T19:56:59.722Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: sparx5: switchdev: fix possible NULL pointer dereference As the possible failure of the allocation, devm_kzalloc() may return NULL pointer. Therefore, it should be better to check the 'db' in order to prevent the dereference of NULL pointer. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/b375ea083fa649092cd016ac1f89a2d1fd8f8e8b - https://git.kernel.org/stable/c/c346791877e6ce923bb21e34b30c6f99326aa5a8 - https://git
fa649092cd016ac1f89a2d1fd8f8e8b - https://git.kernel.org/stable/c/c346791877e6ce923bb21e34b30c6f99326aa5a8 - https://git.kernel.org/stable/c/e7e1fff76c4c57688dc7d53a3b6212182d5628d0 - https://git.kernel.org/stable/c/0906f3a3df07835e37077d8971aac65347f2ed57
CVE ID: CVE-2022-49185 State: PUBLISHED Published: 2025-02-26T01:55:35.068Z Last Updated: 2025-10-01T19:56:59.497Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: pinctrl: nomadik: Add missing of_node_put() in nmk_pinctrl_probe This node pointer is returned by of_parse_phandle() with refcount incremented in this function. Calling of_node_put() to avoid the refcount leak. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/59250d547542f1c7765a78dc97ddfe5e6b0d2ab0 - https://git.kernel.org/stable/c/0356d4b64a03d23daf99a2a29d7d7d91d6ec2ea8 - https://git.kernel.org/stable/c/0067ba448f1c29c
tps://git.kernel.org/stable/c/0356d4b64a03d23daf99a2a29d7d7d91d6ec2ea8 - https://git.kernel.org/stable/c/0067ba448f1c29ca06e5aee00d8506889ed1f9d0 - https://git.kernel.org/stable/c/bc1e29a35147c1ba6ea2b06a16cb0028f7c852d2 - https://git.kernel.org/stable/c/669b05ff43bd7ed684379c6e2006a6dad5127b71 - https://git.kernel.org/stable/c/c52703355766c347f270df222a744e0c491a02f2 - https://git.kernel.org/stable/c/9511c6018cd772668def8b034bc67269847e591a - https://git.kernel.org/stable/c/62580a40c9bef3d8a90629c64dda381344b35ffd - https://git.kernel.org/stable/c/c09ac191b1f97cfa06f394dbfd7a5db07986cefc
CVE ID: CVE-2022-49186 State: PUBLISHED Published: 2025-02-26T01:55:35.590Z Last Updated: 2025-10-01T19:56:59.343Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: clk: visconti: prevent array overflow in visconti_clk_register_gates() This code was using -1 to represent that there was no reset function. Unfortunately, the -1 was stored in u8 so the if (clks[i].rs_id >= 0) condition was always true. This lead to an out of bounds access in visconti_clk_register_gates(). Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/2723543c1d60278d5aef1c4ad732dbad24b84a81 - https://git.kernel.org/s
hment: References: - https://git.kernel.org/stable/c/2723543c1d60278d5aef1c4ad732dbad24b84a81 - https://git.kernel.org/stable/c/c5601e0720ce1a3ad895f94a5838530edde01ed3
CVE ID: CVE-2022-49187 State: PUBLISHED Published: 2025-02-26T01:55:36.094Z Last Updated: 2025-10-01T19:56:59.191Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: clk: Fix clk_hw_get_clk() when dev is NULL Any registered clk_core structure can have a NULL pointer in its dev field. While never actually documented, this is evidenced by the wide usage of clk_register and clk_hw_register with a NULL device pointer, and the fact that the core of_clk_hw_register() function also passes a NULL device pointer. A call to clk_hw_get_clk() on a clk_hw struct whose clk_core is in that case will result in a NULL pointer derefence when it call
clk_hw_get_clk() on a clk_hw struct whose clk_core is in that case will result in a NULL pointer derefence when it calls dev_name() on that NULL device pointer. Add a test for this case and use NULL as the dev_id if the device pointer is NULL. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/4be3e4c05d8dd1b83b75652cad88c9e752ec7054 - https://git.kernel.org/stable/c/d183f20cf5a7b546d4108e796b98210ceb317579 - https://git.kernel.org/stable/c/23f89fe005b105f0dcc55034c13eb89f9b570fac - https://git.kernel.org/stable/c/0c1b56df451716ba207bbf59f303473643eee4fd
CVE ID: CVE-2022-49188 State: PUBLISHED Published: 2025-02-26T01:55:36.582Z Last Updated: 2025-05-04T08:31:52.927Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: remoteproc: qcom_q6v5_mss: Fix some leaks in q6v5_alloc_memory_region The device_node pointer is returned by of_parse_phandle() or of_get_child_by_name() with refcount incremented. We should use of_node_put() on it when done. This function only call of_node_put(node) when of_address_to_resource succeeds, missing error cases. References: - https://git.kernel.org/stable/c/f7210ca29a783c94478da02368731e4c9cf7cdb7 - https://git.kernel.org/stable/c/bd4771ba2cf9e18473a42b5b7
kernel.org/stable/c/f7210ca29a783c94478da02368731e4c9cf7cdb7 - https://git.kernel.org/stable/c/bd4771ba2cf9e18473a42b5b70175e50d67a64bb - https://git.kernel.org/stable/c/a7d988735e757e111f9722de7cf1b40a84a48b1f - https://git.kernel.org/stable/c/b9df3007b3cda4936cc50f5a7d2d30505a652828 - https://git.kernel.org/stable/c/07a5dcc4bed9d7cae54adf5aa10ff9f037a3204b
CVE ID: CVE-2022-49189 State: PUBLISHED Published: 2025-02-26T01:55:37.095Z Last Updated: 2025-05-04T08:31:54.404Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: clk: qcom: clk-rcg2: Update logic to calculate D value for RCG The display pixel clock has a requirement on certain newer platforms to support M/N as (2/3) and the final D value calculated results in underflow errors. As the current implementation does not check for D value is within the accepted range for a given M & N value. Update the logic to calculate the final D value based on the range. References: - https://git.kernel.org/stable/c/52592f9afbfe01bce8f8953e4f19cb
ulate the final D value based on the range. References: - https://git.kernel.org/stable/c/52592f9afbfe01bce8f8953e4f19cbe3bcbdbd3a - https://git.kernel.org/stable/c/334720f418f57b1d969dad2117b21f9388cb9395 - https://git.kernel.org/stable/c/34dca60982e93e69ae442aa2d36ce61c9a3bb563 - https://git.kernel.org/stable/c/96888f0dcf351e758b9df57e015a48427ca709c1 - https://git.kernel.org/stable/c/a4e2e31971354790b0d1fa3e783452a9d135fcff - https://git.kernel.org/stable/c/58922910add18583d5273c2edcdb9fd7bf4eca02
CVE ID: CVE-2022-49190 State: PUBLISHED Published: 2025-02-26T01:55:37.629Z Last Updated: 2025-11-03T19:27:48.713Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: kernel/resource: fix kfree() of bootmem memory again Since commit ebff7d8f270d ("mem hotunplug: fix kfree() of bootmem memory"), we could get a resource allocated during boot via alloc_resource(). And it's required to release the resource using free_resource(). Howerver, many people use kfree directly which will result in kernel BUG. In order to fix this without fixing every call site, just leak a couple of bytes in such corner case. Additional Analyst Notes: - CVE Pro
his without fixing every call site, just leak a couple of bytes in such corner case. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/3379a60f6bb4afcd9c456e340ac525ae649d3ce7 - https://git.kernel.org/stable/c/a9e88c2618d228d7a4e7e515cf30dc0d0d813f27 - https://git.kernel.org/stable/c/d7faa04a44a0c37ac3d222fa8e0bdcbfcee9c0c8 - https://git.kernel.org/stable/c/ab86020070999e758ce2e60c4348f20bf7ddba56 - https://git.kernel.org/stable/c/0cbcc92917c5de80f15c24d033566539ad696892