igbvf: Fix leak in TX DMA error cleanup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c1fa347f20f17f14a4a1575727fa24340e8a9117 · < 845a9cdd9b03b7b6fa8de3ee80579780350a7f65| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's igbvf driver can leak one DMA mapping when a TX buffer mapping fails after an earlier mapping succeeded. The input does not describe how an attacker could trigger this condition or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the igbvf driver should check whether their kernel is affected; no affected versions are specified.