Discussion
Loading...

Post

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Harry Sintonen
Harry Sintonen
@harrysintonen@infosec.exchange  ·  activity timestamp 6 months ago

Recently I found a 35 year old bug from #AmigaOS - in certain situations it releases a FileLock that is still in use, resulting in use after free condition. The effects range from "nothing" to complete system lockup, depending on your luck. I believe this bug was introduced in Kickstart 2.0 (36.x), released in 1990.

#amiga #retrocomputing

Screenshot of AmigaOS test application displaying wildly random struct FileLock fields due to the memory being released prematurely and reused for something else.
Screenshot of AmigaOS test application displaying wildly random struct FileLock fields due to the memory being released prematurely and reused for something else.
Screenshot of AmigaOS test application displaying wildly random struct FileLock fields due to the memory being released prematurely and reused for something else.
  • Copy link
  • Flag this post
  • Block

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.1 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Members
  • Code of Conduct