OPNSense/core 8af4799 — src/opnsense/mvc/app/controllers/OPNsense/Firewall/forms dialogScheduleRange.xml

This does nothing
DeltaFile
+0-1src/opnsense/mvc/app/controllers/OPNsense/Firewall/forms/dialogScheduleRange.xml
+0-11 files

OPNSense/core b20909a — src/opnsense/mvc/tests/app/models/OPNsense/Base BaseModelTest.php, src/opnsense/mvc/tests/app/models/OPNsense/Base/BaseModel TestModel.xml

tests: add a test case for getNodeCotent()
DeltaFile
+26-0src/opnsense/mvc/tests/app/models/OPNsense/Base/BaseModelTest.php
+12-0src/opnsense/mvc/tests/app/models/OPNsense/Base/BaseModel/TestModel.xml
+38-02 files

OPNSense/src 74b39df — tests/sys/fs/tmpfs Makefile setgid_test.c

tmpfs tests: Add regression tests for setgid handling

Approved by:    so
Security:       FreeBSD-SA-26:94.tmpfs
Sponsored by:   The FreeBSD Foundation
DeltaFile
+221-0tests/sys/fs/tmpfs/setgid_test.c
+3-0tests/sys/fs/tmpfs/Makefile
+224-02 files

OPNSense/src 9d35d0d — . UPDATING, sys/conf newvers.sh

Add UPDATING entries and bump version

Approved by:    so
DeltaFile
+80-0UPDATING
+1-1sys/conf/newvers.sh
+81-12 files

OPNSense/src 4a5d7ed — sys/fs/tmpfs tmpfs_subr.c

tmpfs: Clear setgid on creation by nonmembers

New tmpfs nodes inherit their parent directory group. Clear S_ISGID when
the creator is not a member of that group and lacks PRIV_VFS_SETGID,
matching UFS and tmpfs chmod behavior.

Approved by:    so
Security:       FreeBSD-SA-26:94.tmpfs
Security:       CVE-2026-127749
Reviewed by:    kib
DeltaFile
+8-1sys/fs/tmpfs/tmpfs_subr.c
+8-11 files

OPNSense/src 39b567d — sys/kern vfs_vnops.c, tests/sys/file fcntlflags_test.c

vfs: Check access for O_CREAT directory opens

O_CREAT with O_DIRECTORY takes LOOKUP without creating a vnode.
Clear O_CREAT there so vn_open_vnode checks read or search access.

Add an unprivileged regression test for denied and permitted opens.

Approved by:    so
Security:       FreeBSD-SA-26:92.vfs
Security:       CVE-2026-127746
Reviewed by:    kib
Fixes:          9e18c9eb27cd
DeltaFile
+33-0tests/sys/file/fcntlflags_test.c
+1-0sys/kern/vfs_vnops.c
+34-02 files

OPNSense/src 841a785 — sys/netinet tcp_var.h tcp_input.c, tests/sys/netinet Makefile tcp_oob.c

tcp: Handle read-only mbufs in tcp_pulloutofband()

tcp_pulloutofband() is used to implement the urgent flag: it pulls a
byte out of the data stream, to be returned to the recevier when MSG_OOB
is specified.  That function extracts the byte assuming that the mbuf is
safe to modify, which may not be the case, e.g., when transmitting file
data with sendfile().  This flaw can be exploited by a local user to
obtain root privileges.

Generalize this subroutine so that it handles read-only mbufs as well.

Add some regression tests.

Approved by:    so
Security:       FreeBSD-SA-26:93.tcp
Security:       CVE-2026-127748
Reported by:    OpenAI Security Research Team
Reviewed by:    tuexen
Sponsored by:   The FreeBSD Foundation
Differential Revision:  https://reviews.freebsd.org/D61411
DeltaFile
+303-0tests/sys/netinet/tcp_oob.c
+58-36sys/netinet/tcp_input.c
+0-2sys/netinet/tcp_var.h
+1-0tests/sys/netinet/Makefile
+362-384 files

OPNSense/src 2b959a4 — tests/sys/fs/fdescfs fdescfs_test.c

