lkml.org 
[lkml]   [2012]   [Feb]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [kernel-hardening] Re: Add overflow protection to kref
    On 24 Feb 2012 at 23:13, Vasiliy Kulikov wrote:

    > > But in this case, the principle does not apply because we can recover.
    > > The reason we cannot recover from the stack protector case is because
    > > the stack protector is reacting after the fact, which is not the case
    > > here. Simply peg the reference count at the maximum value, neither
    > > incrementing it nor decrementing it further.
    >
    > ...and simply loose one reference, which leads to use-after-free.

    saturating the refcount keeps the protected object allocated, so it is
    a memory leak, but it is not a use-after-free.



    \
     
     \ /
      Last update: 2012-02-25 00:03    [W:7.674 / U:0.084 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site