r8169: Fix possible ring buffer corruption on fragmented Tx packets.
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9020845fb5d6bb4876a38fdf1259600e7d9a63d4 · < 54e7a0d111240c92c0f02ceba6eb8f26bf6d6479| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
r8169: Fix possible ring buffer corruption on fragmented Tx packets.
An issue was found on the RTL8125b when transmitting small fragmented packets, whereby invalid entries were inserted into the transmit ring buffer, subsequently leading to calls to dma_unmap_single() with a null address.
This was caused by rtl8169_start_xmit() not noticing changes to nr_frags which may occur when small packets are padded (to work around hardware quirks) in rtl8169_tso_csum_v2().
To fix this, postpone inspecting nr_frags until after any padding has been applied.
From the CVE record · Linux
On systems using the RTL8125b, the Linux kernel’s r8169 driver can insert invalid transmit-ring entries when sending small fragmented packets. This can lead to a call to dma_unmap_single() with a null address. The input does not establish whether an attacker can trigger this remotely or locally, or whether authentication or user interaction is required.
Engineers running Linux systems with RTL8125b hardware should check their kernel’s r8169 driver; affected versions were not provided.