tests: Add test for fdescfs truncation bug

Add a test case that verifies that it is not possible to truncate a
file opened read-only through fdescfs in default mode, and another that
verifies that it is possible when fdescfs was mounted in nodup mode.

Approved by:    so
Security:       FreeBSD-SA-26:91.fdescfs
Reviewed by:    kib
Differential Revision:  https://reviews.freebsd.org/D61236
DeltaFile
+73-0tests/sys/fs/fdescfs/fdescfs_test.c
+73-01 files

OPNSense/src 5d928ce — sys/fs/fdescfs fdesc_vnops.c

fdescfs: check the target file for FWRITE access when truncating

Truncation is done by calling fdesc_setattr(), and fdesc_setattr() looks
up fd N again, so a concurrent dup2() can swap the file between the
access check and the truncate.

Correct the rights checked for the setattr().
Unlock the fdescfs vnode around fdrop() of the underlying file.

Approved by:    so
Security:       FreeBSD-SA-26:91.fdescfs
Sponsored by:   The FreeBSD Foundation
DeltaFile
+13-5sys/fs/fdescfs/fdesc_vnops.c
+13-51 files

OPNSense/src afc3730 — sys/fs/fdescfs fdesc_vnops.c

fdescfs: add VOP_ACCESS() implementation

kern_truncate() checks VWRITE only through VOP_ACCESS() on the fdescfs
vnode, which always succeeded until now. So a file opened read-only
could be truncated, even if the caller has no write permission for it.

Note that reopen on mounts without nodup already performs the permission
checks in dupfdopen().  For nodup mounts, the VOP_ACCESS() implementation
of the real filesystem is used.

Approved by:    so
Security:       FreeBSD-SA-26:91.fdescfs
Security:       CVE-2026-127745
Reported by:    Kevin Day <kevin at your.org>
Sponsored by:   The FreeBSD Foundation
DeltaFile
+33-1sys/fs/fdescfs/fdesc_vnops.c
+33-11 files

OPNSense/src 177aa25 — contrib/bsnmp/snmpd main.c

bsnmp: let an SNMPv3 discovery message elicit only a Report

An SNMPv3 message with no variable bindings is treated as RFC 3414
engineID (or time-window) discovery: snmp_input_start() appends a
single usmStats counter to the request, and snmp_pdu_auth_access()
skips the VACM check because the AUTODISCOVER flag is set.  The
request's verb was then still dispatched by type.  A genuine discovery
is a GET and simply reads that counter back -- the intended Report --
but a zero-binding GETNEXT or GETBULK instead walks forward from the
appended OID, and with VACM skipped it returns the next registered
object(s): an unauthenticated read of the agent's USM and VACM
configuration (objects at or after 1.3.6.1.6.3.15).

Force the verb of a discovery message to GET, so the appended counter
is read as-is and no walk (or SET) can run under the skipped-VACM
state.  Genuine discovery, which already uses GET, is unaffected.

This complements the earlier change that rejects an AUTODISCOVER
message carrying its own bindings; that guard is never reached on this

    [7 lines not shown]
DeltaFile
+9-0contrib/bsnmp/snmpd/main.c
+9-01 files

OPNSense/src ce06286 — sys/vm vm_map.c vm_fault.c, tests/sys/posixshm posixshm_test.c

vm_map: Fix handling of largepage mappings

vm_map_pmap_enter() is not aware of largepage objects and enters their
constituent 4KB pages into the pmap.  This permits mapping a constituent
page after the corresponding largepage object is freed, which can be
abused to escalate privileges.  Simply don't pass largepage mappings to
it.

Modify vm_fault_copy_entry() to handle largepage mappings for the case
where mprotect() needs to eagerly upgrade protections on a wired
largepage mapping.

