03 Aug, 2018

1 commit

  • The squashfs fragment reading code doesn't actually verify that the
    fragment is inside the fragment table. The end result _is_ verified to
    be inside the image when actually reading the fragment data, but before
    that is done, we may end up taking a page fault because the fragment
    table itself might not even exist.

    Another report from Anatoly and his endless squashfs image fuzzing.

    Reported-by: Анатолий Тросиненко
    Acked-by:: Phillip Lougher ,
    Cc: Willy Tarreau
    Signed-off-by: Linus Torvalds

    Linus Torvalds
     

30 Jul, 2018

1 commit

  • Anatoly Trosinenko reports that a corrupted squashfs image can cause a
    kernel oops. It turns out that squashfs can end up being confused about
    negative fragment lengths.

    The regular squashfs_read_data() does check for negative lengths, but
    squashfs_read_metadata() did not, and the fragment size code just
    blindly trusted the on-disk value. Fix both the fragment parsing and
    the metadata reading code.

    Reported-by: Anatoly Trosinenko
    Cc: Al Viro
    Cc: Phillip Lougher
    Cc: stable@kernel.org
    Signed-off-by: Linus Torvalds

    Linus Torvalds
     

29 May, 2011

1 commit


26 May, 2011

3 commits


14 Jan, 2011

1 commit


21 Jan, 2010

1 commit


05 Jan, 2009

1 commit