Vulnerabilities

Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.9.8.8, Vigor 2860/2925 prior to v3.9.7, Vigor 2862/2926 prior to v3.9.9.4, Vigor 2133/2762/2832 prior to v3.9.8, Vigor 2135/2765/2766 prior to v4.4.5.1, Vigor 2865/2866/2927 prior to v4.4.5.3, Vigor 2962/3910 prior to v4.3.2.7, Vigor 3912 prior to v4.3.5.2, and Vigor 2925 up to v3.9.6 were discovered to not utilize certificate verification, allowing attackers to upload crafted APPE modules from non-official servers, leading to arbitrary code execution.

A NULL pointer dereference in Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.9.8.8, Vigor 2860/2925 prior to v3.9.7, Vigor 2862/2926 prior to v3.9.9.4, Vigor 2133/2762/2832 prior to v3.9.8, Vigor 2135/2765/2766 prior to v4.4.5.1, Vigor 2865/2866/2927 prior to v4.4.5.3, Vigor 2962/3910 prior to v4.3.2.7, Vigor 3912 prior to v4.3.5.2, and Vigor 2925 up to v3.9.6 allows attackers to cause a Denial of Service (DoS) via a crafted DHCP request.

An issue in the CGI endpoint used to upload configurations in Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.9.8.8, Vigor 2860/2925 prior to v3.9.7, Vigor 2862/2926 prior to v3.9.9.4, Vigor 2133/2762/2832 prior to v3.9.8, Vigor 2135/2765/2766 prior to v4.4.5.1, Vigor 2865/2866/2927 prior to v4.4.5.3, Vigor 2962/3910 prior to v4.3.2.7, Vigor 3912 prior to v4.3.5.2, and Vigor 2925 up to v3.9.6 allows attackers to upload a crafted kernel module, allowing for arbitrary code execution.

