Astra Linux – Vulnerability found in Linux 6.12, Linux 6.1

In the Linux kernel, the following vulnerabilities have been resolved: x86/iopl: Fixed inconsistencies in TIFIOBITMAP The function iobitmapexit is called from exitthread, when a task exists or when a fork fails. In the latter case, exitthread cleans up resources that were allocated during fork...

[SECURITY] Fedora 42 Update: dtk6log-0.0.2-13.fc42

Simple, convenient and thread safe logger for Qt-based C++ apps...

CVE-2025-10151 Malicious TCP/IP thread locking leads into diverse malfunctions

Improper locking vulnerability in Softing Industrial Automation GmbH gateways allows infected memory and/or resource leak exposure.This issue affects smartLink HW-PN: from 1.02 through 1.03 smartLink HW-DP: 1.31...

CVE-2025-10151

CVE-2025-10151 affects Softing Industrial Automation GmbH gateways, specifically SmartLink HW-PN (versions 1.02–1.03) and SmartLink HW-DP (version 1.31). The issue stems from improper locking, potentially causing memory and/or resource leaks. Impact is described as exposure of infected memory and...

PT-2025-53012

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A flaw exists in the Linux kernel’s SPI subsystem, specifically within the tegra210-quad driver. Under conditions of high CPU load on the processor handling QSPI interrupts typically CPU...

AZL-68799 CVE-2025-40024 affecting package kernel for versions less than 6.6.112.1-2

In the Linux kernel, the following vulnerability has been resolved: vhost: Take a reference on the task in struct vhosttask. vhosttaskcreate creates a task and keeps a reference to its taskstruct. That task may exit early via a signal and its taskstruct will be released. A pending vhosttaskwake...

Nutanix AOS : Multiple Vulnerabilities (NXSA-AOS-7.0.1.9)

The version of AOS installed on the remote host is prior to 7.0.1.9. It is, therefore, affected by multiple vulnerabilities as referenced in the NXSA-AOS-7.0.1.9 advisory. - There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number o...

EUVD-2023-60000

In the Linux kernel, the following vulnerability has been resolved: posix-timers: Ensure timer ID search-loop limit is valid posixtimeradd tries to allocate a posix timer ID by starting from the cached ID which was stored by the last successful allocation. This is done in a loop searching the ID...

CVE-2022-50564: Undefined Security Weakness

In the Linux kernel, the following vulnerability has been resolved: s390/netiucv: Fix return type of netiucvtx With clang's kernel control flow integrity kCFI, CONFIGCFICLANG, indirect call targets are validated against the expected function pointer prototype to make sure the call target is valid...

Linux Kernel Security Vulnerabilities

Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in the Linux kernel that stems from a mismatch in the return type of the netiucvtx function, which could lead to a kernel panic or thread...

PT-2025-52468

Уязвимость функции ParamsCalculator::makeFromValues модуля ParamsCalculator.cpp системы управления базами данных «Ред База Данных» связана c взаимной блокировкой потоков выполнения. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, вызвать отказ в обслуживании...

CVE-2025-55079

In Eclipse ThreadX before version 6.4.3, the thread module has a setting of maximum priority. In some cases the check of that maximum priority wasn't performed, allowing, as a result, to obtain a thread with higher priority than expected and causing a possible denial of service...

CVE-2025-55079

In Eclipse ThreadX before version 6.4.3, the thread module has a setting of maximum priority. In some cases the check of that maximum priority wasn't performed, allowing, as a result, to obtain a thread with higher priority than expected and causing a possible denial of service...

CVE-2025-55079

CVE-2025-55079 refers to Eclipse ThreadX RTOS prior to 6.4.3, where the thread module’s maximum priority check could be bypassed, allowing a thread to run at a higher priority than intended and cause a potential denial of service. This is corroborated by Red Hat and other industry sources in the ...

CVE-2025-55079 Missing check for thread priority

In Eclipse ThreadX before version 6.4.3, the thread module has a setting of maximum priority. In some cases the check of that maximum priority wasn't performed, allowing, as a result, to obtain a thread with higher priority than expected and causing a possible denial of service...

CVE-2025-55079 Missing check for thread priority

In Eclipse ThreadX before version 6.4.3, the thread module has a setting of maximum priority. In some cases the check of that maximum priority wasn't performed, allowing, as a result, to obtain a thread with higher priority than expected and causing a possible denial of service...

CVE-2025-55079: Allocation of Resources Without Limits or Throttling

In Eclipse ThreadX before version 6.4.3, the thread module has a setting of maximum priority. In some cases the check of that maximum priority wasn't performed, allowing, as a result, to obtain a thread with higher priority than expected and causing a possible denial of service...

Eclipse ThreadX RTOS security vulnerabilities

Eclipse ThreadX RTOS is an advanced real-time operating system RTOS from Eclipse ThreadX designed for deeply embedded applications. A security vulnerability exists in Eclipse ThreadX RTOS versions prior to 6.4.3 that stems from not properly checking the maximum priority setting of the thread...

PT-2025-52910

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A flaw exists in the Linux kernel related to RCU protection within the md wakeup thread function. An attempt was made to use Read-Copy-Update RCU to protect a pointer, thread, but the...

PT-2025-42228

In Eclipse ThreadX before version 6.4.3, the thread module has a setting of maximum priority. In some cases the check of that maximum priority wasn't performed, allowing, as a result, to obtain a thread with higher priority than expected and causing a possible denial of service...