Approved by:    so
Security:       FreeBSD-SA-26:90.vm
Security:       CVE-2026-127744
Reviewed by:    alc, kib
Reported by:    OpenAI Security Research Team
Reported by:    Albert at Vexera AI
Sponsored by:   The FreeBSD Foundation
Differential Revision:  https://reviews.freebsd.org/D61363
DeltaFile
+63-0tests/sys/posixshm/posixshm_test.c
+27-7sys/vm/vm_fault.c
+4-2sys/vm/vm_map.c
+94-93 files

OPNSense/src d1efa48 — contrib/bsnmp/lib snmp.c

bsnmp: mask reserved SNMPv3 msgFlags bits on input

snmp_pdu_decode_header() reads the msgFlags octet straight into
pdu->flags and never sanitises it.  Only bits 0..2 are defined on the
wire (authFlag, privFlag, reportableFlag).  Bit 7 (0x80) is bsnmp's
internal SNMP_MSG_AUTODISCOVER marker: it shares the same field and is
tested later as "this is discovery, skip USM and VACM".

Because the byte is taken verbatim from an unauthenticated peer, a
client that sets bit 7 of msgFlags has (pdu->flags &
SNMP_MSG_AUTODISCOVER) read true straight after header decode, forging
the discovery state.  A noAuthNoPriv user -- which has no digest to
verify -- can thus mark an ordinary request as discovery and have it
bypass the VACM access check, operating outside its configured views.

Keep only the three defined wire bits when decoding msgFlags, so the
internal marker can never be set from the network.

Approved by:    so

    [3 lines not shown]
DeltaFile
+7-0contrib/bsnmp/lib/snmp.c
+7-01 files

OPNSense/src 6dec616 — contrib/bsnmp/snmp_vacm vacm_snmp.c

bsnmp: reject an oversized vacmViewTreeFamilyMask

The SET handler for vacmViewTreeFamilyMask compared the value length
against the 16-byte view->mask, but the check had no statement of its
own: it guarded the following malloc() instead of rejecting the
request.  A value longer than 16 bytes was therefore copied into
view->mask with memcpy(), overflowing struct vacm_view.  Add the
missing return so an over-long value is refused with wrongValue.

Approved by:    so
Security:       FreeBSD-SA-26:89.bsnmp
Security:       CVE-2026-127743
Reviewed by:    harti
Fixes:          135f7de5ddb6
DeltaFile
+1-0contrib/bsnmp/snmp_vacm/vacm_snmp.c
+1-01 files

OPNSense/src 2316606 — contrib/bsnmp/snmpd main.c

bsnmp: do not act on an SNMPv3 discovery message that carries bindings

An SNMPv3 message with an empty engine id and empty user name is handled
as snmpEngineID discovery: snmp_pdu_auth_user() sets SNMP_MSG_AUTODISCOVER
and returns without a USM user, and snmp_pdu_auth_access() then grants the
message access.  A genuine discovery request carries no variable bindings
and only elicits a Report, but a discovery PDU that did carry bindings was
executed anyway -- so a GET or SET ran with no authentication and without
the VACM access check.

This affects two cases.  With an empty user name the message is wholly
unauthenticated, so anyone able to reach the agent could issue a SET.  It
also affects a configured noAuthNoPriv user: such a user has no digest to
verify, so it too can set the AUTODISCOVER flag (an authenticated request
before time synchronisation) and have a bindings-carrying PDU bypass VACM
and operate outside its views.

Refuse any AUTODISCOVER message that arrives with variable bindings
instead of acting on it.  Empty-binding discovery, the authenticated

    [23 lines not shown]
DeltaFile
+16-1contrib/bsnmp/snmpd/main.c
+16-11 files

OPNSense/src 1a63d2c — sys/dev/sound/pcm buffer.c channel.c

sound: Improve interlocking in chn_resizebuf()

chn_resizebuf() fails if the channel's software buffer is mapped, but
does not take into account the fact that channel I/O drops the channel
lock when copying from or to user memory.  During the window where the
lock is dropped, a resize may free the old buffer, causing userspace to
access freed kernel memory.  This can be exploited to escalate
privileges.

Fix this by disallowing resizing when I/O is in progress.

