| commit | 44a33fd5e9dbc7d3a789ac9ec912b7a873adaab0 | |
| author | Thomas Schmitt <scdbackup@gmx.net> | |
| Wed, 3 Apr 2013 03:42:08 +0000 (2 20:42 -0700) | ||
| committer | H. Peter Anvin <hpa@zytor.com> | |
| Wed, 3 Apr 2013 03:42:08 +0000 (2 20:42 -0700) | ||
| tree | c78710b3a02097d62488b60a873f6237a1fd956e | treesnapshot (tar.gz zip) |
| parent | 556ccf02efe3eae833bcc82c4764179580ba6361 | commitdiff |
iso9660: Avoid arbitrarily large malloc()s
After explaining the slightly wasteful usage of malloc()/memcpy()
with multi-block CE entries, i noticed that i did not install a
safety cap on the malloc size.
I could not challenge this in practice but only by gdb manipulation.
My most CE-happy test image has 3 occasions of multi-block CE.
All three only span over 2 blocks each.
After explaining the slightly wasteful usage of malloc()/memcpy()
with multi-block CE entries, i noticed that i did not install a
safety cap on the malloc size.
I could not challenge this in practice but only by gdb manipulation.
My most CE-happy test image has 3 occasions of multi-block CE.
All three only span over 2 blocks each.
| core/fs/iso9660/susp_rr.c | diffblobblamehistory |