eth: fbnic: Add validation for MTU changes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.146.19.47.0In the Linux kernel, the following vulnerability has been resolved:
eth: fbnic: Add validation for MTU changes
Increasing the MTU beyond the HDS threshold causes the hardware to fragment packets across multiple buffers. If a single-buffer XDP program is attached, the driver will drop all multi-frag frames. While we can't prevent a remote sender from sending non-TCP packets larger than the MTU, this will prevent users from inadvertently breaking new TCP streams.
Traditionally, drivers supported XDP with MTU less than 4Kb (packet per page). Fbnic currently prevents attaching XDP when MTU is too high. But it does not prevent increasing MTU after XDP is attached.
From the CVE record · Linux
The Linux kernel's fbnic driver allows the MTU to be increased beyond the HDS threshold after a single-buffer XDP program is attached. Packets that then span multiple buffers are dropped by the driver, potentially disrupting traffic; the described trigger is a local MTU change, not an authenticated or user-interaction-dependent attack.
Engineers running Linux systems that use the fbnic driver with a single-buffer XDP program should check their kernel versions against the vendor advisory; affected versions were not provided.