{
  "id": "CVE-2026-101307",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-101307",
  "published_at": "2026-10-15T07:05:02.295Z",
  "title": "Remotely triggerable buffer overflow in tcp_rack",
  "vendor": "FreeBSD",
  "product": "FreeBSD",
  "cvss": {
    "score": 9.1,
    "source": "nvd",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "When the PCM sample array needs to grow, the RACK stack doubles a 16-bit allocation counter.  Repeated doublings caused the counter to wrap to zero, resulting in a near-zero-length allocation followed by a copy of the existing samples into the undersized buffer.  A remote peer can trigger the expansion by sending a sufficient number of ACKs on an established connection.\n\nA remote attacker who can establish a TCP connection to a system using the RACK stack can trigger an out-of-bounds write of approximately 512 KB in the kernel heap possibly resulting in a kernel panic.",
  "cwe": "CWE-122",
  "cpes": [
    "cpe:2.3:o:freebsd:freebsd:15.1:-:*:*:*:*:*:*",
    "cpe:2.3:o:freebsd:freebsd:15.1:p1:*:*:*:*:*:*",
    "cpe:2.3:o:freebsd:freebsd:15.1:p2:*:*:*:*:*:*",
    "cpe:2.3:o:freebsd:freebsd:15.1:p3:*:*:*:*:*:*",
    "cpe:2.3:o:freebsd:freebsd:15.1:p4:*:*:*:*:*:*"
  ],
  "cvss_by_source": {
    "cisa-adp": 8.2,
    "nvd": 9.1
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "FreeBSD",
        "product": "FreeBSD",
        "ranges": [
          "\u003e= 15.1-RELEASE, \u003c p5"
        ],
        "fixed_in": [
          "p5"
        ]
      }
    ],
    "upgrade": [
      "Upgrade FreeBSD to p5 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://security.freebsd.org/advisories/FreeBSD-SA-26:70.tcp.asc"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
