PULSE
EN VIVO20señales / 24h
FEED
ransomplay reclama a MIE Solutions · GB · Professional Servicesransomplay reclama a Rilpa Enterprises · Not Foundransomplay reclama a Marconi Industrial Services · IT · Manufacturingransomqilin reclama a Synergy Interactive · US · Technologyransomqilin reclama a Energetic Development Corp · TW · Energy & Utilitiesransomqilin reclama a Panda Logistics Taichung Branch · TW · Transportationransomqilin reclama a East Field Corporation · JP · Agriculture and Food Productionransomqilin reclama a Chun Tai Sing Chemical Industry · HK · Manufacturingransomqilin reclama a pm-energy Die Solarexperten · DE · Energy & Utilitiesransomunsafe reclama a Constellation HomeBuilder Systems · US · Manufacturingransomqilin reclama a Harplast SRL · RO · Manufacturingransomqilin reclama a Price Shoes · MX · Retail & E-Commerceransomqilin reclama a Naval Interior Team · FI · Government & Defenseransomqilin reclama a Phithan Phanich · TH · Manufacturingransomplay reclama a MIE Solutions · GB · Professional Servicesransomplay reclama a Rilpa Enterprises · Not Foundransomplay reclama a Marconi Industrial Services · IT · Manufacturingransomqilin reclama a Synergy Interactive · US · Technologyransomqilin reclama a Energetic Development Corp · TW · Energy & Utilitiesransomqilin reclama a Panda Logistics Taichung Branch · TW · Transportationransomqilin reclama a East Field Corporation · JP · Agriculture and Food Productionransomqilin reclama a Chun Tai Sing Chemical Industry · HK · Manufacturingransomqilin reclama a pm-energy Die Solarexperten · DE · Energy & Utilitiesransomunsafe reclama a Constellation HomeBuilder Systems · US · Manufacturingransomqilin reclama a Harplast SRL · RO · Manufacturingransomqilin reclama a Price Shoes · MX · Retail & E-Commerceransomqilin reclama a Naval Interior Team · FI · Government & Defenseransomqilin reclama a Phithan Phanich · TH · Manufacturing
← Todos los CVEs
CVE Watch4 ago 2026

CVE-2022-49789

In the Linux kernel, the following vulnerability has been resolved: scsi: zfcp: Fix double free of FSF request when qdio send fails We use

CVSS

7.0

Alto

EPSS

0.2%

p9

KEV

Exploit Today

3

0-100

Publicado: 1 may 2025 · Última mod.: 4 ago 2026 · CWE-415

EPSS · 30d
0.2%EPSS · 30 días0.2%
2026-07-112026-08-08
Descripción técnica

