net: l2tp: do not propagate multicast notification errors
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 33f72e6f0c67f673fd0c63a8182dbd9ffb8cf50b · < af20e269f7459d2ce69887fdf2fad7caf986c865| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: l2tp: do not propagate multicast notification errors
The tunnel create, tunnel modify, session create, and session modify netlink handlers send multicast notifications through helpers that can fail while allocating or encoding a message, or while multicasting it.
For tunnel and session create/modify, a notification is sent after the live operation has completed. Returning a best-effort notification error as the command result can therefore report failure for an operation that already committed and can cause callers to retry and accumulate live objects.
Keep sending notifications for listener visibility, but do not propagate their best-effort status as the command result. This also keeps the tunnel modify command consistent with the other notification-only paths.
From the CVE record · Linux
Linux kernel L2TP netlink create and modify handlers can report failure when a multicast notification fails, even though the operation has already completed. A caller able to issue these commands may retry and accumulate live tunnel or session objects. The input does not specify affected versions or additional access requirements.
Engineers running Linux kernels with L2TP support should check whether their versions are affected; affected versions are not specified.