---
- branch: MAIN
  date: Wed Apr 22 19:32:11 UTC 2020
  files:
  - new: '1.178'
    old: '1.177'
    path: src/sys/netinet6/nd6_nbr.c
    pathrev: src/sys/netinet6/nd6_nbr.c@1.178
    type: modified
  id: 20200422T193211Z.867a7f561e7d59a169898922abe9a029a40af060
  log: |
    inet6: nd6_na_input() now considers ln_state <= ND6_LLINFO_INCOMPLETE

    Otherwise if ln_state != ND6_LLINFO_INCOMPLETE and the is no lladdr
    and this message was solicited then ln_state is set to ND6_LLINFO_REACHABLE
    which could then cause a panic in nd6_resolve().
    If ln_state > ND6_LLINFO_INCOMPLETE then it's assumed we have a lladdr.

    Potentially this could have been triggered by the introduction of
    ND6_LLINFO_PURGE in nd6.c r1.143 but also by the re-introduction of
    ND6_LLINFO_INCOMPLETE in nd6.c r1.263.
    Depending on the timing, it's technically possible to receive such
    a message after the llentry is created with ND6_LLINFO_NOSTATE.
  module: src
  subject: 'CVS commit: src/sys/netinet6'
  unixtime: '1587583931'
  user: roy