Contributed by jose on from the fix0rific dept.
First, this only affects you if you applied the refrag.diff to an OpenBSD 3.1-stable system. The bridge refragmentation code that was added in OpenBSD 3.1-current introduced two new bugs which can lead to the following kind of kernel panics: panic: m_copym0: m == 0 and not COPYALL panic: m_copydata: null muf These occur only on pf bridges when scrub is enabled. While the bugs obviously affect stability, it's uncertain whether they can be exploited. The relevant code (which was itself a bugfix) was not commited to the 3.1 stable branch (due to its size), but a patch against 3.1-stable (refrag.diff) was provided and recommended to solve the initial bridge problem. The bugs are now fixed in 3.2-current, but if you're running 3.1-stable with the refrag.diff patch applied, you should revert to 3.1-stable and apply the updated patch.The full message and the link to the patch is available in this message on the PF mailing list.
If you're out of sync with patches and are running this code branch, this may be the source of some instabilities in your firewall.
(Comments are closed)