sock_map: fix a NULL pointer dereference in sock_map_link_update_prog()
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:
sock_map: fix a NULL pointer dereference in sock_map_link_update_prog()
The following race condition could trigger a NULL pointer dereference:
sock_map_link_detach(): sock_map_link_update_prog(): mutex_lock(&sockmap_mutex); ... sockmap_link->map = NULL; mutex_unlock(&sockmap_mutex); mutex_lock(&sockmap_mutex); ... sock_map_prog_link_lookup(sockmap_link->map); mutex_unlock(&sockmap_mutex); <continue>
Fix it by adding a NULL pointer check. In this specific case, it makes no sense to update a link which is being released.
From the CVE record · Linux
A race between sock_map_link_detach() and sock_map_link_update_prog() can cause a NULL pointer dereference in the Linux kernel. It occurs when a link is detached while its program is being updated. The input does not specify whether exploitation requires network or local access, authentication, or user interaction.
Teams running the Linux kernel should check their installations; affected versions are not specified.