CVE-2026-74495
Linux kernel vulnerability
- Published15 Aug 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/0565052b7e2f436b7f1541f4849da96dc0aa7a0e
- https://git.kernel.org/stable/c/31089f4eab42e0fc248ec80c26f9b0bad59ba4cc
- https://git.kernel.org/stable/c/56726ff12cb6759ab90d6f5332c2377aeca7d249
- https://git.kernel.org/stable/c/845a9cdd9b03b7b6fa8de3ee80579780350a7f65
- https://git.kernel.org/stable/c/bc25d56c03e41c10bc4b40e99ca5d7b941675c04
- https://git.kernel.org/stable/c/df07003b5a6c6c9fce60d765d6a3da815a74c41c
- https://git.kernel.org/stable/c/e3ed89c257f6361f13df23023cd10ace830330ad
- https://git.kernel.org/stable/c/e42b7225c45f57b42306b80cdd3bda202bae7293
Frequently asked
Is CVE-2026-74495 being actively exploited?
CVE-2026-74495 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.76%.
How severe is CVE-2026-74495?
CVE-2026-74495 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.76% probability of exploitation.
How do I fix CVE-2026-74495?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-74495 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.