An issue in Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.9.8.8, Vigor 2860/2925 prior to v3.9.7, Vigor 2862/2926 prior to v3.9.9.4, Vigor 2133/2762/2832 prior to v3.9.8, Vigor 2135/2765/2766 prior to v4.4.5.1, Vigor 2865/2866/2927 prior to v4.4.5.3, Vigor 2962/3910 prior to v4.3.2.7, Vigor 3912 prior to v4.3.5.2, and Vigor 2925 up to v3.9.6 allows attackers to upload crafted APP Enforcement modules, leading to arbitrary code execution.

Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.9.8.8, Vigor 2860/2925 prior to v3.9.7, Vigor 2862/2926 prior to v3.9.9.4, Vigor 2133/2762/2832 prior to v3.9.8, Vigor 2135/2765/2766 prior to v4.4.5.1, Vigor 2865/2866/2927 prior to v4.4.5.3, Vigor 2962/3910 prior to v4.3.2.7, Vigor 3912 prior to v4.3.5.2, and Vigor 2925 up to v3.9.6 were discovered to utilize insecure versions of the functions strcmp and memcmp, allowing attackers to possibly obtain sensitive information via timing attacks.

Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.9.8.8, Vigor 2860/2925 prior to v3.9.7, Vigor 2862/2926 prior to v3.9.9.4, Vigor 2133/2762/2832 prior to v3.9.8, Vigor 2135/2765/2766 prior to v4.4.5.1, Vigor 2865/2866/2927 prior to v4.4.5.3, Vigor 2962/3910 prior to v4.3.2.7, Vigor 3912 prior to v4.3.5.2, and Vigor 2925 up to v3.9.6 were discovered to store passwords in plaintext.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ptp: vmclock: Set driver data before its usage<br /> <br /> If vmclock_ptp_register() fails during probing, vmclock_remove() is<br /> called to clean up the ptp clock and misc device.<br /> It uses dev_get_drvdata() to access the vmclock state.<br /> However the driver data is not yet set at this point.<br /> <br /> Assign the driver data earlier.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> block: mark GFP_NOIO around sysfs -&gt;store()<br /> <br /> sysfs -&gt;store is called with queue freezed, meantime we have several<br /> -&gt;store() callbacks(update_nr_requests, wbt, scheduler) to allocate<br /> memory with GFP_KERNEL which may run into direct reclaim code path,<br /> then potential deadlock can be caused.<br /> <br /> Fix the issue by marking NOIO around sysfs -&gt;store()

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mm/compaction: fix UBSAN shift-out-of-bounds warning<br /> <br /> syzkaller reported a UBSAN shift-out-of-bounds warning of (1UL

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> gpu: host1x: Fix a use of uninitialized mutex<br /> <br /> commit c8347f915e67 ("gpu: host1x: Fix boot regression for Tegra")<br /> caused a use of uninitialized mutex leading to below warning when<br /> CONFIG_DEBUG_MUTEXES and CONFIG_DEBUG_LOCK_ALLOC are enabled.<br /> <br /> [ 41.662843] ------------[ cut here ]------------<br /> [ 41.663012] DEBUG_LOCKS_WARN_ON(lock-&gt;magic != lock)<br /> [ 41.663035] WARNING: CPU: 4 PID: 794 at kernel/locking/mutex.c:587 __mutex_lock+0x670/0x878<br /> [ 41.663458] Modules linked in: rtw88_8822c(+) bluetooth(+) rtw88_pci rtw88_core mac80211 aquantia libarc4 crc_itu_t cfg80211 tegra194_cpufreq dwmac_tegra(+) arm_dsu_pmu stmmac_platform stmmac pcs_xpcs rfkill at24 host1x(+) tegra_bpmp_thermal ramoops reed_solomon fuse loop nfnetlink xfs mmc_block rpmb_core ucsi_ccg ina3221 crct10dif_ce xhci_tegra ghash_ce lm90 sha2_ce sha256_arm64 sha1_ce sdhci_tegra pwm_fan sdhci_pltfm sdhci gpio_keys rtc_tegra cqhci mmc_core phy_tegra_xusb i2c_tegra tegra186_gpc_dma i2c_tegra_bpmp spi_tegra114 dm_mirror dm_region_hash dm_log dm_mod<br /> [ 41.665078] CPU: 4 UID: 0 PID: 794 Comm: (udev-worker) Not tainted 6.11.0-29.31_1538613708.el10.aarch64+debug #1<br /> [ 41.665838] Hardware name: NVIDIA NVIDIA Jetson AGX Orin Developer Kit/Jetson, BIOS 36.3.0-gcid-35594366 02/26/2024<br /> [ 41.672555] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)<br /> [ 41.679636] pc : __mutex_lock+0x670/0x878<br /> [ 41.683834] lr : __mutex_lock+0x670/0x878<br /> [ 41.688035] sp : ffff800084b77090<br /> [ 41.691446] x29: ffff800084b77160 x28: ffffdd4bebf7b000 x27: ffffdd4be96b1000<br /> [ 41.698799] x26: 1fffe0002308361c x25: 1ffff0001096ee18 x24: 0000000000000000<br /> [ 41.706149] x23: 0000000000000000 x22: 0000000000000002 x21: ffffdd4be6e3c7a0<br /> [ 41.713500] x20: ffff800084b770f0 x19: ffff00011841b1e8 x18: 0000000000000000<br /> [ 41.720675] x17: 0000000000000000 x16: 0000000000000000 x15: 0720072007200720<br /> [ 41.728023] x14: 0000000000000000 x13: 0000000000000001 x12: ffff6001a96eaab3<br /> [ 41.735375] x11: 1fffe001a96eaab2 x10: ffff6001a96eaab2 x9 : ffffdd4be4838bbc<br /> [ 41.742723] x8 : 00009ffe5691554e x7 : ffff000d4b755593 x6 : 0000000000000001<br /> [ 41.749985] x5 : ffff000d4b755590 x4 : 1fffe0001d88f001 x3 : dfff800000000000<br /> [ 41.756988] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000ec478000<br /> [ 41.764251] Call trace:<br /> [ 41.766695] __mutex_lock+0x670/0x878<br /> [ 41.770373] mutex_lock_nested+0x2c/0x40<br /> [ 41.774134] host1x_intr_start+0x54/0xf8 [host1x]<br /> [ 41.778863] host1x_runtime_resume+0x150/0x228 [host1x]<br /> [ 41.783935] pm_generic_runtime_resume+0x84/0xc8<br /> [ 41.788485] __rpm_callback+0xa0/0x478<br /> [ 41.792422] rpm_callback+0x15c/0x1a8<br /> [ 41.795922] rpm_resume+0x698/0xc08<br /> [ 41.799597] __pm_runtime_resume+0xa8/0x140<br /> [ 41.803621] host1x_probe+0x810/0xbc0 [host1x]<br /> [ 41.807909] platform_probe+0xcc/0x1a8<br /> [ 41.811845] really_probe+0x188/0x800<br /> [ 41.815347] __driver_probe_device+0x164/0x360<br /> [ 41.819810] driver_probe_device+0x64/0x1a8<br /> [ 41.823834] __driver_attach+0x180/0x490<br /> [ 41.827773] bus_for_each_dev+0x104/0x1a0<br /> [ 41.831797] driver_attach+0x44/0x68<br /> [ 41.835296] bus_add_driver+0x23c/0x4e8<br /> [ 41.839235] driver_register+0x15c/0x3a8<br /> [ 41.843170] __platform_register_drivers+0xa4/0x208<br /> [ 41.848159] tegra_host1x_init+0x4c/0xff8 [host1x]<br /> [ 41.853147] do_one_initcall+0xd4/0x380<br /> [ 41.856997] do_init_module+0x1dc/0x698<br /> [ 41.860758] load_module+0xc70/0x1300<br /> [ 41.864435] __do_sys_init_module+0x1a8/0x1d0<br /> [ 41.868721] __arm64_sys_init_module+0x74/0xb0<br /> [ 41.873183] invoke_syscall.constprop.0+0xdc/0x1e8<br /> [ 41.877997] do_el0_svc+0x154/0x1d0<br /> [ 41.881671] el0_svc+0x54/0x140<br /> [ 41.884820] el0t_64_sync_handler+0x120/0x130<br /> [ 41.889285] el0t_64_sync+0x1a4/0x1a8<br /> [ 41.892960] irq event stamp: 69737<br /> [ 41.896370] hardirqs last enabled at (69737): [] _raw_spin_unlock_irqrestore+0x44/0xe8<br /> [ 41.905739] hardirqs last disabled at (69736):<br /> ---truncated---

elestio memos v0.23.0 is vulnerable to Server-Side Request Forgery (SSRF) due to insufficient validation of user-supplied URLs, which can be exploited to perform SSRF attacks.