CVE-2026-43445None▾ SunlitIn 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. Beca…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 6.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.1%
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.
Linux >= c1fa347f20f17f14a4a1575727fa24340e8a9117 < 7eaeb778bfaa3b2a804f89321c234d59c74569dbLinux >= c1fa347f20f17f14a4a1575727fa24340e8a9117 < 0606c24a745bafd1be5d66c48361638cd9cad74bLinux >= c1fa347f20f17f14a4a1575727fa24340e8a9117 < 519051c711dfd239ef6e4b28878efee400a035f9Linux >= c1fa347f20f17f14a4a1575727fa24340e8a9117 < 0a1fc25deabab4efce64610e3c449485c4fa8f5fLinux >= c1fa347f20f17f14a4a1575727fa24340e8a9117 < fa5ba9867a55e640df0dc79bf0199770fb043f03Linux >= c1fa347f20f17f14a4a1575727fa24340e8a9117 < 30e87ade8d678c25a8546cf38c0b498fa5cb27d3Linux >= c1fa347f20f17f14a4a1575727fa24340e8a9117 < 10b5e65959e955a1c8894e0a5413944b5a70204aLinux >= c1fa347f20f17f14a4a1575727fa24340e8a9117 < e94eaef11142b01f77bf8ba4d0b59720b7858109Linux 2.6.33Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses