af_packet: avoid erroring out after sock_init_data() in packet_create()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b013840810c221f2b0cf641d01531526052dc1fb · < fd09880b16d33aa5a7420578e01cd79148fa9829| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
af_packet: avoid erroring out after sock_init_data() in packet_create()
After sock_init_data() the allocated sk object is attached to the provided sock object. On error, packet_create() frees the sk object leaving the dangling pointer in the sock object on return. Some other code may try to use this pointer and cause use-after-free.
From the CVE record · Linux
If packet_create() fails after sock_init_data(), it can free an object while leaving a dangling pointer in the socket. Later use of that pointer can cause a use-after-free. The input does not establish how an attacker could trigger this or whether authentication or user interaction is required.
Engineers running the Linux kernel should check their versions; affected versions are not specified.