[Bug 255069] net.link.ether.ipfw=1 leads to kernel panic under 13.0-RELEASE amd64

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 19 Jun 2021 14:09:33 +0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255069

--- Comment #7 from commit-hook_at_FreeBSD.org ---
A commit in branch stable/13 references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=ed1acef3fe3053b418ce3e41036ccf24957253a4

commit ed1acef3fe3053b418ce3e41036ccf24957253a4
Author:     Mark Johnston <markj_at_FreeBSD.org>
AuthorDate: 2021-06-16 13:46:56 +0000
Commit:     Mark Johnston <markj_at_FreeBSD.org>
CommitDate: 2021-06-19 14:08:49 +0000

    ipfw: Update the pfil mbuf pointer in ipfw_check_frame()

    ipfw_chk() might call m_pullup() and thus can change the mbuf chain
    head.  In this case, the new chain head has to be returned to the pfil
    hook caller, otherwise the pfil hook caller is left with a dangling
    pointer.

    Note that this affects only the link-layer hooks installed when the
    net.link.ether.ipfw sysctl is set to 1.

    PR:             256439, 254015, 255069, 255104
    Fixes:          f355cb3e6
    Reviewed by:    ae
    Sponsored by:   The FreeBSD Foundation

    (cherry picked from commit bc6a2267fffeafd3946637607a74cfd639398f9d)

 sys/netpfil/ipfw/ip_fw_pfil.c | 2 ++
 1 file changed, 2 insertions(+)

-- 
You are receiving this mail because:
You are the assignee for the bug.
Received on Sat Jun 19 2021 - 14:09:33 UTC

Original text of this message