Difference between revisions of "Bug Classes/Integer overflow"

From Linux Kernel Security Subsystem
Jump to: navigation, search
(Examples: paste-o)
Line 6: Line 6:
* [https://jon.oberheide.org/blog/2010/09/10/linux-kernel-can-slub-overflow/ slub overflow]
* [https://jon.oberheide.org/blog/2010/09/10/linux-kernel-can-slub-overflow/ slub overflow]
* [https://cyseclabs.com/page?n=02012016 refcount overflow]
* [https://cyseclabs.com/page?n=02012016 group_info refcount overflow]
* [https://googleplex-android-review.git.corp.google.com/849547 refcount overflow]
* [http://perception-point.io/2016/01/14/analysis-and-exploitation-of-a-linux-kernel-vulnerability-cve-2016-0728/ keyring refcount overflow]
= Mitigations =
= Mitigations =

Revision as of 21:02, 3 February 2016


Integer overflows (or underflows) occur when a multiplication happens that exceeds the size that can be represented by the datatype, generally wrapping around. This usually results in either writing to too-small buffers, or producing out of bound array indexes. Exploitation is most common via heap overflows, since the (too-small) buffers tend to be allocated on the heap. Additionally, reference counting can overflow and wrap around, leading to use-after-free exploits.



  • check for refcount overflows (e.g. PAX_REFCOUNT)
  • compiler instrumentation to detect multiplication overflows at runtime (e.g. PAX_SIZE_OVERFLOW)