Approved by:    so
Security:       FreeBSD-SA-26:88.sound
Security:       CVE-2026-127741
Reviewed by:    christos, kib
Reported by:    OpenAI Security Research Team
Sponsored by:   The FreeBSD Foundation
Differential Revision:  https://reviews.freebsd.org/D61446
DeltaFile
+11-5sys/dev/sound/pcm/channel.c
+1-0sys/dev/sound/pcm/buffer.c
+12-52 files

OPNSense/src 4d43651 — sys/kern uipc_socket.c

so_splice: Serialize teardowns of splices

A socket splice can be configured with a timeout; once the timeout
expires, the splice is automatically undone.  The implementation of an
unsplice operation detaches each socket from the splice structure, and
then drains the timeout task.  The timeout task takes the splice
structure as an argument, and passes the source socket to so_unsplice().

It is possible for two threads to race with the task thread: one removes
the source socket from the splice associated with currently running
task, and the other thread splices that socket again, creating a new
splice structure.  The timeout thread may then unsplice the source
socket even though it doesn't own that socket's current splice.  The
resulting use-after-free can be exploited by a local user to escalate
privileges.

Fix the problem by serializing teardowns of splices: make so_unsplice()
callers specify the cause of the teardown, and ensure that threads can't
race to destroy a splice after an error occurs.

    [8 lines not shown]
DeltaFile
+56-30sys/kern/uipc_socket.c
+56-301 files

OPNSense/src 9e33702 — sys/kern uipc_socket.c

socket: remove tautological condition in so_unsplice()

so2rele was introduced in 1000cc4a0d3 and it was necessary there, but
the cleanup in a837d1fe49e0255 rendered it redundant if our own KASSERT
is to be believed: we've asserted that `so2->so_splice_back == sp` and
`sp` has been dereferenced above, so there's no condition left where
we shouldn't release the socket reference at the end.  Indeed, the
change in so_splice() to NULL out sp->dst removes that possible state of
a partially constructed splice: if sp->dst is set, it has been ref'd.

Approved by:    so
Security:       FreeBSD-SA-26:87.socket
Reviewed by:    gallatin, markj

(cherry picked from commit 8a3d28375450946e4b0de239c9239df54c22d298)
(cherry picked from commit 2b25a0ebb48dc2340e1e15d1a05b89d7df036b38)
DeltaFile
+2-4sys/kern/uipc_socket.c
+2-41 files

OPNSense/src 3b2b496 — sys/kern kern_event.c

kqueue: Fix a race between kqueue_fork_copy_list() and kqueue_expand()

While kqueue_fork_copy_list() is iterating over the knote lists, the
backing array may change while the kqueue lock is dropped.  Since each
list is a singly-linked list, kqueue_fork_copy_list() must start
iterating from the list head in order to remove the marker, but that
list head pointer is invalid after kqueue_expand() runs.

Add a bit of indirection to re-compute the correct list head each time
the kqueue lock is dropped.

Avoid changing the layout of struct knote since I want to backport this
to releng branches.

Approved by:    so
Security:       FreeBSD-SA-26:85.kqueue
Security:       CVE-2026-127750
Reported by:    Dennys Kaluzny Pereira <dennyskaluzny at gmail.com>
Reviewed by:    kib
Differential Revision:  https://reviews.freebsd.org/D61608
DeltaFile
+17-7sys/kern/kern_event.c
+17-71 files

OPNSense/src cbab0a8 — sys/compat/freebsd32 freebsd32_misc.c

freebsd32: Avoid modifying a shared control message

freebsd32_copy_msg_out() copies out received control messages.  The
cmsg ABI differs between the 32-bit and native ABIs in that the 32-bit
ABI requires only 4-byte alignment for message bodies, see CMSG_ALIGN.

When the control message is read from the socket buffer with MSG_PEEK,
short messages which fit into an mbuf are copied into private storage,
but larger messages are returned by acquiring a counted reference on the
underlying mbuf cluster still attached to the socket buffer.

When the underlying storage is shared, the non-atomic, temporary
modification of the control message header in freebsd32_copy_msg_out()
can be abused to corrupt the message queue; this can be leveraged to
escalate privileges.

