PULSE
FEED
ransomn0n reclama a Ingelectus Innovative Electrical Solutions S.L. · ES · Energy & Utilitiesransomwhitearmor reclama a Gamdom · Otherransomfalcon reclama a Beasley Allen Law Firm · US · Professional Servicesransomqilin reclama a RaceTrakka · AU · Retail & E-Commerceransomqilin reclama a Smith Feddeler & Smith · US · Professional Servicesransomqilin reclama a Delta Electric Power Association · US · Energy & Utilitiesransomqilin reclama a Bangor Wholesale Laminates · GB · Manufacturingransomqilin reclama a TeleTronic · ES · Technologyransomqilin reclama a FIRMENGRUPPE APPL Holding GmbH · DE · Otherransomqilin reclama a Premier Medical Group · US · Healthcareransomqilin reclama a Zachary Confections · US · Retail & E-Commerceransomqilin reclama a THOMAS JORDAN, P.A · US · Professional Servicesransomqilin reclama a Five Star Sheets · US · Retail & E-Commerceransomqilin reclama a Power Funding · GB · Financial Servicesransomn0n reclama a Ingelectus Innovative Electrical Solutions S.L. · ES · Energy & Utilitiesransomwhitearmor reclama a Gamdom · Otherransomfalcon reclama a Beasley Allen Law Firm · US · Professional Servicesransomqilin reclama a RaceTrakka · AU · Retail & E-Commerceransomqilin reclama a Smith Feddeler & Smith · US · Professional Servicesransomqilin reclama a Delta Electric Power Association · US · Energy & Utilitiesransomqilin reclama a Bangor Wholesale Laminates · GB · Manufacturingransomqilin reclama a TeleTronic · ES · Technologyransomqilin reclama a FIRMENGRUPPE APPL Holding GmbH · DE · Otherransomqilin reclama a Premier Medical Group · US · Healthcareransomqilin reclama a Zachary Confections · US · Retail & E-Commerceransomqilin reclama a THOMAS JORDAN, P.A · US · Professional Servicesransomqilin reclama a Five Star Sheets · US · Retail & E-Commerceransomqilin reclama a Power Funding · GB · Financial Services
← Todos los CVEs
CVE Watch19 oct 2026

CVE-2026-63996

In the Linux kernel, the following vulnerability has been resolved: ethtool: cmis: require exact CDB reply length Malicious SFP module cou

CVSS

7.8

Alto

EPSS

0.1%

p3

KEV

—

Exploit Today

1

0-100

Publicado: 19 jul 2026 · Última mod.: 19 oct 2026 · CWE-787

EPSS · 30d
0.1%EPSS · 30 días0.1%
2026-09-282026-10-25
Descripción técnica

In the Linux kernel, the following vulnerability has been resolved: ethtool: cmis: require exact CDB reply length Malicious SFP module could respond with rpl_len longer than what cmis_cdb_process_reply() expected, leading to OOB writes. Malicious HW is a bit theoretical but some modules may just be buggy and/or the reads may occasionally get corrupted, so let's protect the kernel. The existing check protects from short replies. We need to protect from long ones, too. All callers that pass a non-zero rpl_exp_len cast the reply payload to a fixed-layout struct and read fields at fixed offsets, with no version negotiation or short-reply handling: - cmis_cdb_validate_password() - cmis_cdb_module_features_get() - cmis_fw_update_fw_mng_features_get() so let's assume that responses longer than expected do not have to be handled gracefully here. Add a warning message to make the debug easier in case my understanding is wrong... Note that page_data->length (argument of kmalloc) comes from last arg to ethtool_cmis_page_init() which is rpl_exp_len. Note2 that AIs also like to point out overflows in args->req.payload itself (which is a fixed-size 120 B buffer, on the stack), but callers should be reading structs defined by the standard, so protecting from requests for more data than max seem like defensive programming.

Referencias oficiales
CVEs relacionados
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-1167416.5 MED
—
———Speex (libspeex) through 1.2.1 contains an out-of-bounds write vulnerability in speex_bits_read_whole_bytes() in libspeex/bits.c that mishandles length truncation for non-owned SpeexBits buffers. Attackers can stream crafted Speex data into buffers set up with speex_bits_init_buffer() or speex_bits_set_bit_buffer() to corrupt heap or stack memory and crash applications.3h
CVE-2026-1165905.9 MED
—
———snappy-java is a Java port of the snappy, a fast C++ compresser/decompresser developed by Google. Prior to 1.1.10.9, Snappy.arrayCopy(Object src, int offset, int byteLength, Object dest, int destOffset) passes caller-supplied ranges to native memcpy without validating either array, allowing negative or oversized byteLength and offset values to read or write outside array bounds and crash the JVM. SnappyOutputStream.rawWrite and SnappyInputStream.rawRead, including their typed-array write and read methods, pass caller-controlled ranges through this primitive, and typed-array byte-size calculations can overflow int. This issue is fixed in version 1.1.10.9.3h
CVE-2026-1165024.4 MED
—
———A flaw has been found in turboderp-org ExLlamaV2 up to 0.3.2. The impacted element is the function QMatrix::make_sequential of the file exllamav2/exllamav2_ext/cuda/q_matrix.cu of the component GPTQ Index Handler. Executing a manipulation of the argument g_idx can lead to out-of-bounds write. The attack needs to be launched locally. The project was informed of the problem early through an issue report but has not responded yet.4h
CVE-2026-1165437.5 ALT
—
———Open5GS 1.3.0 through 2.8.0 contains a heap out-of-bounds write vulnerability in parse_multipart() that allows unauthenticated attackers to corrupt memory by supplying an empty multipart boundary. Attackers can send a single crafted multipart/related request to the SBI interface of any network function, overflowing the lookbehind buffer and crashing it.9h
CVE-2026-1165395.9 MED
—
———Netty netty-tcnative before 2.0.84.Final contains a heap buffer overflow vulnerability in the tcn_write_to_bytebuffer BIO callback caused by failing to wrap the non-application ring buffer write index. Remote TLS peers can drive handshake, renegotiation, or post-handshake messages into this buffer, triggering an out-of-bounds memcpy that crashes the JVM process.8h
CVE-2026-829477.1 ALT
—
——0SOEM version 2.0.0 and earlier contains multiple vulnerabilities in frame processing where a malicious device can cause the master to read data outside allocated buffers. The software uses length and offset values from device messages without validating them against buffer sizes. This can cause the master to access invalid memory locations, potentially disclosing sensitive information or causing crashes.11h