In the Linux kernel, the following vulnerability has been resolved: scsi: zfcp: Fix double free of FSF request when qdio send fails We used to use the wrong type of integer in 'zfcp_fsf_req_send()' to cache the FSF request ID when sending a new FSF request. This is used in case the sending fails and we need to remove the request from our internal hash table again (so we don't keep an invalid reference and use it when we free the request again). In 'zfcp_fsf_req_send()' we used to cache the ID as 'int' (signed and 32 bit wide), but the rest of the zfcp code (and the firmware specification) handles the ID as 'unsigned long'/'u64' (unsigned and 64 bit wide [s390x ELF ABI]). For one this has the obvious problem that when the ID grows past 32 bit (this can happen reasonably fast) it is truncated to 32 bit when storing it in the cache variable and so doesn't match the original ID anymore. The second less obvious problem is that even when the original ID has not yet grown past 32 bit, as soon as the 32nd bit is set in the original ID (0x80000000 = 2'147'483'648) we will have a mismatch when we cast it back to 'unsigned long'. As the cached variable is of a signed type, the compiler will choose a sign-extending instruction to load the 32 bit variable into a 64 bit register (e.g.: 'lgf %r11,188(%r15)'). So once we pass the cached variable into 'zfcp_reqlist_find_rm()' to remove the request again all the leading zeros will be flipped to ones to extend the sign and won't match the original ID anymore (this has been observed in practice). If we can't successfully remove the request from the hash table again after 'zfcp_qdio_send()' fails (this happens regularly when zfcp cannot notify the adapter about new work because the adapter is already gone during e.g. a ChpID toggle) we will end up with a double free. We unconditionally free the request in the calling function when 'zfcp_fsf_req_send()' fails, but because the request is still in the hash table we end up with a stale memory reference, and once the zfcp adapter is either reset during recovery or shutdown we end up freeing the same memory twice. The resulting stack traces vary depending on the kernel and have no direct correlation to the place where the bug occurs. Here are three examples that have been seen in practice: list_del corruption. next->prev should be 00000001b9d13800, but was 00000000dead4ead. (next=00000001bd131a00) ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:62! monitor event: 0040 ilc:2 [#1] PREEMPT SMP Modules linked in: ... CPU: 9 PID: 1617 Comm: zfcperp0.0.1740 Kdump: loaded Hardware name: ... Krnl PSW : 0704d00180000000 00000003cbeea1f8 (__list_del_entry_valid+0x98/0x140) R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 Krnl GPRS: 00000000916d12f1 0000000080000000 000000000000006d 00000003cb665cd6 0000000000000001 0000000000000000 0000000000000000 00000000d28d21e8 00000000d3844000 00000380099efd28 00000001bd131a00 00000001b9d13800 00000000d3290100 0000000000000000 00000003cbeea1f4 00000380099efc70 Krnl Code: 00000003cbeea1e8: c020004f68a7 larl %r2,00000003cc8d7336 00000003cbeea1ee: c0e50027fd65 brasl %r14,00000003cc3e9cb8 #00000003cbeea1f4: af000000 mc 0,0 >00000003cbeea1f8: c02000920440 larl %r2,00000003cd12aa78 00000003cbeea1fe: c0e500289c25 brasl %r14,00000003cc3fda48 00000003cbeea204: b9040043 lgr %r4,%r3 00000003cbeea208: b9040051 lgr %r5,%r1 00000003cbeea20c: b9040032 lgr %r3,%r2 Call Trace: [<00000003cbeea1f8>] __list_del_entry_valid+0x98/0x140 ([<00000003cbeea1f4>] __list_del_entry_valid+0x94/0x140) [<000003ff7ff502fe>] zfcp_fsf_req_dismiss_all+0xde/0x150 [zfcp] [<000003ff7ff49cd0>] zfcp_erp_strategy_do_action+0x160/0x280 [zfcp] ---truncated---

Referencias oficiales
CVEs relacionados
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-203387.5 ALT
25.3%
8A vulnerability in the zip archive parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to improper memory handling when processing content in zip files during scanning. An attacker could exploit this vulnerability by submitting a crafted zip file for scanning. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate as a result of a memory double-free, resulting in a DoS condition on the affected software.2d
CVE-2026-436227.8 ALT
3.3%
1llama.cpp builds b1886 through b7445 contain a double free vulnerability in the LLaMA-Android JNI wrapper where new_1batch() allocates memory using malloc() while free_1batch() deallocates it using the C++ delete operator, causing heap metadata corruption. Attackers can trigger this memory management mismatch to cause denial of service through process crashes or potentially achieve arbitrary code execution depending on allocator state.2d
CVE-2026-55995
16.6%
5A Double Free vulnerability in open-iscsi allows an unauthenticated MITM attacker to cause DoS. This issue affects open-iscsi: from ? through 56718d4e9d1a4f51c30697b5c0534144bb41c9bb.10d
CVE-2026-17573
1.9%
1A double free vulnerability was discovered in the HDF5 library. Processing a crafted HDF5 file containing an oversized chunk size field via h5repack may cause the application to abort due to a double free.10d
CVE-2026-663737.5 ALT
40.4%
12Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE, allows remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer, because deleting both consumers via XGROUP DELCONSUMER leads to a double free. NOTE: this issue exists because of an incomplete fix for CVE-2026-25243.3d
CVE-2026-660328.8 ALT
19.7%
6libssh2 through 1.11.1, fixed in commit 5e47761, contains a double-free vulnerability in the sftp_open() function in src/sftp.c that allows a malicious SSH server to corrupt the heap of any authenticated client opening an SFTP session. When a server responds to SSH_FXP_OPEN with SSH_FXP_STATUS containing FX_OK, the response data buffer is freed, and if a subsequent sftp_packet_require() call returns a specific error such as LIBSSH2_ERROR_CHANNEL_PACKET_EXCEEDED, the same pointer is freed a second time, enabling tcache dup conditions on glibc systems that allow overlapping allocations and function pointer overwrites.3d