Approved by:    so
Security:       FreeBSD-SA-26:86.freebsd32
Security:       CVE-2026-101321

    [4 lines not shown]
DeltaFile
+10-9sys/compat/freebsd32/freebsd32_misc.c
+10-91 files

OPNSense/src 49b349d — sys/kern kern_event.c

kqueue: Fix a race when detaching a timer knote

We currently maintain a per-process list of stopped timer knotes, used
when the owning process receives SIGSTOP.  Upon receiving SIGCONT,
queued timers are re-armed.

When detaching a timer knote, we drain the callout and remove it from
the queue, then check to see if the callout was re-armed by SIGCONT; if
so, then we loop.  However, the callout timer may fire before this
check, and softclock_call_cc() clears the pending bit without the
associated callout lock held, in which case filt_timerdetach() fails to
observe that the callout is still running and doesn't drain.

The callout handler then races with a free of the knote, and the
resulting memory corruption can be exploited to obtain root privileges.

Fix the problem by using an explicit flag that prevents re-arming a
timer whose knote is in the process of being detached.


    [8 lines not shown]
DeltaFile
+14-19sys/kern/kern_event.c
+14-191 files

OPNSense/src c76e608 — sys/kern uipc_usrreq.c

unix: Fix a race between shutdown and listen

In uipc_shutdown(), the SOLISTENING() check is stale as soon as the
socket lock is dropped.  Acquire the unpcb lock earlier and use that to
interlock with other work that touches the socket buffers which are
invalid for a listening socket.  Fix unp_dispose() to handle errors when
acquiring the I/O lock; contrary to the assertions, such races are
possible.

Approved by:    so
Security:       FreeBSD-SA-26:83.unix
Security:       CVE-2026-127751
Reported by:    OpenAI Security Research Team
Sponsored by:   The FreeBSD Foundation
DeltaFile
+23-24sys/kern/uipc_usrreq.c
+23-241 files

OPNSense/src d4b407b — sys/netipsec xform_esp.c, tests/sys/netipsec/tunnel Makefile esp_iv.sh

esp: Fix synchronization of stream cipher counter updates

After commit 0361f165f219, the counter embedded in the IV for AES-CTR,
AES-GCM and ChaCha20 transforms is incremented under a shared lock,
which creates the potential for nonce reuse.  This can be abused by an
on-path attacker to alter the ciphertext of intercepted packets, and
potentially reveal the plaintext of packets whose counter values
collide.

Approved by:    so
Security:       FreeBSD-SA-26:82.ipsec
Security:       CVE-2026-101318
Sponsored by:   Rubicon Communications, LLC ("Netgate")
Fixes:          0361f165f219 ("ipsec: replace SECASVAR mtx by rmlock")
DeltaFile
+91-0tests/sys/netipsec/tunnel/esp_iv.sh
+5-1sys/netipsec/xform_esp.c
+2-1tests/sys/netipsec/tunnel/Makefile
+98-23 files

OPNSense/src 42eabbd — sys/amd64/vmm/intel vmx_msr.c

amd64/vmm: Reject TSC_AUX writes with reserved bits set

On Intel CPUs, bits 63:32 of IA32_TSC_AUX are reserved.  Guest writes to
the MSR are trapped and the value is stored in the vCPU's MSR array.
vmx_msr_guest_enter_tsc_aux() later writes the value to the physical MSR,
so reserved bits must be rejected before the value reaches the host MSR.

Inject #GP into the guest instead, as the hardware would.

Approved by:    so
Security:       FreeBSD-SA-26:84.vmm
Security:       CVE-2026-101319
Fixes:          f5f5f1e7d6de ("Support guest rdtscp and rdpid instructions on Intel VT-x")
Sponsored by:   Alchemilla Ventures Private Limited
DeltaFile
+5-1sys/amd64/vmm/intel/vmx_msr.c
+5-11 files

OPNSense/src 449d029 — sys/kern vfs_lookup.c

rbeneath lookup: move the boundary on union mount fallthrough

