Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • linux
  • Repository
  • linux
  • crypto
  • cipher.c
Find file BlameHistoryPermalink
  • Herbert Xu's avatar
    [CRYPTO]: Fix stack overrun in crypt(). · e8bc549d
    Herbert Xu authored Jul 21, 2004
    
    
    The stack allocation in crypt() is bogus as whether tmp_src/tmp_dst
    is used is determined by factors unrelated to nbytes and
    src->length/dst->length.
    
    Since the condition for whether tmp_src/tmp_dst are used is very
    complex, let's allocate them always instead of guessing.
    
    This fixes a number of weird crashes including those AES crashes
    that people have been seeing with the 2.4 backport + ipt_conntrack.
    
    Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: default avatarJames Morris <jmorris@redhat.com>
    Signed-off-by: default avatarDavid S. Miller <davem@redhat.com>
    e8bc549d
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7