Read the docs

Out-of-bounds kernel memory read in DragonFly BSD ARP handling

Priority LOW 31CWE-130Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

DragonFly BSD through 6.4.2 before 4bb22ff is affected. The ARP input handlers skip checks on the hardware and protocol address length fields, and the reply code then copies kernel memory past its buffers (CWE-130). An unauthenticated attacker on the adjacent network can send one crafted ARP request to read up to roughly 250 bytes of kernel memory, including kernel pointers, returned in the ARP reply.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

In DragonFly BSD through 6.4.2 before 4bb22ff, the ARP input handlers arpintr() and in_arpinput() (sys/netinet/if_ether.c) do not validate the hardware address length (ar_hln) and protocol address length (ar_pln) fields of incoming ARP packets. in_arpreply() then uses these attacker-controlled values as memcpy lengths when copying from kernel buffers that are only 6 and 4 bytes long, resulting in an out-of-bounds read of kernel heap and stack memory that is copied into the ARP reply sent back to the requester. An unauthenticated attacker on the adjacent network can use a single crafted ARP request to disclose up to roughly 250 bytes of each type of kernel memory, including kernel pointers. This is expected to be fixed in the 6.6 stable release when that is available.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00398 34th percentileScored 2026-11-07
Fix Fixed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

No affected products listed by the sources yet.

Remediation

The sources list no fixed version for DragonFly BSD. The source says a fix is expected in the 6.6 stable release when that is available.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Timeline

  1. 2026-10-15 Threatist record created from CVE-2026-110912
  2. 2026-10-15 CISA SSVC decision points changed
  3. 2026-10-15 Priority changed: MEDIUM → LOW
  4. 2026-10-16 Alias added: GHSA-r2jj-8gwv-75pj
  5. 2026-10-16 1 new reference · CNA

References

  • TI-2008-04392 The TCP implementation in (1) Linux, (2) platforms based on BSD Unix, (3) Microsoft… CVSS 2.0HIGH 7.1
  • TI-2005-00657 The sendfile system call in FreeBSD 4.8 through 4.11 and 5 through 5.4 can transfer… CVSS 2.0HIGH 10.0
  • TI-2006-05781 Integer signedness error in the fw_ioctl (FW_IOCTL) function in the FireWire (IEEE-1394)… CVSS 2.0LOW 2.1

Sources