https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Mon, 29 Jun 2026 07:34:55 +0000 https://vulnerability.circl.lu/sighting/e9c6c3ef-e5d1-41b8-9a62-9c84bf88fbab/export {"uuid": "e9c6c3ef-e5d1-41b8-9a62-9c84bf88fbab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-4894", "type": "seen", "source": "https://t.me/cibsecurity/68693", "content": "\u203c CVE-2022-4894 \u203c\n\nCertain HP and Samsung Printer software packages may potentially be vulnerable to elevation of privilege due to Uncontrolled Search Path Element.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-08-17T00:36:46.000000Z"} {"uuid": "e9c6c3ef-e5d1-41b8-9a62-9c84bf88fbab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-4894", "type": "seen", "source": "https://t.me/cibsecurity/68693", "content": "\u203c CVE-2022-4894 \u203c\n\nCertain HP and Samsung Printer software packages may potentially be vulnerable to elevation of privilege due to Uncontrolled Search Path Element.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-08-17T00:36:46.000000Z"} https://vulnerability.circl.lu/sighting/e9c6c3ef-e5d1-41b8-9a62-9c84bf88fbab/export Thu, 17 Aug 2023 00:36:46 +0000 https://vulnerability.circl.lu/sighting/ca0af634-72ca-4c45-ab14-0bac1cd53b8e/export {"uuid": "ca0af634-72ca-4c45-ab14-0bac1cd53b8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48943", "type": "seen", "source": "https://t.me/cvedetector/3883", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48943 - KVM Linux Kernel Guest Ready Event Token Zeroing Vulnerability\", \n \"Content\": \"CVE ID : CVE-2022-48943 \nPublished : Aug. 22, 2024, 4:15 a.m. | 31\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nKVM: x86/mmu: make apf token non-zero to fix bug \n \nIn current async pagefault logic, when a page is ready, KVM relies on \nkvm_arch_can_dequeue_async_page_present() to determine whether to deliver \na READY event to the Guest. This function test token value of struct \nkvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a \nREADY event is finished by Guest. If value is zero meaning that a READY \nevent is done, so the KVM can deliver another. \nBut the kvm_arch_setup_async_pf() may produce a valid token with zero \nvalue, which is confused with previous mention and may lead the loss of \nthis READY event. \n \nThis bug may cause task blocked forever in Guest: \n INFO: task stress:7532 blocked for more than 1254 seconds. \n Not tainted 5.10.0 #16 \n \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message. \n task:stress state:D stack: 0 pid: 7532 ppid: 1409 \n flags:0x00000080 \n Call Trace: \n __schedule+0x1e7/0x650 \n schedule+0x46/0xb0 \n kvm_async_pf_task_wait_schedule+0xad/0xe0 \n ? exit_to_user_mode_prepare+0x60/0x70 \n __kvm_handle_async_pf+0x4f/0xb0 \n ? asm_exc_page_fault+0x8/0x30 \n exc_page_fault+0x6f/0x110 \n ? asm_exc_page_fault+0x8/0x30 \n asm_exc_page_fault+0x1e/0x30 \n RIP: 0033:0x402d00 \n RSP: 002b:00007ffd31912500 EFLAGS: 00010206 \n RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0 \n RDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0 \n RBP: 00000000021262b0 R08: 0000000000000003 R09: 0000000000000086 \n R10: 00000000000000eb R11: 00007fefbdf2baa0 R12: 0000000000000000 \n R13: 0000000000000002 R14: 000000000007d000 R15: 0000000000001000 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T06:49:17.000000Z"} {"uuid": "ca0af634-72ca-4c45-ab14-0bac1cd53b8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48943", "type": "seen", "source": "https://t.me/cvedetector/3883", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48943 - KVM Linux Kernel Guest Ready Event Token Zeroing Vulnerability\", \n \"Content\": \"CVE ID : CVE-2022-48943 \nPublished : Aug. 22, 2024, 4:15 a.m. | 31\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nKVM: x86/mmu: make apf token non-zero to fix bug \n \nIn current async pagefault logic, when a page is ready, KVM relies on \nkvm_arch_can_dequeue_async_page_present() to determine whether to deliver \na READY event to the Guest. This function test token value of struct \nkvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a \nREADY event is finished by Guest. If value is zero meaning that a READY \nevent is done, so the KVM can deliver another. \nBut the kvm_arch_setup_async_pf() may produce a valid token with zero \nvalue, which is confused with previous mention and may lead the loss of \nthis READY event. \n \nThis bug may cause task blocked forever in Guest: \n INFO: task stress:7532 blocked for more than 1254 seconds. \n Not tainted 5.10.0 #16 \n \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message. \n task:stress state:D stack: 0 pid: 7532 ppid: 1409 \n flags:0x00000080 \n Call Trace: \n __schedule+0x1e7/0x650 \n schedule+0x46/0xb0 \n kvm_async_pf_task_wait_schedule+0xad/0xe0 \n ? exit_to_user_mode_prepare+0x60/0x70 \n __kvm_handle_async_pf+0x4f/0xb0 \n ? asm_exc_page_fault+0x8/0x30 \n exc_page_fault+0x6f/0x110 \n ? asm_exc_page_fault+0x8/0x30 \n asm_exc_page_fault+0x1e/0x30 \n RIP: 0033:0x402d00 \n RSP: 002b:00007ffd31912500 EFLAGS: 00010206 \n RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0 \n RDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0 \n RBP: 00000000021262b0 R08: 0000000000000003 R09: 0000000000000086 \n R10: 00000000000000eb R11: 00007fefbdf2baa0 R12: 0000000000000000 \n R13: 0000000000000002 R14: 000000000007d000 R15: 0000000000001000 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T06:49:17.000000Z"} https://vulnerability.circl.lu/sighting/ca0af634-72ca-4c45-ab14-0bac1cd53b8e/export Thu, 22 Aug 2024 06:49:17 +0000 https://vulnerability.circl.lu/sighting/47193d72-8207-44bc-9120-c4e1801ca99e/export {"uuid": "47193d72-8207-44bc-9120-c4e1801ca99e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48942", "type": "seen", "source": "https://t.me/cvedetector/3884", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48942 - Linux Kernel Hardware Monitoring Thermal Zone Sensor Registration Null Pointer Dereference\", \n \"Content\": \"CVE ID : CVE-2022-48942 \nPublished : Aug. 22, 2024, 4:15 a.m. | 31\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nhwmon: Handle failure to register sensor with thermal zone correctly \n \nIf an attempt is made to a sensor with a thermal zone and it fails, \nthe call to devm_thermal_zone_of_sensor_register() may return -ENODEV. \nThis may result in crashes similar to the following. \n \nUnable to handle kernel NULL pointer dereference at virtual address 00000000000003cd \n... \nInternal error: Oops: 96000021 [#1] PREEMPT SMP \n... \npstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) \npc : mutex_lock+0x18/0x60 \nlr : thermal_zone_device_update+0x40/0x2e0 \nsp : ffff800014c4fc60 \nx29: ffff800014c4fc60 x28: ffff365ee3f6e000 x27: ffffdde218426790 \nx26: ffff365ee3f6e000 x25: 0000000000000000 x24: ffff365ee3f6e000 \nx23: ffffdde218426870 x22: ffff365ee3f6e000 x21: 00000000000003cd \nx20: ffff365ee8bf3308 x19: ffffffffffffffed x18: 0000000000000000 \nx17: ffffdde21842689c x16: ffffdde1cb7a0b7c x15: 0000000000000040 \nx14: ffffdde21a4889a0 x13: 0000000000000228 x12: 0000000000000000 \nx11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000 \nx8 : 0000000001120000 x7 : 0000000000000001 x6 : 0000000000000000 \nx5 : 0068000878e20f07 x4 : 0000000000000000 x3 : 00000000000003cd \nx2 : ffff365ee3f6e000 x1 : 0000000000000000 x0 : 00000000000003cd \nCall trace: \n mutex_lock+0x18/0x60 \n hwmon_notify_event+0xfc/0x110 \n 0xffffdde1cb7a0a90 \n 0xffffdde1cb7a0b7c \n irq_thread_fn+0x2c/0xa0 \n irq_thread+0x134/0x240 \n kthread+0x178/0x190 \n ret_from_fork+0x10/0x20 \nCode: d503201f d503201f d2800001 aa0103e4 (c8e47c02) \n \nJon Hunter reports that the exact call sequence is: \n \nhwmon_notify_event() \n --> hwmon_thermal_notify() \n --> thermal_zone_device_update() \n --> update_temperature() \n --> mutex_lock() \n \nThe hwmon core needs to handle all errors returned from calls \nto devm_thermal_zone_of_sensor_register(). If the call fails \nwith -ENODEV, report that the sensor was not attached to a \nthermal zone but continue to register the hwmon device. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T06:49:18.000000Z"} {"uuid": "47193d72-8207-44bc-9120-c4e1801ca99e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48942", "type": "seen", "source": "https://t.me/cvedetector/3884", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48942 - Linux Kernel Hardware Monitoring Thermal Zone Sensor Registration Null Pointer Dereference\", \n \"Content\": \"CVE ID : CVE-2022-48942 \nPublished : Aug. 22, 2024, 4:15 a.m. | 31\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nhwmon: Handle failure to register sensor with thermal zone correctly \n \nIf an attempt is made to a sensor with a thermal zone and it fails, \nthe call to devm_thermal_zone_of_sensor_register() may return -ENODEV. \nThis may result in crashes similar to the following. \n \nUnable to handle kernel NULL pointer dereference at virtual address 00000000000003cd \n... \nInternal error: Oops: 96000021 [#1] PREEMPT SMP \n... \npstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) \npc : mutex_lock+0x18/0x60 \nlr : thermal_zone_device_update+0x40/0x2e0 \nsp : ffff800014c4fc60 \nx29: ffff800014c4fc60 x28: ffff365ee3f6e000 x27: ffffdde218426790 \nx26: ffff365ee3f6e000 x25: 0000000000000000 x24: ffff365ee3f6e000 \nx23: ffffdde218426870 x22: ffff365ee3f6e000 x21: 00000000000003cd \nx20: ffff365ee8bf3308 x19: ffffffffffffffed x18: 0000000000000000 \nx17: ffffdde21842689c x16: ffffdde1cb7a0b7c x15: 0000000000000040 \nx14: ffffdde21a4889a0 x13: 0000000000000228 x12: 0000000000000000 \nx11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000 \nx8 : 0000000001120000 x7 : 0000000000000001 x6 : 0000000000000000 \nx5 : 0068000878e20f07 x4 : 0000000000000000 x3 : 00000000000003cd \nx2 : ffff365ee3f6e000 x1 : 0000000000000000 x0 : 00000000000003cd \nCall trace: \n mutex_lock+0x18/0x60 \n hwmon_notify_event+0xfc/0x110 \n 0xffffdde1cb7a0a90 \n 0xffffdde1cb7a0b7c \n irq_thread_fn+0x2c/0xa0 \n irq_thread+0x134/0x240 \n kthread+0x178/0x190 \n ret_from_fork+0x10/0x20 \nCode: d503201f d503201f d2800001 aa0103e4 (c8e47c02) \n \nJon Hunter reports that the exact call sequence is: \n \nhwmon_notify_event() \n --> hwmon_thermal_notify() \n --> thermal_zone_device_update() \n --> update_temperature() \n --> mutex_lock() \n \nThe hwmon core needs to handle all errors returned from calls \nto devm_thermal_zone_of_sensor_register(). If the call fails \nwith -ENODEV, report that the sensor was not attached to a \nthermal zone but continue to register the hwmon device. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T06:49:18.000000Z"} https://vulnerability.circl.lu/sighting/47193d72-8207-44bc-9120-c4e1801ca99e/export Thu, 22 Aug 2024 06:49:18 +0000 https://vulnerability.circl.lu/sighting/9a0795d8-e2f0-425d-b244-35902b227ee7/export {"uuid": "9a0795d8-e2f0-425d-b244-35902b227ee7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48940", "type": "seen", "source": "https://t.me/cvedetector/3886", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48940 - Linux kernel bpf: Incorrect copy_map_value leads to crash with bpf_spin_lock and bpf_timer\", \n \"Content\": \"CVE ID : CVE-2022-48940 \nPublished : Aug. 22, 2024, 4:15 a.m. | 31\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbpf: Fix crash due to incorrect copy_map_value \n \nWhen both bpf_spin_lock and bpf_timer are present in a BPF map value, \ncopy_map_value needs to skirt both objects when copying a value into and \nout of the map. However, the current code does not set both s_off and \nt_off in copy_map_value, which leads to a crash when e.g. bpf_spin_lock \nis placed in map value with bpf_timer, as bpf_map_update_elem call will \nbe able to overwrite the other timer object. \n \nWhen the issue is not fixed, an overwriting can produce the following \nsplat: \n \n[root@(none) bpf]# ./test_progs -t timer_crash \n[ 15.930339] bpf_testmod: loading out-of-tree module taints kernel. \n[ 16.037849] ================================================================== \n[ 16.038458] BUG: KASAN: user-memory-access in __pv_queued_spin_lock_slowpath+0x32b/0x520 \n[ 16.038944] Write of size 8 at addr 0000000000043ec0 by task test_progs/325 \n[ 16.039399] \n[ 16.039514] CPU: 0 PID: 325 Comm: test_progs Tainted: G OE 5.16.0+ #278 \n[ 16.039983] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ArchLinux 1.15.0-1 04/01/2014 \n[ 16.040485] Call Trace: \n[ 16.040645] \n[ 16.040805] dump_stack_lvl+0x59/0x73 \n[ 16.041069] ? __pv_queued_spin_lock_slowpath+0x32b/0x520 \n[ 16.041427] kasan_report.cold+0x116/0x11b \n[ 16.041673] ? __pv_queued_spin_lock_slowpath+0x32b/0x520 \n[ 16.042040] __pv_queued_spin_lock_slowpath+0x32b/0x520 \n[ 16.042328] ? memcpy+0x39/0x60 \n[ 16.042552] ? pv_hash+0xd0/0xd0 \n[ 16.042785] ? lockdep_hardirqs_off+0x95/0xd0 \n[ 16.043079] __bpf_spin_lock_irqsave+0xdf/0xf0 \n[ 16.043366] ? bpf_get_current_comm+0x50/0x50 \n[ 16.043608] ? jhash+0x11a/0x270 \n[ 16.043848] bpf_timer_cancel+0x34/0xe0 \n[ 16.044119] bpf_prog_c4ea1c0f7449940d_sys_enter+0x7c/0x81 \n[ 16.044500] bpf_trampoline_6442477838_0+0x36/0x1000 \n[ 16.044836] __x64_sys_nanosleep+0x5/0x140 \n[ 16.045119] do_syscall_64+0x59/0x80 \n[ 16.045377] ? lock_is_held_type+0xe4/0x140 \n[ 16.045670] ? irqentry_exit_to_user_mode+0xa/0x40 \n[ 16.046001] ? mark_held_locks+0x24/0x90 \n[ 16.046287] ? asm_exc_page_fault+0x1e/0x30 \n[ 16.046569] ? asm_exc_page_fault+0x8/0x30 \n[ 16.046851] ? lockdep_hardirqs_on+0x7e/0x100 \n[ 16.047137] entry_SYSCALL_64_after_hwframe+0x44/0xae \n[ 16.047405] RIP: 0033:0x7f9e4831718d \n[ 16.047602] Code: b4 0c 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 6c 0c 00 f7 d8 64 89 01 48 \n[ 16.048764] RSP: 002b:00007fff488086b8 EFLAGS: 00000206 ORIG_RAX: 0000000000000023 \n[ 16.049275] RAX: ffffffffffffffda RBX: 00007f9e48683740 RCX: 00007f9e4831718d \n[ 16.049747] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00007fff488086d0 \n[ 16.050225] RBP: 00007fff488086f0 R08: 00007fff488085d7 R09: 00007f9e4cb594a0 \n[ 16.050648] R10: 0000000000000000 R11: 0000000000000206 R12: 00007f9e484cde30 \n[ 16.051124] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 \n[ 16.051608] \n[ 16.051762] ================================================================== \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T06:49:19.000000Z"} {"uuid": "9a0795d8-e2f0-425d-b244-35902b227ee7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48940", "type": "seen", "source": "https://t.me/cvedetector/3886", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48940 - Linux kernel bpf: Incorrect copy_map_value leads to crash with bpf_spin_lock and bpf_timer\", \n \"Content\": \"CVE ID : CVE-2022-48940 \nPublished : Aug. 22, 2024, 4:15 a.m. | 31\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbpf: Fix crash due to incorrect copy_map_value \n \nWhen both bpf_spin_lock and bpf_timer are present in a BPF map value, \ncopy_map_value needs to skirt both objects when copying a value into and \nout of the map. However, the current code does not set both s_off and \nt_off in copy_map_value, which leads to a crash when e.g. bpf_spin_lock \nis placed in map value with bpf_timer, as bpf_map_update_elem call will \nbe able to overwrite the other timer object. \n \nWhen the issue is not fixed, an overwriting can produce the following \nsplat: \n \n[root@(none) bpf]# ./test_progs -t timer_crash \n[ 15.930339] bpf_testmod: loading out-of-tree module taints kernel. \n[ 16.037849] ================================================================== \n[ 16.038458] BUG: KASAN: user-memory-access in __pv_queued_spin_lock_slowpath+0x32b/0x520 \n[ 16.038944] Write of size 8 at addr 0000000000043ec0 by task test_progs/325 \n[ 16.039399] \n[ 16.039514] CPU: 0 PID: 325 Comm: test_progs Tainted: G OE 5.16.0+ #278 \n[ 16.039983] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ArchLinux 1.15.0-1 04/01/2014 \n[ 16.040485] Call Trace: \n[ 16.040645] \n[ 16.040805] dump_stack_lvl+0x59/0x73 \n[ 16.041069] ? __pv_queued_spin_lock_slowpath+0x32b/0x520 \n[ 16.041427] kasan_report.cold+0x116/0x11b \n[ 16.041673] ? __pv_queued_spin_lock_slowpath+0x32b/0x520 \n[ 16.042040] __pv_queued_spin_lock_slowpath+0x32b/0x520 \n[ 16.042328] ? memcpy+0x39/0x60 \n[ 16.042552] ? pv_hash+0xd0/0xd0 \n[ 16.042785] ? lockdep_hardirqs_off+0x95/0xd0 \n[ 16.043079] __bpf_spin_lock_irqsave+0xdf/0xf0 \n[ 16.043366] ? bpf_get_current_comm+0x50/0x50 \n[ 16.043608] ? jhash+0x11a/0x270 \n[ 16.043848] bpf_timer_cancel+0x34/0xe0 \n[ 16.044119] bpf_prog_c4ea1c0f7449940d_sys_enter+0x7c/0x81 \n[ 16.044500] bpf_trampoline_6442477838_0+0x36/0x1000 \n[ 16.044836] __x64_sys_nanosleep+0x5/0x140 \n[ 16.045119] do_syscall_64+0x59/0x80 \n[ 16.045377] ? lock_is_held_type+0xe4/0x140 \n[ 16.045670] ? irqentry_exit_to_user_mode+0xa/0x40 \n[ 16.046001] ? mark_held_locks+0x24/0x90 \n[ 16.046287] ? asm_exc_page_fault+0x1e/0x30 \n[ 16.046569] ? asm_exc_page_fault+0x8/0x30 \n[ 16.046851] ? lockdep_hardirqs_on+0x7e/0x100 \n[ 16.047137] entry_SYSCALL_64_after_hwframe+0x44/0xae \n[ 16.047405] RIP: 0033:0x7f9e4831718d \n[ 16.047602] Code: b4 0c 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 6c 0c 00 f7 d8 64 89 01 48 \n[ 16.048764] RSP: 002b:00007fff488086b8 EFLAGS: 00000206 ORIG_RAX: 0000000000000023 \n[ 16.049275] RAX: ffffffffffffffda RBX: 00007f9e48683740 RCX: 00007f9e4831718d \n[ 16.049747] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00007fff488086d0 \n[ 16.050225] RBP: 00007fff488086f0 R08: 00007fff488085d7 R09: 00007f9e4cb594a0 \n[ 16.050648] R10: 0000000000000000 R11: 0000000000000206 R12: 00007f9e484cde30 \n[ 16.051124] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 \n[ 16.051608] \n[ 16.051762] ================================================================== \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T06:49:19.000000Z"} https://vulnerability.circl.lu/sighting/9a0795d8-e2f0-425d-b244-35902b227ee7/export Thu, 22 Aug 2024 06:49:19 +0000 https://vulnerability.circl.lu/sighting/3da6a33f-0407-42bd-8631-09ba822aef47/export {"uuid": "3da6a33f-0407-42bd-8631-09ba822aef47", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48941", "type": "seen", "source": "https://t.me/cvedetector/3887", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48941 - Intel Ice Linux Kernel VF Reset and Removal Concurrency Vulnerability\", \n \"Content\": \"CVE ID : CVE-2022-48941 \nPublished : Aug. 22, 2024, 4:15 a.m. | 31\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nice: fix concurrent reset and removal of VFs \n \nCommit c503e63200c6 (\"ice: Stop processing VF messages during teardown\") \nintroduced a driver state flag, ICE_VF_DEINIT_IN_PROGRESS, which is \nintended to prevent some issues with concurrently handling messages from \nVFs while tearing down the VFs. \n \nThis change was motivated by crashes caused while tearing down and \nbringing up VFs in rapid succession. \n \nIt turns out that the fix actually introduces issues with the VF driver \ncaused because the PF no longer responds to any messages sent by the VF \nduring its .remove routine. This results in the VF potentially removing \nits DMA memory before the PF has shut down the device queues. \n \nAdditionally, the fix doesn't actually resolve concurrency issues within \nthe ice driver. It is possible for a VF to initiate a reset just prior \nto the ice driver removing VFs. This can result in the remove task \nconcurrently operating while the VF is being reset. This results in \nsimilar memory corruption and panics purportedly fixed by that commit. \n \nFix this concurrency at its root by protecting both the reset and \nremoval flows using the existing VF cfg_lock. This ensures that we \ncannot remove the VF while any outstanding critical tasks such as a \nvirtchnl message or a reset are occurring. \n \nThis locking change also fixes the root cause originally fixed by commit \nc503e63200c6 (\"ice: Stop processing VF messages during teardown\"), so we \ncan simply revert it. \n \nNote that I kept these two changes together because simply reverting the \noriginal commit alone would leave the driver vulnerable to worse race \nconditions. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T06:49:23.000000Z"} {"uuid": "3da6a33f-0407-42bd-8631-09ba822aef47", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48941", "type": "seen", "source": "https://t.me/cvedetector/3887", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48941 - Intel Ice Linux Kernel VF Reset and Removal Concurrency Vulnerability\", \n \"Content\": \"CVE ID : CVE-2022-48941 \nPublished : Aug. 22, 2024, 4:15 a.m. | 31\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nice: fix concurrent reset and removal of VFs \n \nCommit c503e63200c6 (\"ice: Stop processing VF messages during teardown\") \nintroduced a driver state flag, ICE_VF_DEINIT_IN_PROGRESS, which is \nintended to prevent some issues with concurrently handling messages from \nVFs while tearing down the VFs. \n \nThis change was motivated by crashes caused while tearing down and \nbringing up VFs in rapid succession. \n \nIt turns out that the fix actually introduces issues with the VF driver \ncaused because the PF no longer responds to any messages sent by the VF \nduring its .remove routine. This results in the VF potentially removing \nits DMA memory before the PF has shut down the device queues. \n \nAdditionally, the fix doesn't actually resolve concurrency issues within \nthe ice driver. It is possible for a VF to initiate a reset just prior \nto the ice driver removing VFs. This can result in the remove task \nconcurrently operating while the VF is being reset. This results in \nsimilar memory corruption and panics purportedly fixed by that commit. \n \nFix this concurrency at its root by protecting both the reset and \nremoval flows using the existing VF cfg_lock. This ensures that we \ncannot remove the VF while any outstanding critical tasks such as a \nvirtchnl message or a reset are occurring. \n \nThis locking change also fixes the root cause originally fixed by commit \nc503e63200c6 (\"ice: Stop processing VF messages during teardown\"), so we \ncan simply revert it. \n \nNote that I kept these two changes together because simply reverting the \noriginal commit alone would leave the driver vulnerable to worse race \nconditions. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T06:49:23.000000Z"} https://vulnerability.circl.lu/sighting/3da6a33f-0407-42bd-8631-09ba822aef47/export Thu, 22 Aug 2024 06:49:23 +0000 https://vulnerability.circl.lu/sighting/78aaa997-4ba9-42dd-8ed9-45942b8f6b63/export {"uuid": "78aaa997-4ba9-42dd-8ed9-45942b8f6b63", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48944", "type": "seen", "source": "https://t.me/cvedetector/4515", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48944 - Linux Kernel Sched Vulnerability\", \n \"Content\": \"CVE ID : CVE-2022-48944 \nPublished : Aug. 30, 2024, 11:15 a.m. | 40\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nsched: Fix yet more sched_fork() races \n \nWhere commit 4ef0c5c6b5ba (\"kernel/sched: Fix sched_fork() access an \ninvalid sched_task_group\") fixed a fork race vs cgroup, it opened up a \nrace vs syscalls by not placing the task on the runqueue before it \ngets exposed through the pidhash. \n \nCommit 13765de8148f (\"sched/fair: Fix fault in reweight_entity\") is \ntrying to fix a single instance of this, instead fix the whole class \nof issues, effectively reverting this commit. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"30 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-30T13:58:47.000000Z"} {"uuid": "78aaa997-4ba9-42dd-8ed9-45942b8f6b63", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48944", "type": "seen", "source": "https://t.me/cvedetector/4515", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48944 - Linux Kernel Sched Vulnerability\", \n \"Content\": \"CVE ID : CVE-2022-48944 \nPublished : Aug. 30, 2024, 11:15 a.m. | 40\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nsched: Fix yet more sched_fork() races \n \nWhere commit 4ef0c5c6b5ba (\"kernel/sched: Fix sched_fork() access an \ninvalid sched_task_group\") fixed a fork race vs cgroup, it opened up a \nrace vs syscalls by not placing the task on the runqueue before it \ngets exposed through the pidhash. \n \nCommit 13765de8148f (\"sched/fair: Fix fault in reweight_entity\") is \ntrying to fix a single instance of this, instead fix the whole class \nof issues, effectively reverting this commit. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"30 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-30T13:58:47.000000Z"} https://vulnerability.circl.lu/sighting/78aaa997-4ba9-42dd-8ed9-45942b8f6b63/export Fri, 30 Aug 2024 13:58:47 +0000 https://vulnerability.circl.lu/sighting/210d9e0c-7a03-4878-a6c4-d774354f6968/export {"uuid": "210d9e0c-7a03-4878-a6c4-d774354f6968", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48945", "type": "seen", "source": "https://t.me/cvedetector/6179", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48945 - \"Vivid Linux Kernel Media Driver Out-of-Bounds Write Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2022-48945 \nPublished : Sept. 23, 2024, 10:15 a.m. | 40\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nmedia: vivid: fix compose size exceed boundary \n \nsyzkaller found a bug: \n \n BUG: unable to handle page fault for address: ffffc9000a3b1000 \n #PF: supervisor write access in kernel mode \n #PF: error_code(0x0002) - not-present page \n PGD 100000067 P4D 100000067 PUD 10015f067 PMD 1121ca067 PTE 0 \n Oops: 0002 [#1] PREEMPT SMP \n CPU: 0 PID: 23489 Comm: vivid-000-vid-c Not tainted 6.1.0-rc1+ #512 \n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 \n RIP: 0010:memcpy_erms+0x6/0x10 \n[...] \n Call Trace: \n \n ? tpg_fill_plane_buffer+0x856/0x15b0 \n vivid_fillbuff+0x8ac/0x1110 \n vivid_thread_vid_cap_tick+0x361/0xc90 \n vivid_thread_vid_cap+0x21a/0x3a0 \n kthread+0x143/0x180 \n ret_from_fork+0x1f/0x30 \n \n \nThis is because we forget to check boundary after adjust compose->height \nint V4L2_SEL_TGT_CROP case. Add v4l2_rect_map_inside() to fix this problem \nfor this case. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"23 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-23T12:58:19.000000Z"} {"uuid": "210d9e0c-7a03-4878-a6c4-d774354f6968", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48945", "type": "seen", "source": "https://t.me/cvedetector/6179", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48945 - \"Vivid Linux Kernel Media Driver Out-of-Bounds Write Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2022-48945 \nPublished : Sept. 23, 2024, 10:15 a.m. | 40\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nmedia: vivid: fix compose size exceed boundary \n \nsyzkaller found a bug: \n \n BUG: unable to handle page fault for address: ffffc9000a3b1000 \n #PF: supervisor write access in kernel mode \n #PF: error_code(0x0002) - not-present page \n PGD 100000067 P4D 100000067 PUD 10015f067 PMD 1121ca067 PTE 0 \n Oops: 0002 [#1] PREEMPT SMP \n CPU: 0 PID: 23489 Comm: vivid-000-vid-c Not tainted 6.1.0-rc1+ #512 \n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 \n RIP: 0010:memcpy_erms+0x6/0x10 \n[...] \n Call Trace: \n \n ? tpg_fill_plane_buffer+0x856/0x15b0 \n vivid_fillbuff+0x8ac/0x1110 \n vivid_thread_vid_cap_tick+0x361/0xc90 \n vivid_thread_vid_cap+0x21a/0x3a0 \n kthread+0x143/0x180 \n ret_from_fork+0x1f/0x30 \n \n \nThis is because we forget to check boundary after adjust compose->height \nint V4L2_SEL_TGT_CROP case. Add v4l2_rect_map_inside() to fix this problem \nfor this case. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"23 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-23T12:58:19.000000Z"} https://vulnerability.circl.lu/sighting/210d9e0c-7a03-4878-a6c4-d774354f6968/export Mon, 23 Sep 2024 12:58:19 +0000 https://vulnerability.circl.lu/sighting/8ab2e0e1-cd98-4598-aea1-b1068e999e8c/export {"uuid": "8ab2e0e1-cd98-4598-aea1-b1068e999e8c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2022-48943", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "8ab2e0e1-cd98-4598-aea1-b1068e999e8c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2022-48943", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} https://vulnerability.circl.lu/sighting/8ab2e0e1-cd98-4598-aea1-b1068e999e8c/export Wed, 03 Dec 2025 14:14:49 +0000