freebsd test error: panic: ASan: Invalid access, NUM-byte write at ADDR, GenericRedZone(fa)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 50982d26e45b net80211: add MMIC element ID (for management..
git tree: freebsd-src
console output: https://syzkaller.appspot.com/x/log.txt?x=13d88900580000
dashboard link: https://syzkaller.appspot.com/bug?extid=c5e279db5763b58e8d69

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c5e279...@syzkaller.appspotmail.com

panic: ASan: Invalid access, 8-byte write at 0xffffffff84c18980, GenericRedZone(fa)
cpuid = 0
time = 1
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0xc6/frame 0xffffffff84c18470
kdb_backtrace() at kdb_backtrace+0xd0/frame 0xffffffff84c185d0
vpanic() at vpanic+0x280/frame 0xffffffff84c18790
panic() at panic+0xb5/frame 0xffffffff84c18860
kasan_report() at kasan_report+0xdf/frame 0xffffffff84c18930
pctrie_remove_lookup() at pctrie_remove_lookup+0xf8/frame 0xffffffff84c189f0
pmap_demote_pde_locked() at pmap_demote_pde_locked+0x323/frame 0xffffffff84c18bf0
pmap_change_props_locked() at pmap_change_props_locked+0x896/frame 0xffffffff84c18d90
pmap_init() at pmap_init+0xddd/frame 0xffffffff84c18eb0
vm_mem_init() at vm_mem_init+0xa8/frame 0xffffffff84c18ed0
mi_startup() at mi_startup+0x2c9/frame 0xffffffff84c18ff0
KDB: enter: panic
[ thread pid 0 tid 0 ]
Stopped at kdb_enter+0x6e: movq $0,0x23e2e77(%rip)
db> serialport: Connected to syzkaller.us-central1-b.ci-freebsd-main-test-0 port 1 (session ID: b6f7b38458fa5b90981a85c544f21c49596b3c5b4ea8c357a83dbb177b454bfd, active connections: 1).


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup