From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 168153F0771 for ; Fri, 8 May 2026 14:25:59 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778250359; cv=none; b=ojauhQkooBP0cRmT+FNXcpX95zb5fttDr+cDHtZIwGkjm9KH4PN+bcaTCd1dk/P/uSfadSTCKwbem44frkOOhutuzlAO278pRCWTGIp6BYO0nDcvsz1+reaB2NWMVDXwH448cj/IQQqKy2kdoE3j14vhspf8OzkLOvhnpvKqHmY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778250359; c=relaxed/simple; bh=wkxZJNpRfkpTo1kgQI4iIETI7S7p4T+tCXhBDnih4hI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=NDceI5M9F+Rd7vn++U/EpTYGme6ZAfSw0Kz/97vM2NzZwGHj+5/fll3nob2G+v865kBhRBiWTEDkD5imiq84Ew8p3V5jFMH6ntPkHH83EX0w05yByfn/4zULl1+v1l86VCgiz/1umGo9V8unlxBaTldUvXBgjjjghyW+Ha5tqYo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=g8wJhIpw; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="g8wJhIpw" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A016EC2BCB0; Fri, 8 May 2026 14:25:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1778250359; bh=wkxZJNpRfkpTo1kgQI4iIETI7S7p4T+tCXhBDnih4hI=; h=From:To:Cc:Subject:Date:Reply-To:From; b=g8wJhIpwc06VKMtO1OyznMFtGFBnUDDfgmOHOV1y1m5V054Zjk7k4Xcdsuf5aZ1B8 9uMw2kB46o5eppZbtqhylqcsa+j2L6Mn6El7KTyoxQ8c1uU7cbB7Do/PZQr2TWBqSV G4IH/zAqjoF1csXEv+P/kekHGE5X9iHN8YE29HX8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-43445: e1000/e1000e: Fix leak in DMA error cleanup Date: Fri, 8 May 2026 16:22:54 +0200 Message-ID: <2026050855-CVE-2026-43445-4e53@gregkh> X-Mailer: git-send-email 2.54.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4152; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=K3zduf8GYYxYU8LYrJNbOkaCKo3ws3G1bg/KwaNYLCY=; b=owGbwMvMwCRo6H6F97bub03G02pJDJl/Pza/ZD1sq5r+K+PksQi/yJ8a20TyUi9eSedXfD4nt ukEa6pERywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEwkmI9hwWXnzmWpLP8nezh9 2C33tStCkXnJG4YFU6/L6xzfxzFnRvWWhYfCUo7t2DxDCAA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: e1000/e1000e: Fix leak in DMA error cleanup If an error is encountered while mapping TX buffers, the driver should unmap any buffers already mapped for that skb. Because count is incremented after a successful mapping, it will always match the correct number of unmappings needed when dma_error is reached. Decrementing count before the while loop in dma_error causes an off-by-one error. If any mapping was successful before an unsuccessful mapping, exactly one DMA mapping would leak. In these commits, a faulty while condition caused an infinite loop in dma_error: Commit 03b1320dfcee ("e1000e: remove use of skb_dma_map from e1000e driver") Commit 602c0554d7b0 ("e1000: remove use of skb_dma_map from e1000 driver") Commit c1fa347f20f1 ("e1000/e1000e/igb/igbvf/ixgb/ixgbe: Fix tests of unsigned in *_tx_map()") fixed the infinite loop, but introduced the off-by-one error. This issue may still exist in the igbvf driver, but I did not address it in this patch. The Linux kernel CVE team has assigned CVE-2026-43445 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.33 with commit c1fa347f20f17f14a4a1575727fa24340e8a9117 and fixed in 5.10.253 with commit 7eaeb778bfaa3b2a804f89321c234d59c74569db Issue introduced in 2.6.33 with commit c1fa347f20f17f14a4a1575727fa24340e8a9117 and fixed in 5.15.203 with commit 0606c24a745bafd1be5d66c48361638cd9cad74b Issue introduced in 2.6.33 with commit c1fa347f20f17f14a4a1575727fa24340e8a9117 and fixed in 6.1.167 with commit 519051c711dfd239ef6e4b28878efee400a035f9 Issue introduced in 2.6.33 with commit c1fa347f20f17f14a4a1575727fa24340e8a9117 and fixed in 6.6.130 with commit 0a1fc25deabab4efce64610e3c449485c4fa8f5f Issue introduced in 2.6.33 with commit c1fa347f20f17f14a4a1575727fa24340e8a9117 and fixed in 6.12.78 with commit fa5ba9867a55e640df0dc79bf0199770fb043f03 Issue introduced in 2.6.33 with commit c1fa347f20f17f14a4a1575727fa24340e8a9117 and fixed in 6.18.19 with commit 30e87ade8d678c25a8546cf38c0b498fa5cb27d3 Issue introduced in 2.6.33 with commit c1fa347f20f17f14a4a1575727fa24340e8a9117 and fixed in 6.19.9 with commit 10b5e65959e955a1c8894e0a5413944b5a70204a Issue introduced in 2.6.33 with commit c1fa347f20f17f14a4a1575727fa24340e8a9117 and fixed in 7.0 with commit e94eaef11142b01f77bf8ba4d0b59720b7858109 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-43445 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/net/ethernet/intel/e1000/e1000_main.c drivers/net/ethernet/intel/e1000e/netdev.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/7eaeb778bfaa3b2a804f89321c234d59c74569db https://git.kernel.org/stable/c/0606c24a745bafd1be5d66c48361638cd9cad74b https://git.kernel.org/stable/c/519051c711dfd239ef6e4b28878efee400a035f9 https://git.kernel.org/stable/c/0a1fc25deabab4efce64610e3c449485c4fa8f5f https://git.kernel.org/stable/c/fa5ba9867a55e640df0dc79bf0199770fb043f03 https://git.kernel.org/stable/c/30e87ade8d678c25a8546cf38c0b498fa5cb27d3 https://git.kernel.org/stable/c/10b5e65959e955a1c8894e0a5413944b5a70204a https://git.kernel.org/stable/c/e94eaef11142b01f77bf8ba4d0b59720b7858109