Linux ksmbd denial of service in network namespace binding
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:
ksmbd: ignore network devices of other namespaces
With no interface list configured, ksmbd binds every interface that comes up. ksmbd_netdev_event() does not look at the device's namespace, and create_socket() opens the listener in the namespace of the task raising NETDEV_UP. A container with its own address on a bridge brings up its interface and finds port 445 in its namespace already taken by ksmbd, so an SMB server running inside the container fails with "Address already in use".
Interfaces are also matched by name only, so a container's eth0 going down would stop the listener on the host's eth0.
Only handle netdev events for devices in init_net.
From the CVE record · Linux
Linux kernel ksmbd handles network-device events from other namespaces when no interface list is configured. A container bringing up an interface can find port 445 already taken by ksmbd, preventing its SMB server from starting; a container interface going down can also stop the listener on a host interface with the same name.
Operators running Linux kernel ksmbd, particularly on hosts with containers and no ksmbd interface list configured, should check their systems; affected versions were not specified.