A name not found in the root of a union (MNT_UNION) mount is looked up
in the covered directory.  If the union root is the starting directory
of a strict relative lookup and the name is a relative symlink in the
covered directory, namei() resolves the symlink target from ni_dvp, the
covered vnode, without crossing back into the union root.  A ".." in
the target is then checked against ni_rbeneath_dpp, the union root,
which does not match, and the lookup leaves the starting directory.

Before 2f60984053 the fallthrough added the covered vnode to the
visited vnodes, and the parent of the covered directory, never
visited, was refused.

When the fallthrough happens at ni_rbeneath_dpp, move ni_rbeneath_dpp
to the covered vnode.  ".." from the union root steps over
mnt_vnodecovered in the vfs_lookup() dotdot loop and meets the moved
boundary there, so both directories stay protected.  The mount holds a
reference on the covered vnode, and the doomed check fails the lookup

    [6 lines not shown]
DeltaFile
+31-6sys/kern/vfs_lookup.c
+31-61 files

OPNSense/src 12d7e3f — tests/sys/vfs lookup_cap_dotdot.c

lookup_cap_dotdot test: check dotdot VV_ROOT escape

Approved by:    so
Security:       FreeBSD-SA-26:81.vfs
DeltaFile
+71-0tests/sys/vfs/lookup_cap_dotdot.c
+71-01 files

OPNSense/src dd817e0 — tests/sys/vfs lookup_cap_dotdot.c

lookup_cap_dotdot test: check symlink escape below a union mount root

Let mount_tmpfs() add the union option, and leave creating the mount
point to the callers, so that the covered directory can be populated
before the mount.

Approved by:    so
Security:       FreeBSD-SA-26:81.vfs
Sponsored by:   The FreeBSD Foundation
DeltaFile
+74-10tests/sys/vfs/lookup_cap_dotdot.c
+74-101 files

OPNSense/src ad4ebde — sys/kern vfs_lookup.c

lookup: hold ni_rbeneath_dpp

The vnode is held to ensure the validity of the pointer.

Approved by:    so
Security:       FreeBSD-SA-26:81.vfs
Reported by:    pjd
Sponsored by:   The FreeBSD Foundation
DeltaFile
+7-1sys/kern/vfs_lookup.c
+7-11 files

OPNSense/src 40047ca — sys/kern vfs_lookup.c

rbeneath lookup: do not allow to step up with dotdot lookup over VV_ROOT

In vfs_lookup(), the ".." loop steps from a mount root to
its mnt_vnodecovered vnode before the name is looked up.
nameicap_check_dotdot() runs only after VOP_LOOKUP() and compares the
directory being left, ni_dvp, with ni_rbeneath_dpp, the start. After
the mount crossing ni_dvp is the covered vnode, not the start, so the
comparison never matches and ".." is allowed. [*]

Before 2f60984053 the loop called nameicap_check_dotdot(ndp, dp) right
after the mnt_vnodecovered step, and the covered vnode, which was not
among the vnodes the lookup had visited, was refused. The change replaced
the visited-vnode tracking with the comparison against ni_rbeneath_dpp,
and removed that call.

A process restricted to a directory descriptor by Capsicum (capability
mode, or a descriptor limited with cap_rights_limit()), or a program that
relies on O_RESOLVE_BENEATH / AT_RESOLVE_BENEATH to keep a lookup beneath
a directory, is not contained when that directory is a mount root (for

    [17 lines not shown]
DeltaFile
+13-1sys/kern/vfs_lookup.c
+13-11 files

OPNSense/src e766284 — sys/fs/nfsserver nfs_nfsdstate.c

nfsd: Make nfsrv_getstate() validate the stateid type

Otherwise nfsrv_delegupdate() can be tricked by a client into freeing a
state when it shouldn't, resulting in a use-after-free.

Approved by:    so
Security:       FreeBSD-SA-26:79.nfs
Security:       CVE-2026-101317
Reported by:    H. P. Cook <barry at unseen.sh>
DeltaFile
+5-6sys/fs/nfsserver/nfs_nfsdstate.c
+5-61 files