Total
8686 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2024-38925 | 1 Openrobotics | 1 Robot Operating System | 2026-06-17 | N/A | 9.8 CRITICAL |
| Open Robotics Robotic Operating System 2 (ROS2) and Nav2 humble versions were discovered to contain a use-after-free via the nav2_amcl process. This vulnerability is triggered via remotely sending a request for change the value of dynamic-parameter`/amcl z_max` . | |||||
| CVE-2024-38924 | 1 Openrobotics | 1 Robot Operating System | 2026-06-17 | N/A | 9.8 CRITICAL |
| Open Robotics Robotic Operating System 2 (ROS2) and Nav2 humble versions were discovered to contain a use-after-free via the nav2_amcl process. This vulnerability is triggered via remotely sending a request to change the value of dynamic-parameter`/amcl laser_model_type` . | |||||
| CVE-2024-38923 | 1 Openrobotics | 1 Robot Operating System | 2026-06-17 | N/A | 9.8 CRITICAL |
| Open Robotics Robotic Operating System 2 (ROS2) and Nav2 humble versions were discovered to contain a use-after-free via the nav2_amcl process. This vulnerability is triggered via remotely sending a request to change the value of dynamic-parameter`/amcl odom_frame_id` . | |||||
| CVE-2024-38921 | 1 Openrobotics | 1 Robot Operating System | 2026-06-17 | N/A | 9.8 CRITICAL |
| Open Robotics Robotic Operating System 2 (ROS2) and Nav2 humble versions were discovered to contain a use-after-free via the nav2_amcl process. This vulnerability is triggered via remotely sending a request for change the value of dynamic-parameter`/amcl z_rand ` . | |||||
| CVE-2024-38920 | 2026-06-17 | N/A | 9.1 CRITICAL | ||
| Open Robotics Robotic Operating System 2 (ROS2) and Nav2 humble versions were discovered to contain a use-after-free via the nav2_amcl process. This vulnerability is triggerd via remotely sending a request for change the value of dynamic-parameter`/amcl max_beams` . | |||||
| CVE-2024-38910 | 2026-06-17 | N/A | 7.5 HIGH | ||
| Open Robotics Robotic Operating System 2 (ROS2) and Nav2 humble version was discovered to contain a use-after-free in the nav2_amcl process. This vulnerability is triggered via sending a request to change dynamic parameters. | |||||
| CVE-2024-38630 | 1 Linux | 1 Linux Kernel | 2026-06-17 | N/A | 7.8 HIGH |
| In the Linux kernel, the following vulnerability has been resolved: watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger When the cpu5wdt module is removing, the origin code uses del_timer() to de-activate the timer. If the timer handler is running, del_timer() could not stop it and will return directly. If the port region is released by release_region() and then the timer handler cpu5wdt_trigger() calls outb() to write into the region that is released, the use-after-free bug will happen. Change del_timer() to timer_shutdown_sync() in order that the timer handler could be finished before the port region is released. | |||||
| CVE-2024-38629 | 1 Linux | 1 Linux Kernel | 2026-06-17 | N/A | 7.8 HIGH |
| In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Avoid unnecessary destruction of file_ida file_ida is allocated during cdev open and is freed accordingly during cdev release. This sequence is guaranteed by driver file operations. Therefore, there is no need to destroy an already empty file_ida when the WQ cdev is removed. Worse, ida_free() in cdev release may happen after destruction of file_ida per WQ cdev. This can lead to accessing an id in file_ida after it has been destroyed, resulting in a kernel panic. Remove ida_destroy(&file_ida) to address these issues. | |||||
| CVE-2024-38588 | 2 Debian, Linux | 2 Debian Linux, Linux Kernel | 2026-06-17 | N/A | 7.8 HIGH |
| In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix possible use-after-free issue in ftrace_location() KASAN reports a bug: BUG: KASAN: use-after-free in ftrace_location+0x90/0x120 Read of size 8 at addr ffff888141d40010 by task insmod/424 CPU: 8 PID: 424 Comm: insmod Tainted: G W 6.9.0-rc2+ [...] Call Trace: <TASK> dump_stack_lvl+0x68/0xa0 print_report+0xcf/0x610 kasan_report+0xb5/0xe0 ftrace_location+0x90/0x120 register_kprobe+0x14b/0xa40 kprobe_init+0x2d/0xff0 [kprobe_example] do_one_initcall+0x8f/0x2d0 do_init_module+0x13a/0x3c0 load_module+0x3082/0x33d0 init_module_from_file+0xd2/0x130 __x64_sys_finit_module+0x306/0x440 do_syscall_64+0x68/0x140 entry_SYSCALL_64_after_hwframe+0x71/0x79 The root cause is that, in lookup_rec(), ftrace record of some address is being searched in ftrace pages of some module, but those ftrace pages at the same time is being freed in ftrace_release_mod() as the corresponding module is being deleted: CPU1 | CPU2 register_kprobes() { | delete_module() { check_kprobe_address_safe() { | arch_check_ftrace_location() { | ftrace_location() { | lookup_rec() // USE! | ftrace_release_mod() // Free! To fix this issue: 1. Hold rcu lock as accessing ftrace pages in ftrace_location_range(); 2. Use ftrace_location_range() instead of lookup_rec() in ftrace_location(); 3. Call synchronize_rcu() before freeing any ftrace pages both in ftrace_process_locs()/ftrace_release_mod()/ftrace_free_mem(). | |||||
| CVE-2024-38561 | 1 Linux | 1 Linux Kernel | 2026-06-17 | N/A | 7.0 HIGH |
| In the Linux kernel, the following vulnerability has been resolved: kunit: Fix kthread reference There is a race condition when a kthread finishes after the deadline and before the call to kthread_stop(), which may lead to use after free. | |||||
| CVE-2024-38424 | 1 Qualcomm | 238 Ar8035, Ar8035 Firmware, Fastconnect 6200 and 235 more | 2026-06-17 | N/A | 7.8 HIGH |
| Memory corruption during GNSS HAL process initialization. | |||||
| CVE-2024-38421 | 1 Qualcomm | 154 Fastconnect 6200, Fastconnect 6200 Firmware, Fastconnect 7800 and 151 more | 2026-06-17 | N/A | 7.8 HIGH |
| Memory corruption while processing GPU commands. | |||||
| CVE-2024-38419 | 1 Qualcomm | 296 Ar8035, Ar8035 Firmware, Csra6620 and 293 more | 2026-06-17 | N/A | 7.8 HIGH |
| Memory corruption while invoking IOCTL calls from the use-space for HGSL memory node. | |||||
| CVE-2024-38415 | 1 Qualcomm | 356 215 Mobile Platform, 215 Mobile Platform Firmware, Ar8035 and 353 more | 2026-06-17 | N/A | 7.8 HIGH |
| Memory corruption while handling session errors from firmware. | |||||
| CVE-2024-38412 | 1 Qualcomm | 14 Fastconnect 7800, Fastconnect 7800 Firmware, Snapdragon 8 Gen 3 Mobile and 11 more | 2026-06-17 | N/A | 6.6 MEDIUM |
| Memory corruption while invoking IOCTL calls from user-space to kernel-space to handle session errors. | |||||
| CVE-2024-38411 | 1 Qualcomm | 36 Fastconnect 6900, Fastconnect 6900 Firmware, Fastconnect 7800 and 33 more | 2026-06-17 | N/A | 6.6 MEDIUM |
| Memory corruption while registering a buffer from user-space to kernel-space using IOCTL calls. | |||||
| CVE-2024-38402 | 1 Qualcomm | 336 Ar8035, Ar8035 Firmware, Csra6620 and 333 more | 2026-06-17 | N/A | 7.8 HIGH |
| Memory corruption while processing IOCTL call for getting group info. | |||||
| CVE-2024-38401 | 1 Qualcomm | 80 Ar8035, Ar8035 Firmware, C-v2x 9150 and 77 more | 2026-06-17 | N/A | 7.8 HIGH |
| Memory corruption while processing concurrent IOCTL calls. | |||||
| CVE-2024-38399 | 1 Qualcomm | 80 Fastconnect 6900, Fastconnect 6900 Firmware, Fastconnect 7800 and 77 more | 2026-06-17 | N/A | 8.4 HIGH |
| Memory corruption while processing user packets to generate page faults. | |||||
| CVE-2024-38375 | 2026-06-17 | N/A | 5.3 MEDIUM | ||
| @fastly/js-compute is a JavaScript SDK and runtime for building Fastly Compute applications. The implementation of several functions were determined to include a use-after-free bug. This bug could allow for unintended data loss if the result of the preceding functions were sent anywhere else, and often results in a guest trap causing services to return a 500. This bug has been fixed in version 3.16.0 of the `@fastly/js-compute` package. | |||||