29354 matches found
CVE-2026-93543
An out-of-bounds read exists in the XI2 class parser of libXi prior to version 1.8.4 . This vulnerability could be exploited by a malicious X server to cause a crash in an attached X client. No specific exploits or in-the-wild exploitation details are provided in the documents.
EUVD-2026-86062
In the Linux kernel, the following vulnerability has been resolved: ACPICA: Add package limit checks in parser functions Add package limit checks in parser functions to prevent out-of-bounds access...
CVE-2026-97449
The Linux kernel contains a vulnerability in the ACPICA component where parser functions lacked sufficient package limit checks. This oversight could lead to out-of-bounds access . The issue has been resolved by adding the necessary package limit checks to the parser functions. No specific exploi...
CVE-2026-97449 ACPICA: Add package limit checks in parser functions
In the Linux kernel, the following vulnerability has been resolved: ACPICA: Add package limit checks in parser functions Add package limit checks in parser functions to prevent out-of-bounds access...
EUVD-2026-86176
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: bound aligned TLV advance in FW parser Validate ALIGNtlvlen, 4 against remaining parser length before consuming bytes from the firmware image. This avoids length underflow on malformed TLVs...
CVE-2026-93789
The Linux kernel contains a vulnerability in the wifi: iwlwifi driver's firmware parser. The issue is caused by a failure to validate the ALIGN(tlv_len, 4) against the remaining parser length before consuming bytes from a firmware image. This oversight can lead to a length underflow when processi...
CVE-2026-93789 wifi: iwlwifi: bound aligned TLV advance in FW parser
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: bound aligned TLV advance in FW parser Validate ALIGNtlvlen, 4 against remaining parser length before consuming bytes from the firmware image. This avoids length underflow on malformed TLVs...
CVE-2026-93789 wifi: iwlwifi: bound aligned TLV advance in FW parser
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: bound aligned TLV advance in FW parser Validate ALIGNtlvlen, 4 against remaining parser length before consuming bytes from the firmware image. This avoids length underflow on malformed TLVs...
CVE-2026-93213
In the Linux kernel, the following vulnerability has been resolved: of: fix out-of-bounds read in ofaliasscan stem parser The stem parser tests isdigitend - 1 before checking end start and so reads one byte before the property name when the name is empty or all digits. Check the bound first...
EUVD-2026-85942
In the Linux kernel, the following vulnerability has been resolved: of: fix out-of-bounds read in ofaliasscan stem parser The stem parser tests isdigitend - 1 before checking end start and so reads one byte before the property name when the name is empty or all digits. Check the bound first...
CVE-2026-93213 of: fix out-of-bounds read in of_alias_scan() stem parser
In the Linux kernel, the following vulnerability has been resolved: of: fix out-of-bounds read in ofaliasscan stem parser The stem parser tests isdigitend - 1 before checking end start and so reads one byte before the property name when the name is empty or all digits. Check the bound first...
CVE-2026-93213
The Linux kernel contains an out-of-bounds read vulnerability in the of_alias_scan() stem parser. The flaw occurs because the parser evaluates isdigit(*(end - 1)) before verifying that end > start. This logic error causes the system to read one byte before the property name when the name is em...
CVE-2026-93213 of: fix out-of-bounds read in of_alias_scan() stem parser
In the Linux kernel, the following vulnerability has been resolved: of: fix out-of-bounds read in ofaliasscan stem parser The stem parser tests isdigitend - 1 before checking end start and so reads one byte before the property name when the name is empty or all digits. Check the bound first...
CVE-2026-97057
A flaw was found in redis-parser. This vulnerability allows a malicious or compromised Redis endpoint to trigger an uncaught RangeError by sending a crafted RESP REdis Serialization Protocol header with an excessively large declared length. The flaw occurs because redis-parser fails to validate t...
CVE-2026-97057
redis-parser through 3.0.0 fails to validate the multi-bulk length value in RESP protocol parsing, allowing attackers to trigger an uncaught RangeError by supplying an excessively large declared length. A malicious or compromised Redis endpoint can deliver a crafted RESP header with a length abov...
CVE-2026-97057
The redis-parser library, in versions through 3.0.0 , is vulnerable to a Denial of Service (DoS) attack due to improper validation of the multi-bulk length value during RESP protocol parsing . An attacker who controls or compromises a Redis endpoint can send a crafted RESP header with a declared ...
CVE-2026-97057 redis-parser through 3.0.0 Denial of Service via Invalid Array Length
redis-parser through 3.0.0 fails to validate the multi-bulk length value in RESP protocol parsing, allowing attackers to trigger an uncaught RangeError by supplying an excessively large declared length. A malicious or compromised Redis endpoint can deliver a crafted RESP header with a length abov...
EUVD-2026-85883
redis-parser through 3.0.0 fails to validate the multi-bulk length value in RESP protocol parsing, allowing attackers to trigger an uncaught RangeError by supplying an excessively large declared length. A malicious or compromised Redis endpoint can deliver a crafted RESP header with a length abov...
CVE-2026-97057 redis-parser through 3.0.0 Denial of Service via Invalid Array Length
redis-parser through 3.0.0 fails to validate the multi-bulk length value in RESP protocol parsing, allowing attackers to trigger an uncaught RangeError by supplying an excessively large declared length. A malicious or compromised Redis endpoint can deliver a crafted RESP header with a length abov...
CVE-2026-97057
redis-parser through 3.0.0 fails to validate the multi-bulk length value in RESP protocol parsing, allowing attackers to trigger an uncaught RangeError by supplying an excessively large declared length. A malicious or compromised Redis endpoint can deliver a crafted RESP header with a length abov...