CVE-2026-74495igbvf: Fix leak in TX DMA error cleanup
- 9.8CriticalCVSS base score
- 0.51%Exploitation in 30 daysEPSS · top 56% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: igbvf: Fix leak in TX 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 before each frag 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 (the head) would leak. This bug was introduced by a 2010 fix for an endless loop in dma_error. All other affected drivers have already been fixed.
Timeline
ID reserved
By Linux
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.51% · top 56% of all CVEs (13 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected c1fa347f20f17f14a4a1575727fa24340e8a9117 – < e42b7225c45f57b42306b80cdd3bda202bae7293
- affected c1fa347f20f17f14a4a1575727fa24340e8a9117 – < e3ed89c257f6361f13df23023cd10ace830330ad
- affected c1fa347f20f17f14a4a1575727fa24340e8a9117 – < 56726ff12cb6759ab90d6f5332c2377aeca7d249
- affected c1fa347f20f17f14a4a1575727fa24340e8a9117 – < 31089f4eab42e0fc248ec80c26f9b0bad59ba4cc
- affected c1fa347f20f17f14a4a1575727fa24340e8a9117 – < bc25d56c03e41c10bc4b40e99ca5d7b941675c04
- affected c1fa347f20f17f14a4a1575727fa24340e8a9117 – < 845a9cdd9b03b7b6fa8de3ee80579780350a7f65
- affected c1fa347f20f17f14a4a1575727fa24340e8a9117 – < df07003b5a6c6c9fce60d765d6a3da815a74c41c
- affected c1fa347f20f17f14a4a1575727fa24340e8a9117 – < 0565052b7e2f436b7f1541f4849da96dc0aa7a0e
- affected 2.6.33
- unaffected < 2.6.33
- unaffected 5.10.265 – ≤ 5.10.*
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.151 – ≤ 6.6.*
- unaffected 6.12.103 – ≤ 6.12.*
- unaffected 6.18.44 – ≤ 6.18.*
- unaffected 7.1.8 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/e42b7225c45f57b42306b80cdd3bda202bae7293 (opens in a new tab)
- https://git.kernel.org/stable/c/e3ed89c257f6361f13df23023cd10ace830330ad (opens in a new tab)
- https://git.kernel.org/stable/c/56726ff12cb6759ab90d6f5332c2377aeca7d249 (opens in a new tab)
- https://git.kernel.org/stable/c/31089f4eab42e0fc248ec80c26f9b0bad59ba4cc (opens in a new tab)
- https://git.kernel.org/stable/c/bc25d56c03e41c10bc4b40e99ca5d7b941675c04 (opens in a new tab)
- https://git.kernel.org/stable/c/845a9cdd9b03b7b6fa8de3ee80579780350a7f65 (opens in a new tab)
- https://git.kernel.org/stable/c/df07003b5a6c6c9fce60d765d6a3da815a74c41c (opens in a new tab)
- https://git.kernel.org/stable/c/0565052b7e2f436b7f1541f4849da96dc0aa7a0e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59688 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74495)Record last updated .