An issue was discovered in the Linux kernel before 4.14.16. There is a use-after-free in net/sctp/socket.c for a held lock after a peel off, aka CID-a0ff660058b8.
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.
| Link | Tags |
|---|---|
| https://syzkaller.appspot.com/bug?id=a8d38d1b68ffc744c53bd9b9fc1dbd6c86b1afe2 | mailing list exploit third party advisory |
| https://sites.google.com/view/syzscope/warning-held-lock-freed | third party advisory exploit |
| https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0ff660058b88d12625a783ce9e5c1371c87951f | mailing list patch vendor advisory |
| https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.16 | mailing list release notes vendor advisory |
| https://security.netapp.com/advisory/ntap-20210720-0002/ | third party advisory |