Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
CVE ID: CVE-2022-49297 State: PUBLISHED Published: 2025-02-26T02:01:26.628Z Last Updated: 2025-10-29T10:50:00.620Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nbd: fix io hung while disconnecting device In our tests, "qemu-nbd" triggers a io hung: INFO: task qemu-nbd:11445 blocked for more than 368 seconds. Not tainted 5.18.0-rc3-next-20220422-00003-g2176915513ca #884 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:qemu-nbd state:D stack: 0 pid:11445 ppid: 1 flags:0x00000000 Call Trace: <TASK> __schedule+0x480/0x1050 ? _raw_spin_lock_irqsave+0x3e/0xb0 schedule+0x9c/0x1b0 blk_mq_freeze_queue_wai
all Trace: <TASK> __schedule+0x480/0x1050 ? _raw_spin_lock_irqsave+0x3e/0xb0 schedule+0x9c/0x1b0 blk_mq_freeze_queue_wait+0x9d/0xf0 ? ipi_rseq+0x70/0x70 blk_mq_freeze_queue+0x2b/0x40 nbd_add_socket+0x6b/0x270 [nbd] nbd_ioctl+0x383/0x510 [nbd] blkdev_ioctl+0x18e/0x3e0 __x64_sys_ioctl+0xac/0x120 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7fd8ff706577 RSP: 002b:00007fd8fcdfebf8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000040000000 RCX: 00007fd8ff706577 RDX: 000000000000000d RSI: 000000000000ab00 RDI: 000000000000000f RBP: 000000000000000f R08: 000000000000fbe8 R09: 000055fe497c62b0 R10: 00000002aff20000 R11: 0000000000000246 R1
000000f RBP: 000000000000000f R08: 000000000000fbe8 R09: 000055fe497c62b0 R10: 00000002aff20000 R11: 0000000000000246 R12: 000000000000006d R13: 0000000000000000 R14: 00007ffe82dc5e70 R15: 00007fd8fcdff9c0 "qemu-ndb -d" will call ioctl 'NBD_DISCONNECT' first, however, following message was found: block nbd0: Send disconnect failed -32 Which indicate that something is wrong with the server. Then, "qemu-nbd -d" will call ioctl 'NBD_CLEAR_SOCK', however ioctl can't clear requests after commit 2516ab1543fd("nbd: only clear the queue on device teardown"). And in the meantime, request can't complete through timeout because nbd_xmit_timeout() will always return 'BLK_EH_RESET_TIMER', which means suc
quest can't complete through timeout because nbd_xmit_timeout() will always return 'BLK_EH_RESET_TIMER', which means such request will never be completed in this situation. Now that the flag 'NBD_CMD_INFLIGHT' can make sure requests won't complete multiple times, switch back to call nbd_clear_sock() in nbd_clear_sock_ioctl(), so that inflight requests can be cleared. References: - https://git.kernel.org/stable/c/67e403136a0e1a55fef6a05f103a3979a39ad3fd - https://git.kernel.org/stable/c/62d227f67a8c25d5e16f40e5290607f9306d2188 - https://git.kernel.org/stable/c/69893d6d7f5c10d8306c1b5fc64b71efc91aa6cd - https://git.kernel.org/stable/c/f72df77600a43e59b3189e53b47f8685739867d3 - https://git.kern
d8306c1b5fc64b71efc91aa6cd - https://git.kernel.org/stable/c/f72df77600a43e59b3189e53b47f8685739867d3 - https://git.kernel.org/stable/c/c4ba982bd5084fa659ef518aaf159e4dab02ecda - https://git.kernel.org/stable/c/54b06dc2a206b4d67349bb56b92d4bd32700b7b1 - https://git.kernel.org/stable/c/141318e62db87105b0103fccc59c9c5940da248d - https://git.kernel.org/stable/c/09dadb5985023e27d4740ebd17e6fea4640110e5
CVE ID: CVE-2022-49298 State: PUBLISHED Published: 2025-02-26T02:01:27.111Z Last Updated: 2025-10-01T19:46:59.578Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: staging: rtl8712: fix uninit-value in r871xu_drv_init() When 'tmpU1b' returns from r8712_read8(padapter, EE_9346CR) is 0, 'mac[6]' will not be initialized. BUG: KMSAN: uninit-value in r871xu_drv_init+0x2d54/0x3070 drivers/staging/rtl8712/usb_intf.c:541 r871xu_drv_init+0x2d54/0x3070 drivers/staging/rtl8712/usb_intf.c:541 usb_probe_interface+0xf19/0x1600 drivers/usb/core/driver.c:396 really_probe+0x653/0x14b0 drivers/base/dd.c:596 __driver_probe_device+0x3e9/0x530 driver
0 drivers/usb/core/driver.c:396 really_probe+0x653/0x14b0 drivers/base/dd.c:596 __driver_probe_device+0x3e9/0x530 drivers/base/dd.c:752 driver_probe_device drivers/base/dd.c:782 [inline] __device_attach_driver+0x79f/0x1120 drivers/base/dd.c:899 bus_for_each_drv+0x2d6/0x3f0 drivers/base/bus.c:427 __device_attach+0x593/0x8e0 drivers/base/dd.c:970 device_initial_probe+0x4a/0x60 drivers/base/dd.c:1017 bus_probe_device+0x17b/0x3e0 drivers/base/bus.c:487 device_add+0x1fff/0x26e0 drivers/base/core.c:3405 usb_set_configuration+0x37e9/0x3ed0 drivers/usb/core/message.c:2170 usb_generic_driver_probe+0x13c/0x300 drivers/usb/core/generic.c:238 usb_probe_device+0x309/0x570 drivers/usb/core/driver.c:293 re
ic_driver_probe+0x13c/0x300 drivers/usb/core/generic.c:238 usb_probe_device+0x309/0x570 drivers/usb/core/driver.c:293 really_probe+0x653/0x14b0 drivers/base/dd.c:596 __driver_probe_device+0x3e9/0x530 drivers/base/dd.c:752 driver_probe_device drivers/base/dd.c:782 [inline] __device_attach_driver+0x79f/0x1120 drivers/base/dd.c:899 bus_for_each_drv+0x2d6/0x3f0 drivers/base/bus.c:427 __device_attach+0x593/0x8e0 drivers/base/dd.c:970 device_initial_probe+0x4a/0x60 drivers/base/dd.c:1017 bus_probe_device+0x17b/0x3e0 drivers/base/bus.c:487 device_add+0x1fff/0x26e0 drivers/base/core.c:3405 usb_new_device+0x1b8e/0x2950 drivers/usb/core/hub.c:2566 hub_port_connect drivers/usb/core/hub.c:5358 [inline]
e.c:3405 usb_new_device+0x1b8e/0x2950 drivers/usb/core/hub.c:2566 hub_port_connect drivers/usb/core/hub.c:5358 [inline] hub_port_connect_change drivers/usb/core/hub.c:5502 [inline] port_event drivers/usb/core/hub.c:5660 [inline] hub_event+0x58e3/0x89e0 drivers/usb/core/hub.c:5742 process_one_work+0xdb6/0x1820 kernel/workqueue.c:2307 worker_thread+0x10b3/0x21e0 kernel/workqueue.c:2454 kthread+0x3c7/0x500 kernel/kthread.c:377 ret_from_fork+0x1f/0x30 Local variable mac created at: r871xu_drv_init+0x1771/0x3070 drivers/staging/rtl8712/usb_intf.c:394 usb_probe_interface+0xf19/0x1600 drivers/usb/core/driver.c:396 KMSAN: uninit-value in r871xu_drv_init https://syzkaller.appspot.com/bug?id=3cd92b1d8
1600 drivers/usb/core/driver.c:396 KMSAN: uninit-value in r871xu_drv_init https://syzkaller.appspot.com/bug?id=3cd92b1d85428b128503bfa7a250294c9ae00bd8 Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/0b7371a22489cbb2e8e826ca03fb5ce92afb04fe - https://git.kernel.org/stable/c/277faa442fe0c59f418ac53f47a78e1266addd65 - https://git.kernel.org/stable/c/a6535d00a9d54ce1c2a8d86a85001ffb6844f9b2 - https://git.kernel.org/stable/c/52a0d88c328098b4e9fb8f2f3877fec0eff4104b - https://git.kernel.org/stable/c/ff727ab0b7d7a56b5ef281f12abd00c4b85894e9 - https://git.kernel.org/stable/c/f36e754a1f0bafb9feeea63463de78080acb6de0 - https://git.kernel.org/stable/c/7
4b85894e9 - https://git.kernel.org/stable/c/f36e754a1f0bafb9feeea63463de78080acb6de0 - https://git.kernel.org/stable/c/76a964ad0ea8f2b10abd69a7532e174a28258283 - https://git.kernel.org/stable/c/70df04433fd351ba72bc635bd0b5fe443d9ac964 - https://git.kernel.org/stable/c/0458e5428e5e959d201a40ffe71d762a79ecedc4
CVE ID: CVE-2022-49299 State: REJECTED Published: 2025-02-26T02:10:34.977Z Last Updated: 2025-06-19T13:03:26.154Z Description: No description available.
CVE ID: CVE-2022-49300 State: PUBLISHED Published: 2025-02-26T02:10:35.594Z Last Updated: 2025-10-01T19:46:59.286Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nbd: fix race between nbd_alloc_config() and module removal When nbd module is being removing, nbd_alloc_config() may be called concurrently by nbd_genl_connect(), although try_module_get() will return false, but nbd_alloc_config() doesn't handle it. The race may lead to the leak of nbd_config and its related resources (e.g, recv_workq) and oops in nbd_read_stat() due to the unload of nbd module as shown below: BUG: kernel NULL pointer dereference, address: 00000000000
d_read_stat() due to the unload of nbd module as shown below: BUG: kernel NULL pointer dereference, address: 0000000000000040 Oops: 0000 [#1] SMP PTI CPU: 5 PID: 13840 Comm: kworker/u17:33 Not tainted 5.14.0+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Workqueue: knbd16-recv recv_work [nbd] RIP: 0010:nbd_read_stat.cold+0x130/0x1a4 [nbd] Call Trace: recv_work+0x3b/0xb0 [nbd] process_one_work+0x1ed/0x390 worker_thread+0x4a/0x3d0 kthread+0x12a/0x150 ret_from_fork+0x22/0x30 Fixing it by checking the return value of try_module_get() in nbd_alloc_config(). As nbd_alloc_config() may return ERR_PTR(-ENODEV), assign nbd->config only when nbd_alloc_config() succeeds to ensure the value of
oc_config() may return ERR_PTR(-ENODEV), assign nbd->config only when nbd_alloc_config() succeeds to ensure the value of nbd->config is binary (valid or NULL). Also adding a debug message to check the reference counter of nbd_config during module removal. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/165cf2e0019fa6cedc75b456490c41494c34abb4 - https://git.kernel.org/stable/c/2573f2375b64280be977431701ed5d33b75b9ad0 - https://git.kernel.org/stable/c/8a7da4ced236ce6637fe70f14ca18e718d4bf9e9 - https://git.kernel.org/stable/c/122e4adaff2439f1cc18cc7e931980fa7560df5c - https://git.kernel.org/stable/c/71c142f910da44421213ade601bcbd23ceae19fa - http
2e4adaff2439f1cc18cc7e931980fa7560df5c - https://git.kernel.org/stable/c/71c142f910da44421213ade601bcbd23ceae19fa - https://git.kernel.org/stable/c/2888fa41985f93ed0a6837cfbb06bcbfd7fa2314 - https://git.kernel.org/stable/c/d09525720dd5201756f698bee1076de9aefd4602 - https://git.kernel.org/stable/c/c55b2b983b0fa012942c3eb16384b2b722caa810
CVE ID: CVE-2022-49301 State: PUBLISHED Published: 2025-02-26T02:10:36.072Z Last Updated: 2025-10-01T19:46:59.120Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: staging: rtl8712: fix uninit-value in usb_read8() and friends When r8712_usbctrl_vendorreq() returns negative, 'data' in usb_read{8,16,32} will not be initialized. BUG: KMSAN: uninit-value in string_nocheck lib/vsprintf.c:643 [inline] BUG: KMSAN: uninit-value in string+0x4ec/0x6f0 lib/vsprintf.c:725 string_nocheck lib/vsprintf.c:643 [inline] string+0x4ec/0x6f0 lib/vsprintf.c:725 vsnprintf+0x2222/0x3650 lib/vsprintf.c:2806 va_format lib/vsprintf.c:1704 [inline] pointer+
4ec/0x6f0 lib/vsprintf.c:725 vsnprintf+0x2222/0x3650 lib/vsprintf.c:2806 va_format lib/vsprintf.c:1704 [inline] pointer+0x18e6/0x1f70 lib/vsprintf.c:2443 vsnprintf+0x1a9b/0x3650 lib/vsprintf.c:2810 vprintk_store+0x537/0x2150 kernel/printk/printk.c:2158 vprintk_emit+0x28b/0xab0 kernel/printk/printk.c:2256 dev_vprintk_emit+0x5ef/0x6d0 drivers/base/core.c:4604 dev_printk_emit+0x1dd/0x21f drivers/base/core.c:4615 __dev_printk+0x3be/0x440 drivers/base/core.c:4627 _dev_info+0x1ea/0x22f drivers/base/core.c:4673 r871xu_drv_init+0x1929/0x3070 drivers/staging/rtl8712/usb_intf.c:401 usb_probe_interface+0xf19/0x1600 drivers/usb/core/driver.c:396 really_probe+0x6c7/0x1350 drivers/base/dd.c:621 __driver_p
sb_probe_interface+0xf19/0x1600 drivers/usb/core/driver.c:396 really_probe+0x6c7/0x1350 drivers/base/dd.c:621 __driver_probe_device+0x3e9/0x530 drivers/base/dd.c:752 driver_probe_device drivers/base/dd.c:782 [inline] __device_attach_driver+0x79f/0x1120 drivers/base/dd.c:899 bus_for_each_drv+0x2d6/0x3f0 drivers/base/bus.c:427 __device_attach+0x593/0x8e0 drivers/base/dd.c:970 device_initial_probe+0x4a/0x60 drivers/base/dd.c:1017 bus_probe_device+0x17b/0x3e0 drivers/base/bus.c:487 device_add+0x1fff/0x26e0 drivers/base/core.c:3405 usb_set_configuration+0x37e9/0x3ed0 drivers/usb/core/message.c:2170 usb_generic_driver_probe+0x13c/0x300 drivers/usb/core/generic.c:238 usb_probe_device+0x309/0x570 dr
/core/message.c:2170 usb_generic_driver_probe+0x13c/0x300 drivers/usb/core/generic.c:238 usb_probe_device+0x309/0x570 drivers/usb/core/driver.c:293 really_probe+0x6c7/0x1350 drivers/base/dd.c:621 __driver_probe_device+0x3e9/0x530 drivers/base/dd.c:752 driver_probe_device drivers/base/dd.c:782 [inline] __device_attach_driver+0x79f/0x1120 drivers/base/dd.c:899 bus_for_each_drv+0x2d6/0x3f0 drivers/base/bus.c:427 __device_attach+0x593/0x8e0 drivers/base/dd.c:970 device_initial_probe+0x4a/0x60 drivers/base/dd.c:1017 bus_probe_device+0x17b/0x3e0 drivers/base/bus.c:487 device_add+0x1fff/0x26e0 drivers/base/core.c:3405 usb_new_device+0x1b91/0x2950 drivers/usb/core/hub.c:2566 hub_port_connect drivers
0x1fff/0x26e0 drivers/base/core.c:3405 usb_new_device+0x1b91/0x2950 drivers/usb/core/hub.c:2566 hub_port_connect drivers/usb/core/hub.c:5363 [inline] hub_port_connect_change drivers/usb/core/hub.c:5507 [inline] port_event drivers/usb/core/hub.c:5665 [inline] hub_event+0x58e3/0x89e0 drivers/usb/core/hub.c:5747 process_one_work+0xdb6/0x1820 kernel/workqueue.c:2289 worker_thread+0x10d0/0x2240 kernel/workqueue.c:2436 kthread+0x3c7/0x500 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 Local variable data created at: usb_read8+0x5d/0x130 drivers/staging/rtl8712/usb_ops.c:33 r8712_read8+0xa5/0xd0 drivers/staging/rtl8712/rtl8712_io.c:29 KMSAN: uninit-value in r871xu_drv_init https://syzkaller.appspot.c
ad8+0xa5/0xd0 drivers/staging/rtl8712/rtl8712_io.c:29 KMSAN: uninit-value in r871xu_drv_init https://syzkaller.appspot.com/bug?id=3cd92b1d85428b128503bfa7a250294c9ae00bd8 Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/58762f1c63c75cbe1dc393eed3c9cf8e38310ca1 - https://git.kernel.org/stable/c/33ef21d55418ab6a62a63fd550b2dbe297433372 - https://git.kernel.org/stable/c/95b0f54f8a898072a2810c05fab34d971f23a612 - https://git.kernel.org/stable/c/d7ed3c85da0b230bcdf5329acfe012ed093f3daa - https://git.kernel.org/stable/c/de075af8c404f7d59ed34df230aedd9f645fb846 - https://git.kernel.org/stable/c/d1b57669732d09da7e13ef86d058dab0cd57f6e0
CVE ID: CVE-2022-49302 State: PUBLISHED Published: 2025-02-26T02:10:36.556Z Last Updated: 2025-10-01T19:46:58.970Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: USB: host: isp116x: check return value after calling platform_get_resource() It will cause null-ptr-deref if platform_get_resource() returns NULL, we need check the return value. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/804de302ada3544699c5f48c5314b249af76faa3 - https://git.kernel.org/stable/c/7bffda1560a6f255fdf504e059fbbdb5d46b9e44 - https://git.kernel.org/stable/c/3825db88d8c704e7992b685618a03f82bffcf2ef - http
ffda1560a6f255fdf504e059fbbdb5d46b9e44 - https://git.kernel.org/stable/c/3825db88d8c704e7992b685618a03f82bffcf2ef - https://git.kernel.org/stable/c/c91a74b1f0f2d2d7e728742ae55e3ffe9ba7853d - https://git.kernel.org/stable/c/ee105039d3653444de4d3ede642383c92855dc1e - https://git.kernel.org/stable/c/3592cfd8b848bf0c4d7740d78a87a7b8f6e1fa9a - https://git.kernel.org/stable/c/aca0cab0e9ed33b6371aafb519a6c38f2850ffc3 - https://git.kernel.org/stable/c/82a101f14943f479fd190b1e5b40d91c77e2ac1b - https://git.kernel.org/stable/c/134a3408c2d3f7e23eb0e4556e0a2d9f36c2614e
CVE ID: CVE-2022-49303 State: PUBLISHED Published: 2025-02-26T02:10:37.056Z Last Updated: 2025-10-01T19:46:58.829Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drivers: staging: rtl8192eu: Fix deadlock in rtw_joinbss_event_prehandle There is a deadlock in rtw_joinbss_event_prehandle(), which is shown below: (Thread 1) | (Thread 2) | _set_timer() rtw_joinbss_event_prehandle()| mod_timer() spin_lock_bh() //(1) | (wait a time) ... | rtw_join_timeout_handler() | _rtw_join_timeout_handler() del_timer_sync() | spin_lock_bh() //(2) (wait timer to stop) | ... We hold pmlmepriv->lock in position (1) of thread 1 and use del_timer_sync(
n_lock_bh() //(2) (wait timer to stop) | ... We hold pmlmepriv->lock in position (1) of thread 1 and use del_timer_sync() to wait timer to stop, but timer handler also need pmlmepriv->lock in position (2) of thread 2. As a result, rtw_joinbss_event_prehandle() will block forever. This patch extracts del_timer_sync() from the protection of spin_lock_bh(), which could let timer handler to obtain the needed lock. What`s more, we change spin_lock_bh() to spin_lock_irq() in _rtw_join_timeout_handler() in order to prevent deadlock. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/25cf414b0610fea29d8e045f315648d9007c9a46 - https://git.kernel.org/stabl
t: References: - https://git.kernel.org/stable/c/25cf414b0610fea29d8e045f315648d9007c9a46 - https://git.kernel.org/stable/c/0fcddf9c7c10202946d5b19409efbdff744fba88
CVE ID: CVE-2022-49304 State: PUBLISHED Published: 2025-02-26T02:10:37.726Z Last Updated: 2025-10-01T19:46:58.692Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drivers: tty: serial: Fix deadlock in sa1100_set_termios() There is a deadlock in sa1100_set_termios(), which is shown below: (Thread 1) | (Thread 2) | sa1100_enable_ms() sa1100_set_termios() | mod_timer() spin_lock_irqsave() //(1) | (wait a time) ... | sa1100_timeout() del_timer_sync() | spin_lock_irqsave() //(2) (wait timer to stop) | ... We hold sport->port.lock in position (1) of thread 1 and use del_timer_sync() to wait timer to stop, but timer handler also need s
ort->port.lock in position (1) of thread 1 and use del_timer_sync() to wait timer to stop, but timer handler also need sport->port.lock in position (2) of thread 2. As a result, sa1100_set_termios() will block forever. This patch moves del_timer_sync() before spin_lock_irqsave() in order to prevent the deadlock. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/0976808d0d171ec837d4bd3e9f4ad4a00ab703b8 - https://git.kernel.org/stable/c/85e20f8bd31a46d8c60103d0274a8ebe8f47f2b2 - https://git.kernel.org/stable/c/920f0ae7a129ffee98a106e3bbdfd61a2a59e939 - https://git.kernel.org/stable/c/09a5958a2452ad22d0cb638711ef34ea1863a829 - https://git.kernel.or
106e3bbdfd61a2a59e939 - https://git.kernel.org/stable/c/09a5958a2452ad22d0cb638711ef34ea1863a829 - https://git.kernel.org/stable/c/6e2273eefab54a521d9c59efb6e1114e742bdf41 - https://git.kernel.org/stable/c/2cbfc38df580bff5b2fe19f21c1a7520efcc4b3b - https://git.kernel.org/stable/c/553213432ef0c295becdc08c0207d2094468f673 - https://git.kernel.org/stable/c/34d91e555e5582cffdbcbb75517bc9217866823e - https://git.kernel.org/stable/c/62b2caef400c1738b6d22f636c628d9f85cd4c4c
CVE ID: CVE-2022-49305 State: PUBLISHED Published: 2025-02-26T02:10:38.212Z Last Updated: 2025-10-01T19:46:58.552Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drivers: staging: rtl8192u: Fix deadlock in ieee80211_beacons_stop() There is a deadlock in ieee80211_beacons_stop(), which is shown below: (Thread 1) | (Thread 2) | ieee80211_send_beacon() ieee80211_beacons_stop() | mod_timer() spin_lock_irqsave() //(1) | (wait a time) ... | ieee80211_send_beacon_cb() del_timer_sync() | spin_lock_irqsave() //(2) (wait timer to stop) | ... We hold ieee->beacon_lock in position (1) of thread 1 and use del_timer_sync() to wait timer to s
t timer to stop) | ... We hold ieee->beacon_lock in position (1) of thread 1 and use del_timer_sync() to wait timer to stop, but timer handler also need ieee->beacon_lock in position (2) of thread 2. As a result, ieee80211_beacons_stop() will block forever. This patch extracts del_timer_sync() from the protection of spin_lock_irqsave(), which could let timer handler to obtain the needed lock. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/b465bb2ebf666116c1ac745cb80c65154dc0d27e - https://git.kernel.org/stable/c/1fbe033c52480f7954c057510040fa6286c4ea25 - https://git.kernel.org/stable/c/66f769762f65d957f688f3258755c6ec410bf710 - https://git.ke
0f7954c057510040fa6286c4ea25 - https://git.kernel.org/stable/c/66f769762f65d957f688f3258755c6ec410bf710 - https://git.kernel.org/stable/c/042915c1bfedd684c1d98a841794ee203200571a - https://git.kernel.org/stable/c/ffc9cab7243f8151be37966301307bfd3cda2db3 - https://git.kernel.org/stable/c/b34cb54923a6e5ddefbaf358c85c922c6ab456e2 - https://git.kernel.org/stable/c/806c7b53414934ba2a39449b31fd1a038e500273
CVE ID: CVE-2022-49306 State: PUBLISHED Published: 2025-02-26T02:10:38.680Z Last Updated: 2025-09-03T12:58:40.666Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: host: Stop setting the ACPI companion It is no longer needed. The sysdev pointer is now used when assigning the ACPI companions to the xHCI ports and USB devices. Assigning the ACPI companion here resulted in the fwnode->secondary pointer to be replaced also for the parent dwc3 device since the primary fwnode (the ACPI companion) was shared. That was unintentional and it created potential side effects like resource leaks. References: - https://git.kernel.org
. That was unintentional and it created potential side effects like resource leaks. References: - https://git.kernel.org/stable/c/d7f35934f7ab67bfd9adabc84207e59da9c19108 - https://git.kernel.org/stable/c/9c185fde906a48368bd2d2a8c17d4b6fb3d670af - https://git.kernel.org/stable/c/7fd069d65da2e20b1caec3b7bcf9dfbe28c04bb2
CVE ID: CVE-2022-49307 State: PUBLISHED Published: 2025-02-26T02:10:39.151Z Last Updated: 2025-10-01T19:46:58.412Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: tty: synclink_gt: Fix null-pointer-dereference in slgt_clean() When the driver fails at alloc_hdlcdev(), and then we remove the driver module, we will get the following splat: [ 25.065966] general protection fault, probably for non-canonical address 0xdffffc0000000182: 0000 [#1] PREEMPT SMP KASAN PTI [ 25.066914] KASAN: null-ptr-deref in range [0x0000000000000c10-0x0000000000000c17] [ 25.069262] RIP: 0010:detach_hdlc_protocol+0x2a/0x3e0 [ 25.077709] Call Trace: [ 25.07
000000000c10-0x0000000000000c17] [ 25.069262] RIP: 0010:detach_hdlc_protocol+0x2a/0x3e0 [ 25.077709] Call Trace: [ 25.077924] <TASK> [ 25.078108] unregister_hdlc_device+0x16/0x30 [ 25.078481] slgt_cleanup+0x157/0x9f0 [synclink_gt] Fix this by checking whether the 'info->netdev' is a null pointer first. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/50c341f9a2adc4c32a8ad5a39eb99d9c4a419e0d - https://git.kernel.org/stable/c/078212ad15dbd88840c82c97f12c93d83703c8fd - https://git.kernel.org/stable/c/ba08cbc5b53e151d0acf1930fb526fc65b7f3e65 - https://git.kernel.org/stable/c/f6e07eb7ebec53ffe81fc2489589320fbe4a6b75 - https://git.kernel.org/stable/c
fc65b7f3e65 - https://git.kernel.org/stable/c/f6e07eb7ebec53ffe81fc2489589320fbe4a6b75 - https://git.kernel.org/stable/c/d68d5e68b7f64de7170f8e04dd9b995c36b2c71c - https://git.kernel.org/stable/c/8a95696bdc0e13f8980f05b54a3b9081963d1256 - https://git.kernel.org/stable/c/ddd67751ab86c6a65f95c35293c42f85a42ac05d - https://git.kernel.org/stable/c/1ceb4ca9543a8a788febf6bc8dad2e605e172d5e - https://git.kernel.org/stable/c/689ca31c542687709ba21ec2195c1fbce34fd029
CVE ID: CVE-2022-49308 State: PUBLISHED Published: 2025-02-26T02:10:39.648Z Last Updated: 2025-05-04T08:34:53.112Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: extcon: Modify extcon device to be created after driver data is set Currently, someone can invoke the sysfs such as state_show() intermittently before dev_set_drvdata() is done. And it can be a cause of kernel Oops because of edev is Null at that time. So modified the driver registration to after setting drviver data. - Oops's backtrace. Backtrace: [<c067865c>] (state_show) from [<c05222e8>] (dev_attr_show) [<c05222c0>] (dev_attr_show) from [<c02c66e0>] (sysfs_kf_seq_s