Is FreeBSD-SA-26:14.pf (CVE-2026-7164, SCTP panic) fixed in pfSense CE 2.9.0?
-
Hi,
I'm running pfSense CE 2.9.0-RELEASE (amd64), and pfSense-upgrade -c reports the system is up to date. Kernel build string from uname -a:
FreeBSD 16.0-CURRENT #12 RELENG_2_9_0-n256132-d8e3138ecf52: Mon Aug 17 18:50:13 UTC 2026
FreeBSD-SA-26:14.pf (CVE-2026-7164, published 2026-04-29) describes a remote kernel panic caused by crafted SCTP packets. It affects any system where pf processes traffic, "independent of the configured ruleset", and the advisory says no workaround is available.
In FreeBSD main I can see commit 6f9ddb329b07 ("pf: improve SCTP validation", 2026-04-29). The advisory lists e1c9f92130e8 as the stable/15 fix.
I couldn't confirm whether this fix is in the 2.9.0 kernel:
- The 2.9.0 release notes don't mention SA-26:14 or SCTP.
- The public pfsense/FreeBSD-src mirror on GitHub hasn't been updated since March 2026, so I can't check the RELENG_2_9_0 branch myself.
Could someone from Netgate confirm whether CE 2.9.0 includes the fix? If it doesn't, is a patch or 2.9.x release planned?
Thanks!
-
CVE-2026-7164
where does that list freebsd 16?
looks 15 and below to me.
Announced: 2026-04-29 Credits: Igor Gabriel Sousa e Souza Affects: All supported versions of FreeBSD. Corrected: 2026-04-29 14:47:50 UTC (stable/15, 15.0-STABLE) 2026-04-29 14:48:30 UTC (releng/15.0, 15.0-RELEASE-p7) 2026-04-29 14:48:52 UTC (stable/14, 14.4-STABLE) 2026-04-29 14:49:44 UTC (releng/14.4, 14.4-RELEASE-p3) 2026-04-29 14:49:20 UTC (releng/14.3, 14.3-RELEASE-p12) 2026-04-29 14:50:08 UTC (stable/13, 13.5-STABLE) 2026-04-29 14:50:20 UTC (releng/13.5, 13.5-RELEASE-p13) -
@johnpoz Thanks for looking! The advisory only lists release/stable branches. FreeBSD advisories never list main (CURRENT), which is what 16.0-CURRENT and pfSense 2.9.0 are built from.
The same fix landed in main first, with the same Security tags:
main: 6f9ddb329b07 "pf: improve SCTP validation" (2026-04-29 14:39 UTC)
stable/15: e1c9f92130e8 (2026-04-29 14:40 UTC)Both commit messages carry "Security: FreeBSD-SA-26:14.pf" and "Security: CVE-2026-7164".
https://cgit.freebsd.org/src/commit/?id=6f9ddb329b07So main was affected. The open question is whether pfSense's RELENG_2_9_0 branch (my kernel: RELENG_2_9_0-n256132-d8e3138ecf52, built Aug 17 2026) includes 6f9ddb329b07, either because it branched after Apr 29 or as a cherry-pick. The public pfsense/FreeBSD-src mirror hasn't been updated since March, so I can't check it myself. Could someone from Netgate confirm?
-
@Gorbyz since they released fixes back in april, I can't believe something that was built with an aug date wouldn't have said fix.
-
Shh! We're trying to trick anyone from Netgate into making a statement that might offer a clue about when the Github codebase will be updated!
-
@tinfoilmatt FWIW, yes in 26.10
-
@SteveITS Thought I'd follow up on this since it was bugging me. Rather than go by the build date, I spun up a throwaway 2.9.0-RELEASE VM and actually went digging in the kernel to settle it for myself.
The fix is in. On my build (RELENG_2_9_0-n256132-d8e3138ecf52, Aug 17) pf_multihome_scan in pf.c has the extra asconf argument from the FreeBSD commit (6f9ddb329b07, the RFC5061 "add/delete IP params only belong in ASCONF" change that also kills the unbounded recursion). Both the add and delete parameter branches bail out with a DROP when the ASCONF flag is set, exactly like upstream. So CVE-2026-7164 / SA-26:14 is handled in CE 2.9.0, not just in 26.10.
So @SteveITS' "yes" holds for CE too. Figured I'd post it in case anyone else runs into the same question and wants something more concrete than the build timestamp. Cheers.
-
@Gorbyz so you thought freebsd would put out info on this cve and state which builds were fix, but forget to put in a build done months after they announce fixes?
-
@johnpoz Fair enough, it was always the most likely answer. I just couldn't verify it from public sources, since the GitHub mirror stops in March and a build date doesn't show when the branch was cut. At least there's something concrete in the thread now for the next person who searches for it. Thanks for the help!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register LoginPrivacy Policy · Cookie Policy