Use after free in tcpslice triggers AddressSanitizer, no other confirmed impact.
Weakness
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Tcpslice | Tcpdump | * | 1.5 (excluding) |
| Red Hat Enterprise Linux 8 | RedHat | tcpdump-14:4.9.3-3.el8_9.1 | * |
| Red Hat Enterprise Linux 8.6 Extended Update Support | RedHat | tcpdump-14:4.9.3-3.el8_6.1 | * |
| Red Hat Enterprise Linux 8.8 Extended Update Support | RedHat | tcpdump-14:4.9.3-3.el8_8.1 | * |
| Red Hat Enterprise Linux 9 | RedHat | tcpdump-14:4.99.0-9.el9 | * |
| Red Hat Enterprise Linux 9.2 Extended Update Support | RedHat | tcpdump-14:4.99.0-6.el9_2.1 | * |
| Tcpslice | Ubuntu | bionic | * |
| Tcpslice | Ubuntu | focal | * |
| Tcpslice | Ubuntu | hirsute | * |
| Tcpslice | Ubuntu | impish | * |
| Tcpslice | Ubuntu | kinetic | * |
| Tcpslice | Ubuntu | lunar | * |
| Tcpslice | Ubuntu | mantic | * |
| Tcpslice | Ubuntu | oracular | * |
| Tcpslice | Ubuntu | plucky | * |
| Tcpslice | Ubuntu | trusty | * |
| Tcpslice | Ubuntu | xenial | * |