Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
8 83 f8 0a 0f 86 c1 00 00 00 44 39 c1 7f 10 48 89 df RIP: backport_rdma_dim+0x10e/0x240 [mlx_compat] RSP: ffff880c10e83ec0 Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/5af106f8e072aebd88b95e164a08fa320651a99a - https://git.kernel.org/stable/c/fae2a9fb1eaf348ad8732f90d42ebbb971bd7e95 - https://git.kernel.org/stable/c/0b6e0eb5c45e79e9095de2498cc0ca5ec563fc5e - https://git.kernel.org/stable/c/7c1963391af51ee322378d1b2849c60e9037f069 - https://git.kernel.org/stable/c/0fe3dbbefb74a8575f61d7801b08dbc50523d60d
CVE ID: CVE-2022-49671 State: PUBLISHED Published: 2025-02-26T02:24:04.608Z Last Updated: 2025-10-01T19:36:47.464Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: RDMA/cm: Fix memory leak in ib_cm_insert_listen cm_alloc_id_priv() allocates resource for the cm_id_priv. When cm_init_listen() fails it doesn't free it, leading to memory leak. Add the missing error unwind. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/b0cab8b517aeaf2592c3479294f934209c41a26f - https://git.kernel.org/stable/c/889000874c1204e47c7f2a4945db262a47e7efc9 - https://git.kernel.org/stable/c/2febf09a8a8ae4accf
://git.kernel.org/stable/c/889000874c1204e47c7f2a4945db262a47e7efc9 - https://git.kernel.org/stable/c/2febf09a8a8ae4accf908f043f1bab1421056568 - https://git.kernel.org/stable/c/2990f223ffa7bb25422956b9f79f9176a5b38346
CVE ID: CVE-2022-49672 State: PUBLISHED Published: 2025-02-26T02:24:05.284Z Last Updated: 2025-05-04T08:43:01.207Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: tun: unlink NAPI from device on destruction Syzbot found a race between tun file and device destruction. NAPIs live in struct tun_file which can get destroyed before the netdev so we have to del them explicitly. The current code is missing deleting the NAPI if the queue was detached first. References: - https://git.kernel.org/stable/c/82e729aee59acefe135fceffadcbc5b86dd4f1b9 - https://git.kernel.org/stable/c/a8cf919022373c97a84fe596bbea544f909c485d - https://git.k
acefe135fceffadcbc5b86dd4f1b9 - https://git.kernel.org/stable/c/a8cf919022373c97a84fe596bbea544f909c485d - https://git.kernel.org/stable/c/bec1be0a745ab420718217e3e0d9542a75108989 - https://git.kernel.org/stable/c/8145f77d38de4f88b8a69e1463f5c09ba189d77c - https://git.kernel.org/stable/c/8661d4b8faa2f7ee7a559969c0a7c57f077b1728 - https://git.kernel.org/stable/c/3b9bc84d311104906d2b4995a9a02d7b7ddab2db
CVE ID: CVE-2022-49673 State: PUBLISHED Published: 2025-02-26T02:24:05.945Z Last Updated: 2025-05-04T08:43:02.339Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: dm raid: fix KASAN warning in raid5_add_disks There's a KASAN warning in raid5_add_disk when running the LVM testsuite. The warning happens in the test lvconvert-raid-reshape-linear_to_raid6-single-type.sh. We fix the warning by verifying that rdev->saved_raid_disk is within limits. References: - https://git.kernel.org/stable/c/2d4e7c9898c20fb3d3f55381cab601761aab7d64 - https://git.kernel.org/stable/c/2fb2928728038280bd925ce2aafb4997e9d47ee9 - https://git.kernel.org/st
1cab601761aab7d64 - https://git.kernel.org/stable/c/2fb2928728038280bd925ce2aafb4997e9d47ee9 - https://git.kernel.org/stable/c/3553a69bb52be2deba61d0ca064c41aee842bb35 - https://git.kernel.org/stable/c/f157bd9cf377a947fdb7035e69466b6ecdc17c17 - https://git.kernel.org/stable/c/d8bca518d5272fe349e0a722fdb9e3acb661f3f0 - https://git.kernel.org/stable/c/d5b06039b195d4b6f94f5d345b1e4ac1975a9832 - https://git.kernel.org/stable/c/02cffb1921edadd9b6e4eee7ada4a5213e8ba12e - https://git.kernel.org/stable/c/617b365872a247480e9dcd50a32c8d1806b21861
CVE ID: CVE-2022-49674 State: PUBLISHED Published: 2025-02-26T02:24:06.636Z Last Updated: 2025-05-04T08:43:03.651Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: dm raid: fix accesses beyond end of raid member array On dm-raid table load (using raid_ctr), dm-raid allocates an array rs->devs[rs->raid_disks] for the raid device members. rs->raid_disks is defined by the number of raid metadata and image tupples passed into the target's constructor. In the case of RAID layout changes being requested, that number can be different from the current number of members for existing raid sets as defined in their superblocks. Example RAID
an be different from the current number of members for existing raid sets as defined in their superblocks. Example RAID layout changes include: - raid1 legs being added/removed - raid4/5/6/10 number of stripes changed (stripe reshaping) - takeover to higher raid level (e.g. raid5 -> raid6) When accessing array members, rs->raid_disks must be used in control loops instead of the potentially larger value in rs->md.raid_disks. Otherwise it will cause memory access beyond the end of the rs->devs array. Fix this by changing code that is prone to out-of-bounds access. Also fix validate_raid_redundancy() to validate all devices that are added. Also, use braces to help clean up raid_iterate_devices(
lidate_raid_redundancy() to validate all devices that are added. Also, use braces to help clean up raid_iterate_devices(). The out-of-bounds memory accesses was discovered using KASAN. This commit was verified to pass all LVM2 RAID tests (with KASAN enabled). References: - https://git.kernel.org/stable/c/5e161a8826b63c0b8b43e4a7fad1f956780f42ab - https://git.kernel.org/stable/c/df1a5ab0dd0775f2ea101c71f2addbc4c0ea0f85 - https://git.kernel.org/stable/c/90de15357504c8097ab29769dc6852e16281e9e8 - https://git.kernel.org/stable/c/9bf2b0757b04c78dc5d6e3a198acca98457b32a1 - https://git.kernel.org/stable/c/6352b2f4d8e95ec0ae576d7705435d64cfa29503 - https://git.kernel.org/stable/c/bcff98500ea3b4e7615
//git.kernel.org/stable/c/6352b2f4d8e95ec0ae576d7705435d64cfa29503 - https://git.kernel.org/stable/c/bcff98500ea3b4e7615ec31d2bdd326bc1ef5134 - https://git.kernel.org/stable/c/332bd0778775d0cf105c4b9e03e460b590749916
CVE ID: CVE-2022-49675 State: PUBLISHED Published: 2025-02-26T02:24:07.395Z Last Updated: 2025-05-04T08:43:04.795Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: tick/nohz: unexport __init-annotated tick_nohz_full_setup() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic. modpost used to detect it, but it had been broken for a decade. Commit 28438794aba4 ("modpost: fix section mismatch check for exported init/exit sections") fixed it so modpost started to
mit 28438794aba4 ("modpost: fix section mismatch check for exported init/exit sections") fixed it so modpost started to warn it again, then this showed up: MODPOST vmlinux.symvers WARNING: modpost: vmlinux.o(___ksymtab_gpl+tick_nohz_full_setup+0x0): Section mismatch in reference from the variable __ksymtab_tick_nohz_full_setup to the function .init.text:tick_nohz_full_setup() The symbol tick_nohz_full_setup is exported and annotated __init Fix this by removing the __init annotation of tick_nohz_full_setup or drop the export. Drop the export because tick_nohz_full_setup() is only called from the built-in code in kernel/sched/isolation.c. References: - https://git.kernel.org/stable/c/c4ff3ffe0
only called from the built-in code in kernel/sched/isolation.c. References: - https://git.kernel.org/stable/c/c4ff3ffe0138234774602152fe67e3a898c615c6 - https://git.kernel.org/stable/c/f4a80ec8c51d68be4b7a7830c510f75080c5e417 - https://git.kernel.org/stable/c/ea32b27e2f8c58c92bff5ecba7fcf64b97707089 - https://git.kernel.org/stable/c/2390095113e98fc52fffe35c5206d30d9efe3f78
CVE ID: CVE-2022-49676 State: PUBLISHED Published: 2025-02-26T02:24:07.905Z Last Updated: 2025-10-01T19:36:47.324Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: memory: samsung: exynos5422-dmc: Fix refcount leak in of_get_dram_timings of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. This function doesn't call of_node_put() in some error paths. To unify the structure, Add put_node label and goto it on errors. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/889aad2203e09eed2071ca8985c25e9d6aea5735 - https
- CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/889aad2203e09eed2071ca8985c25e9d6aea5735 - https://git.kernel.org/stable/c/cde4480b5ab06195b9164184b0c02ced71e601b4 - https://git.kernel.org/stable/c/bb2a481778c60f912c363e271ae46b55ff8132db - https://git.kernel.org/stable/c/1332661e09304b7b8e84e5edc11811ba08d12abe
CVE ID: CVE-2022-49677 State: PUBLISHED Published: 2025-02-26T02:24:08.366Z Last Updated: 2025-10-01T19:36:47.093Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ARM: cns3xxx: Fix refcount leak in cns3xxx_init 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. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/b8b84e01ca94e2e1f5492353e9c24dab520b2e5b - https://git.kernel.org/stable/c/45bebbc8cea7d586a6216dc62814bdb380b9b29b - https://git.kernel.org/stable/c/68d4303
e5b - https://git.kernel.org/stable/c/45bebbc8cea7d586a6216dc62814bdb380b9b29b - https://git.kernel.org/stable/c/68d4303bf59662b64bd555e2aa0518282d20aa4f - https://git.kernel.org/stable/c/d1359e4129ad43e43972a28838b87291c51de23d - https://git.kernel.org/stable/c/c980392af1473d6d5662f70d8089c8e6d85144a4 - https://git.kernel.org/stable/c/da3ee7cd2f15922ad88a7ca6deee2eafdc7cd214 - https://git.kernel.org/stable/c/dc5170aae24e04068fd5ea125d06c0ab51f48a27 - https://git.kernel.org/stable/c/1ba904b6b16e08de5aed7c1349838d9cd0d178c5
CVE ID: CVE-2022-49678 State: PUBLISHED Published: 2025-02-26T02:24:08.833Z Last Updated: 2025-10-01T19:36:46.972Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe 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. In brcmstb_init_sram, it pass dn to of_address_to_resource(), of_address_to_resource() will call of_find_device_by_node() to take reference, so we should release the reference returned by of_find_matching_node(). Additional
d_device_by_node() to take reference, so we should release the reference returned by of_find_matching_node(). Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/4f5877bdf7b593e988f1924f4c3df6523f80b39c - https://git.kernel.org/stable/c/734a4d15142bb4c8ecad2d8ec70d7564e78ae34d - https://git.kernel.org/stable/c/30bbfeb480ae8b5ee43199d72417b232590440c2 - https://git.kernel.org/stable/c/10ba9d499a9fd82ed40897e734ba19870a879407 - https://git.kernel.org/stable/c/dcafd5463d8f20c4f90ddc138a5738adb99f74c8 - https://git.kernel.org/stable/c/37d838de369b07b596c19ff3662bf0293fdb09ee
CVE ID: CVE-2022-49679 State: PUBLISHED Published: 2025-02-26T02:24:09.299Z Last Updated: 2025-10-01T19:36:46.842Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ARM: Fix refcount leak in axxia_boot_secondary 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. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/a9b76c232a1ce4cbf27862097f7eb634dcc779eb - https://git.kernel.org/stable/c/b385cb59aac8d61c29bc72ebf3d19a536914af96 - https://git.kernel.org/stable/c/71e12e5b
eb - https://git.kernel.org/stable/c/b385cb59aac8d61c29bc72ebf3d19a536914af96 - https://git.kernel.org/stable/c/71e12e5b02674459a24f16e965255d63b31fe049 - https://git.kernel.org/stable/c/29ca9c4efacccdc15104a8d4bf10b5183fc92840 - https://git.kernel.org/stable/c/44a5b3a073e5aaa5720929dba95b2725eb32bb65 - https://git.kernel.org/stable/c/4d9c60e868f7cf8e09956e7d5bb44d807d712699 - https://git.kernel.org/stable/c/3c19fe3f04f4f4e7a2b722c2fd3c98356fc1d72b - https://git.kernel.org/stable/c/7c7ff68daa93d8c4cdea482da4f2429c0398fcde
CVE ID: CVE-2022-49680 State: PUBLISHED Published: 2025-02-26T02:24:09.762Z Last Updated: 2025-10-01T19:36:46.715Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ARM: exynos: Fix refcount leak in exynos_map_pmu 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. of_node_put() checks null pointer. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/545ae5cbae839ce39bfe09828e413f1c916082de - https://git.kernel.org/stable/c/31d09571bb071c20f6bdc0bb7ac1ef8dd298
stable/c/545ae5cbae839ce39bfe09828e413f1c916082de - https://git.kernel.org/stable/c/31d09571bb071c20f6bdc0bb7ac1ef8dd2987c04 - https://git.kernel.org/stable/c/7571bcecf01b69f0d3ec60ca41ce5d4c75411a4a - https://git.kernel.org/stable/c/f9b77a52937582a5b99a5a07e4ef1e2f48f87347 - https://git.kernel.org/stable/c/68f28d52e6cbab8dcfa249cac4356d1d0573e868 - https://git.kernel.org/stable/c/d23f76018e17618559da9eea179d137362023f95 - https://git.kernel.org/stable/c/fc354856e9fad9cd36e2ad28f9da70716025055a - https://git.kernel.org/stable/c/c4c79525042a4a7df96b73477feaf232fe44ae81
CVE ID: CVE-2022-49681 State: PUBLISHED Published: 2025-02-26T02:24:10.231Z Last Updated: 2025-10-01T19:36:46.582Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: xtensa: xtfpga: Fix refcount leak bug in setup In machine_setup(), of_find_compatible_node() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/b12d5c52f073a0420622aaf2f21b615cce8b36cc - https://git.kernel.org/stable/c/35d7e961be68732eb3acaeba81fb81ca16eafd05 - https://git.kernel.org/stable/c/0715d0e60052662c3f2253
it.kernel.org/stable/c/35d7e961be68732eb3acaeba81fb81ca16eafd05 - https://git.kernel.org/stable/c/0715d0e60052662c3f225342062f174dd721d1c7 - https://git.kernel.org/stable/c/a52972ee706b438302eb0350e61f378eb191e3d1 - https://git.kernel.org/stable/c/6c0839cf1b9e1b3c88da6af76794583cbfae8da3 - https://git.kernel.org/stable/c/0162451723178602c37f0555d235dfa17e486112 - https://git.kernel.org/stable/c/9b30c5c8884eda3f541229899671cebbad15979b - https://git.kernel.org/stable/c/173940b3ae40114d4179c251a98ee039dc9cd5b3
CVE ID: CVE-2022-49682 State: PUBLISHED Published: 2025-02-26T02:24:10.703Z Last Updated: 2025-10-01T19:36:46.447Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: xtensa: Fix refcount leak bug in time.c In calibrate_ccount(), of_find_compatible_node() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/3e5eb904d9ba657308fc75a5de434b0e58dcb8d7 - https://git.kernel.org/stable/c/7de4502af68f4f3932f450157f5483eb7b33cb74 - https://git.kernel.org/stable/c/f1eaf4ba5372ad111f687a80c6
ernel.org/stable/c/7de4502af68f4f3932f450157f5483eb7b33cb74 - https://git.kernel.org/stable/c/f1eaf4ba5372ad111f687a80c67e270708e14c23 - https://git.kernel.org/stable/c/e5234a9d64a976abd134a14710dcd5188158a7c5 - https://git.kernel.org/stable/c/af0ff2da01521144bc11194f4c26485d7c9cee73 - https://git.kernel.org/stable/c/0dcc1dd8a5dd9240639f1051dfaa2dffc9fbbde5 - https://git.kernel.org/stable/c/0e403a383c14b63c86bd9df085b7e573e9caee64 - https://git.kernel.org/stable/c/a0117dc956429f2ede17b323046e1968d1849150
CVE ID: CVE-2022-49683 State: PUBLISHED Published: 2025-02-26T02:24:11.201Z Last Updated: 2025-10-01T19:36:46.309Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: iio: adc: adi-axi-adc: Fix refcount leak in adi_axi_adc_attach_client 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. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/501652a2ad5450b4908e1f204ce75b2414c305b7 - https://git.kernel.org/stable/c/ab7bf025cee89db73c649216ddd2bc589c3d3862 - https://git.
5450b4908e1f204ce75b2414c305b7 - https://git.kernel.org/stable/c/ab7bf025cee89db73c649216ddd2bc589c3d3862 - https://git.kernel.org/stable/c/5eaa84e1605035a90a64d25b6cba79e89d188175 - https://git.kernel.org/stable/c/ada7b0c0dedafd7d059115adf49e48acba3153a8
CVE ID: CVE-2022-49684 State: PUBLISHED Published: 2025-02-26T02:24:11.677Z Last Updated: 2025-10-01T19:36:46.177Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: iio: adc: aspeed: Fix refcount leak in aspeed_adc_set_trim_data of_find_node_by_name() 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. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/9664491db50a84be92696c8fad2c3b49a7a5f36f - https://git.kernel.org/stable/c/8a2b6b5687984a010ed094b4f436a2f091987758
CVE ID: CVE-2022-49685 State: PUBLISHED Published: 2025-02-26T02:24:12.143Z Last Updated: 2025-05-04T08:43:17.291Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: iio: trigger: sysfs: fix use-after-free on remove Ensure that the irq_work has completed before the trigger is freed. ================================================================== BUG: KASAN: use-after-free in irq_work_run_list Read of size 8 at addr 0000000064702248 by task python3/25 Call Trace: irq_work_run_list irq_work_tick update_process_times tick_sched_handle tick_sched_timer __hrtimer_run_queues hrtimer_interrupt Allocated by task 25: kmem_cache_alloc_tra
mes tick_sched_handle tick_sched_timer __hrtimer_run_queues hrtimer_interrupt Allocated by task 25: kmem_cache_alloc_trace iio_sysfs_trig_add dev_attr_store sysfs_kf_write kernfs_fop_write_iter new_sync_write vfs_write ksys_write sys_write Freed by task 25: kfree iio_sysfs_trig_remove dev_attr_store sysfs_kf_write kernfs_fop_write_iter new_sync_write vfs_write ksys_write sys_write ================================================================== Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/d6111e7bdb8ec27eb43d01c4cd4ff1620a75f7f2 - https://git.kernel.org/stable/c/fd5d8fb298a2866c337da635c79d63c3afabcaf7 - https://git.kernel.org/stable/c/31
0a75f7f2 - https://git.kernel.org/stable/c/fd5d8fb298a2866c337da635c79d63c3afabcaf7 - https://git.kernel.org/stable/c/31ff3309b47d98313c61b8301bf595820cc3cc33 - https://git.kernel.org/stable/c/5e39397d60dacc7f5d81d442c1c958eaaaf31128 - https://git.kernel.org/stable/c/b07a30a774b3c3e584a68dc91779c68ea2da4813 - https://git.kernel.org/stable/c/4687c3f955240ca2a576bdc3f742d4d915b6272d - https://git.kernel.org/stable/c/4ef1e521be610b720daeb7cf899fedc7db0274c4 - https://git.kernel.org/stable/c/78601726d4a59a291acc5a52da1d3a0a6831e4e8
CVE ID: CVE-2022-49686 State: PUBLISHED Published: 2025-02-26T02:24:12.624Z Last Updated: 2025-05-04T08:43:18.743Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: usb: gadget: uvc: fix list double add in uvcg_video_pump A panic can occur if the endpoint becomes disabled and the uvcg_video_pump adds the request back to the req_free list after it has already been queued to the endpoint. The endpoint complete will add the request back to the req_free list. Invalidate the local request handle once it's been queued. <6>[ 246.796704][T13726] configfs-gadget gadget: uvc: uvc_function_set_alt(1, 0) <3>[ 246.797078][ T26] list_add double
<6>[ 246.796704][T13726] configfs-gadget gadget: uvc: uvc_function_set_alt(1, 0) <3>[ 246.797078][ T26] list_add double add: new=ffffff878bee5c40, prev=ffffff878bee5c40, next=ffffff878b0f0a90. <6>[ 246.797213][ T26] ------------[ cut here ]------------ <2>[ 246.797224][ T26] kernel BUG at lib/list_debug.c:31! <6>[ 246.807073][ T26] Call trace: <6>[ 246.807180][ T26] uvcg_video_pump+0x364/0x38c <6>[ 246.807366][ T26] process_one_work+0x2a4/0x544 <6>[ 246.807394][ T26] worker_thread+0x350/0x784 <6>[ 246.807442][ T26] kthread+0x2ac/0x320 References: - https://git.kernel.org/stable/c/d95ac8b920de1d39525fadc408ce675697626ca6 - https://git.kernel.org/stable/c/96163f835e65f8c9897487fac965819f0651d
table/c/d95ac8b920de1d39525fadc408ce675697626ca6 - https://git.kernel.org/stable/c/96163f835e65f8c9897487fac965819f0651d671
CVE ID: CVE-2022-49687 State: PUBLISHED Published: 2025-02-26T02:24:13.187Z Last Updated: 2025-05-04T08:43:19.791Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: virtio_net: fix xdp_rxq_info bug after suspend/resume The following sequence currently causes a driver bug warning when using virtio_net: # ip link set eth0 up # echo mem > /sys/power/state (or e.g. # rtcwake -s 10 -m mem) <resume> # ip link set eth0 down Missing register, driver bug WARNING: CPU: 0 PID: 375 at net/core/xdp.c:138 xdp_rxq_info_unreg+0x58/0x60 Call trace: xdp_rxq_info_unreg+0x58/0x60 virtnet_close+0x58/0xac __dev_close_many+0xac/0x140 __dev_change_flags+
58/0x60 Call trace: xdp_rxq_info_unreg+0x58/0x60 virtnet_close+0x58/0xac __dev_close_many+0xac/0x140 __dev_change_flags+0xd8/0x210 dev_change_flags+0x24/0x64 do_setlink+0x230/0xdd0 ... This happens because virtnet_freeze() frees the receive_queue completely (including struct xdp_rxq_info) but does not call xdp_rxq_info_unreg(). Similarly, virtnet_restore() sets up the receive_queue again but does not call xdp_rxq_info_reg(). Actually, parts of virtnet_freeze_down() and virtnet_restore_up() are almost identical to virtnet_close() and virtnet_open(): only the calls to xdp_rxq_info_(un)reg() are missing. This means that we can fix this easily and avoid such problems in the future by just callin
_info_(un)reg() are missing. This means that we can fix this easily and avoid such problems in the future by just calling virtnet_close()/open() from the freeze/restore handlers. Aside from adding the missing xdp_rxq_info calls the only difference is that the refill work is only cancelled if netif_running(). However, this should not make any functional difference since the refill work should only be active if the network interface is actually up. References: - https://git.kernel.org/stable/c/9222672fa6370f0ec3d899662cb8680e9282fc4c - https://git.kernel.org/stable/c/8c7a32b7c15555beddc5810c3334d9cefff061bf - https://git.kernel.org/stable/c/340fbdc8011f2dc678f622c5ce1cbb5ab8305de7 - https://gi
c15555beddc5810c3334d9cefff061bf - https://git.kernel.org/stable/c/340fbdc8011f2dc678f622c5ce1cbb5ab8305de7 - https://git.kernel.org/stable/c/8d7fe9ad6fddc2af8bde4b921b4f8fab231ed38c - https://git.kernel.org/stable/c/57ee40f1b198b59d43c216fbc4672f9300d3c8b0 - https://git.kernel.org/stable/c/8af52fe9fd3bf5e7478da99193c0632276e1dfce