netdev: prevent accessing NAPI instances from another namespace
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netdev: prevent accessing NAPI instances from another namespace
The NAPI IDs were not fully exposed to user space prior to the netlink API, so they were never namespaced. The netlink API must ensure that at the very least NAPI instance belongs to the same netns as the owner of the genl sock.
napi_by_id() can become static now, but it needs to move because of dev_get_by_napi_id().
From the CVE record · Linux
The Linux kernel netdev netlink API did not ensure that a NAPI instance belonged to the same network namespace as the requesting socket. A user-space caller able to use the API could access a NAPI instance from another namespace; the input does not specify authentication requirements or user interaction.
Operators running Linux kernels with the affected netdev netlink API should check their kernel versions against the vendor advisory; affected versions are not specified here.