In the Linux kernel before 4.20.5, attackers can trigger a drivers/char/ipmi/ipmi_msghandler.c use-after-free and OOPS by arranging for certain simultaneous execution of the code, as demonstrated by a "service ipmievd restart" loop.
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 |
---|---|
http://www.securityfocus.com/bid/107145 | vdb entry third party advisory |
https://github.com/torvalds/linux/commit/77f8269606bf95fcb232ee86f6da80886f1dfae8 | third party advisory patch |
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.20.5 | release notes vendor advisory |
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=77f8269606bf95fcb232ee86f6da80886f1dfae8 | patch vendor advisory |
https://security.netapp.com/advisory/ntap-20190327-0002/ | third party advisory |
https://usn.ubuntu.com/3930-1/ | third party advisory vendor advisory |
https://usn.ubuntu.com/3930-2/ | third party advisory vendor advisory |
http://lists.opensuse.org/opensuse-security-announce/2019-05/msg00037.html | mailing list third party advisory vendor advisory |