<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>FreeBSD — recent CVEs</title>
    <link>https://vulnogram.org/</link>
    <atom:link href="https://vulnogram.org/rss/freebsd" rel="self" type="application/rss+xml"/>
    <description>Most recent CVEs assigned by FreeBSD (freebsd).</description>
    <image>
      <url>https://vulnogram.org/seaview/icons/freebsd.png</url>
      <title>FreeBSD — recent CVEs</title>
      <link>https://vulnogram.org/</link>
    </image>
    <lastBuildDate>Wed, 21 Oct 2026 07:00:07 GMT</lastBuildDate>
    <item>
      <title>CVE-2026-101311 · 7 HIGH — Multiple vulnerabilities in bhyve device models</title>
      <link>https://vulnogram.org/CVE-2026-101311</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-101311</guid>
      <description>The framebuffer device model&apos;s maximum resolution constants were duplicated between the framebuffer and RFB modules and had gotten out of sync. Additionally, writes to the framebuffer BAR could set arbitrary width and height values without validation…</description>
      <category>High</category>
      <pubDate>Thu, 15 Oct 2026 07:18:18 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-101310 · 7 HIGH — Multiple vulnerabilities in bhyve device models</title>
      <link>https://vulnogram.org/CVE-2026-101310</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-101310</guid>
      <description>The HDA audio device model did not check for zero-length Buffer Descriptor List (BDL) entries when starting a stream. A zero-length entry caused an out-of-bounds read or write during DMA transfer processing. BDL fields were also subject to modificati…</description>
      <category>High</category>
      <pubDate>Thu, 15 Oct 2026 07:18:11 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-101309 · 7 HIGH — Multiple vulnerabilities in bhyve device models</title>
      <link>https://vulnogram.org/CVE-2026-101309</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-101309</guid>
      <description>The xHCI (USB 3) device model did not validate or save the event ring size provided by the guest. The size was re-read from guest memory on each use, and Transfer Request Block (TRB) fields were loaded without protection against concurrent modificati…</description>
      <category>High</category>
      <pubDate>Thu, 15 Oct 2026 07:17:50 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-101308 · 5.5 MEDIUM — TOCTOU race between sound(4) buffer resizing and mmap</title>
      <link>https://vulnogram.org/CVE-2026-101308</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-101308</guid>
      <description>When an audio channel&apos;s buffer needs to be resized, the sound(4) driver checks that the buffer is not memory-mapped and then drops the channel lock to allocate a new buffer. An mmap(2) call on another thread can complete during this window, after whi…</description>
      <category>Medium</category>
      <pubDate>Thu, 15 Oct 2026 07:08:52 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-101307 · 8.2 HIGH 🌩️ — Remotely triggerable buffer overflow in tcp_rack</title>
      <link>https://vulnogram.org/CVE-2026-101307</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-101307</guid>
      <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 undersi…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 15 Oct 2026 07:05:02 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-101303 · 7.5 HIGH 🌩️ — IPv6 UDP sendto(2) bypasses jail loopback restriction</title>
      <link>https://vulnogram.org/CVE-2026-101303</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-101303</guid>
      <description>The IPv6 UDP send path for unconnected sockets did not apply the jail policy of rewriting a loopback destination address to the jail&apos;s primary IPv6 address. A process in a classic (non-VNET) jail can send UDP datagrams to services listening on the ho…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 15 Oct 2026 06:58:55 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-101302 · 6.5 MEDIUM — Remote DoS via receive-side kernel TLS</title>
      <link>https://vulnogram.org/CVE-2026-101302</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-101302</guid>
      <description>TLS 1.3 embeds the actual record type as the last non-zero byte of the decrypted payload, optionally followed by zero padding. The code which searches for the inner record type had an off-by-one bug which could be triggered by an invalid frame, leadi…</description>
      <category>Medium</category>
      <pubDate>Thu, 15 Oct 2026 06:53:12 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-101306 · 9.8 CRITICAL 🌩️ — Multiple jail filesystem root escapes</title>
      <link>https://vulnogram.org/CVE-2026-101306</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-101306</guid>
      <description>SCM_RIGHTS file descriptor passing did not preserve FD_RESOLVE_BENEATH when a descriptor was transferred. A process could clear the restriction by sending the descriptor to itself over a Unix domain socket. A process in a jail that has received a dir…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 15 Oct 2026 06:46:25 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-101305 · 8.8 HIGH — Multiple jail filesystem root escapes</title>
      <link>https://vulnogram.org/CVE-2026-101305</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-101305</guid>
      <description>renameat(2) did not enforce FD_RESOLVE_BENEATH on its directory arguments. A jailed process could rename a directory relative to a restricted descriptor, then escape the jail root via fchdir(2). This requires the directory to reside on a filesystem t…</description>
      <category>High</category>
      <pubDate>Thu, 15 Oct 2026 06:46:16 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-101304 · 7.1 HIGH — Multiple jail filesystem root escapes</title>
      <link>https://vulnogram.org/CVE-2026-101304</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-101304</guid>
      <description>When fdescfs(4) was mounted in a jail with the &quot;nodup&quot; option, opening /dev/fd/N returned a descriptor that did not inherit FD_RESOLVE_BENEATH or the Capsicum capability rights of descriptor N. A process in a jail that has received a directory file d…</description>
      <category>High</category>
      <pubDate>Thu, 15 Oct 2026 06:46:03 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58100 · 7 HIGH — Memory safety bugs in kqueue copy-on-fork implementation</title>
      <link>https://vulnogram.org/CVE-2026-58100</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58100</guid>
      <description>kqueue_fork_copy_knote() indexed into the child&apos;s file descriptor table using a knote&apos;s file descriptor number without a bounds check. Because the child&apos;s table is copied before knotes are transferred, a concurrent thread in the parent could grow the…</description>
      <category>High</category>
      <pubDate>Thu, 15 Oct 2026 06:31:27 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58099 · 7 HIGH — Memory safety bugs in kqueue copy-on-fork implementation</title>
      <link>https://vulnogram.org/CVE-2026-58099</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58099</guid>
      <description>When copying knotes from a parent kqueue to a child, the copy code did not correctly exclude marker knotes (used internally to track list traversal position) before marking them as in-flux and releasing the kqueue lock. If another thread freed a mark…</description>
      <category>High</category>
      <pubDate>Thu, 15 Oct 2026 06:31:18 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58098 · 8.4 HIGH — Heap out-of-bounds access in semop(2)</title>
      <link>https://vulnogram.org/CVE-2026-58098</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58098</guid>
      <description>When semop(2) blocks waiting for a semaphore condition, it releases the per-set lock and sleeps. Upon waking, it checks the sequence number embedded in the semaphore set&apos;s IPC identifier to detect whether the set was removed while the caller was asle…</description>
      <category>High</category>
      <pubDate>Thu, 15 Oct 2026 06:15:44 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58094 · 7.8 HIGH — TOCTOU race in POSIX shared memory large page configuration</title>
      <link>https://vulnogram.org/CVE-2026-58094</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58094</guid>
      <description>The FIOSSHMLPGCNF ioctl(2) operation configures the page size for a largepage shared memory object. This is intended to be used immediately after creating the object, before any memory is allocated for the object. The handler checked whether a page s…</description>
      <category>High</category>
      <pubDate>Wed, 26 Aug 2026 05:39:42 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58093 · 7 HIGH — Kernel use-after-free via tty ioctls</title>
      <link>https://vulnogram.org/CVE-2026-58093</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58093</guid>
      <description>The TIOCSCTTY ioctl handler drops the tty lock in order to acquire the process tree lock. After reacquiring the tty lock, the handler did not revalidate the state of the terminal, and could proceed to link a terminal that was concurrently being destr…</description>
      <category>High</category>
      <pubDate>Wed, 26 Aug 2026 05:33:30 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58097 · 7.8 HIGH — ppp(8): missing length validation in mp_SetEnddisc()</title>
      <link>https://vulnogram.org/CVE-2026-58097</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58097</guid>
      <description>mp_SetEnddisc() copied a user-supplied PSN endpoint value without length validation, allowing a buffer overflow via the ppp(8) command interface. A local user with access to the ppp(8) command interface can crash ppp(8) or potentially execute arbitra…</description>
      <category>High</category>
      <pubDate>Wed, 26 Aug 2026 05:28:17 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58096 · 8.8 HIGH — ppp(8): missing length validation in LcpDecodeConfig()</title>
      <link>https://vulnogram.org/CVE-2026-58096</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58096</guid>
      <description>LcpDecodeConfig() did not validate the length of received endpoint discriminator options against the minimum required by RFC 1717. Undersized options would trigger an out-of-bounds write. A malicious PPP peer can exploit CVE-2026-58095 and CVE-2026-5…</description>
      <category>High</category>
      <pubDate>Wed, 26 Aug 2026 05:28:09 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58095 · 8.8 HIGH — ppp(8): incorrect length calculation in mp_Enddisc()</title>
      <link>https://vulnogram.org/CVE-2026-58095</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58095</guid>
      <description>mp_Enddisc() used incorrect length calculations when formatting endpoint discriminator addresses for display, allowing a received endpoint option to overflow a global result buffer. A malicious PPP peer can crash ppp(8) or potentially execute arbitra…</description>
      <category>High</category>
      <pubDate>Wed, 26 Aug 2026 05:28:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58092 · 8.1 HIGH — Unauthorized credential switching</title>
      <link>https://vulnogram.org/CVE-2026-58092</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58092</guid>
      <description>In FreeBSD 15.0, the kernel structure used to represent user credentials changed: previously the primary group ID was stored in the first element of the array containing the list of supplementary group IDs, whereas now the primary group ID is stored…</description>
      <category>High</category>
      <pubDate>Wed, 26 Aug 2026 04:46:17 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58091 · 7.8 HIGH — Kernel use-after-free via the SNDCTL_DSP_SYNCSTART ioctl</title>
      <link>https://vulnogram.org/CVE-2026-58091</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58091</guid>
      <description>The implementation of this ioctl attempts to acquire locks on all channels in a sync group. If locking a channel would block, it releases the sync group list lock and sleeps. Upon reawakening, it is possible that the sync group structure is freed, bu…</description>
      <category>High</category>
      <pubDate>Wed, 26 Aug 2026 04:38:19 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58090 · 7.8 HIGH — Use-after-free in unix SOCK_STREAM message handling</title>
      <link>https://vulnogram.org/CVE-2026-58090</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58090</guid>
      <description>The SOCK_STREAM receive path in the unix socket implementation failed to fully detach control messages from the socket buffer before processing them. Some error paths would free those messages, leaving freed data mbufs in the receive socket buffer. A…</description>
      <category>High</category>
      <pubDate>Wed, 26 Aug 2026 04:35:10 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58089 · 7.8 HIGH — hwpmc fails to detach PMCs during exec credential transitions</title>
      <link>https://vulnogram.org/CVE-2026-58089</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58089</guid>
      <description>When a process calls execve(2) to execute a setuid or setgid image, hwpmc(4) is supposed to detach PMCs owned by unprivileged processes. An inverted check meant that this scenario was not handled properly. An unprivileged local user who has attached…</description>
      <category>High</category>
      <pubDate>Wed, 26 Aug 2026 04:30:06 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58088 · 7.4 HIGH — Race condition in ELF core dump segment counting</title>
      <link>https://vulnogram.org/CVE-2026-58088</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58088</guid>
      <description>The ELF core dump code counted the number of dumpable VM map entries, allocated a buffer for the corresponding program headers, then iterated over the map a second time to populate them. A process sharing the address space via rfork(2) can mutate the…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 07:52:13 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58087 · 7.8 HIGH — Heap out-of-bounds access in semctl(2)</title>
      <link>https://vulnogram.org/CVE-2026-58087</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58087</guid>
      <description>The GETALL and SETALL commands in semctl(2) recorded the number of semaphores in the target set, dropped the lock protecting the set, allocated a buffer sized for that count, and reacquired the lock. A sequence-number check was used to verify that th…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 07:47:50 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58086 · 8.1 HIGH — ktrace(2) privilege incorrectly validated in jails</title>
      <link>https://vulnogram.org/CVE-2026-58086</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58086</guid>
      <description>As an inadvertent side effect of an unrelated code change, PRIV_KTRACE was always denied to a jailed root user. Tracing configured by a jailed root user was therefore not flagged as privileged. An unprivileged user in a jail that has permission to de…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 07:42:10 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58085 · 7.5 HIGH 🌩️ — Missing MAC validation in wg(4) packet decryption</title>
      <link>https://vulnogram.org/CVE-2026-58085</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58085</guid>
      <description>After dispatching a decrypt operation to OCF and receiving the result, the wg(4) driver failed to check whether the MAC verification step succeeded. The driver thus silently accepted packets with an invalid Poly1305 authentication tag. A remote attac…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 19 Aug 2026 07:38:50 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58084 · 5.5 MEDIUM — Kernel stack disclosure via timer_settime(2)</title>
      <link>https://vulnogram.org/CVE-2026-58084</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58084</guid>
      <description>To retrieve the previous timer value, the kernel calls realtimer_gettime(), which obtains the current time for the timer&apos;s clock. For a timer using CLOCK_TAI this can fail when no TAI offset has been configured, but the error return was not checked,…</description>
      <category>Medium</category>
      <pubDate>Wed, 19 Aug 2026 07:31:42 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58083 · 8.4 HIGH — Use-after-free in kqueue copy-on-fork</title>
      <link>https://vulnogram.org/CVE-2026-58083</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58083</guid>
      <description>While the kernel was copying knotes during fork, a knote with a timer-based filter could fire and be enqueued on the kqueue&apos;s active list before the copy was complete. The copy routine did not account for this and could enqueue the new knote a second…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 07:28:28 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58082 · 9.8 CRITICAL 🌩️ — Stack based buffer overflow in iconv(3)</title>
      <link>https://vulnogram.org/CVE-2026-58082</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58082</guid>
      <description>The ISO-2022 encoding module used a stack buffer sized to MB_LEN_MAX (6 bytes) for intermediate character output. Some ISO-2022 variants can require up to 10 bytes per character, in which case conversions can trigger a stack buffer overflow of up to…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 19 Aug 2026 07:20:37 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-58081 · 9.8 CRITICAL 🌩️ — Heap based buffer overflow in iconv(3)</title>
      <link>https://vulnogram.org/CVE-2026-58081</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-58081</guid>
      <description>Several encoding modules, including HZ, UTF-7, VIQR, and ZW, did not properly check the size of the caller-supplied output buffer before writing converted characters. An application that uses iconv(3) to convert untrusted input to or from one of the…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 19 Aug 2026 07:20:26 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49425 · 5.5 MEDIUM — Kernel stack disclosure in 32-bit compatibility support</title>
      <link>https://vulnogram.org/CVE-2026-49425</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49425</guid>
      <description>The compat32 kevent() handler translates a 64-bit kevent struct into a stack- declared 32-bit struct. It did not first zero the stack struct. An unprivileged user may observe a small amount of uninitialized kernel stack data, which may contain sensit…</description>
      <category>Medium</category>
      <pubDate>Wed, 19 Aug 2026 07:11:21 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49424 · 5.5 MEDIUM — Kernel stack disclosure in Linux compatibility layer</title>
      <link>https://vulnogram.org/CVE-2026-49424</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49424</guid>
      <description>The Linux waitid() implementation translates a FreeBSD siginfo_t struct into a stack-declared Linux siginfo_t. It did not first zero the stack struct. An unprivileged user may observe 104 bytes of uninitialized kernel stack data, which may contain se…</description>
      <category>Medium</category>
      <pubDate>Wed, 19 Aug 2026 07:08:35 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49423 · 3.3 LOW — Remote DOS via uninitialized memory access in KTLS receive</title>
      <link>https://vulnogram.org/CVE-2026-49423</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49423</guid>
      <description>When building the iovec array for a received TLS 1.2 CBC record, ktls_ocf_tls_cbc_decrypt() incremented the iovec index for every mbuf in the chain, including mbufs that were skipped because they contained only TLS header bytes. This left uninitializ…</description>
      <category>Low</category>
      <pubDate>Wed, 19 Aug 2026 07:01:49 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49426 · 3.3 LOW — Incorrect audit records for ptrace(2) syscall requests</title>
      <link>https://vulnogram.org/CVE-2026-49426</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49426</guid>
      <description>When auditing a system call executed via ptrace(PT_SC_REMOTE), the kernel passed the return value of an internal setup function to AUDIT_SYSCALL_EXIT() rather than the actual result of the executed system call. As a result, committed audit records fo…</description>
      <category>Low</category>
      <pubDate>Wed, 19 Aug 2026 06:04:36 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49428 · 8.4 HIGH — posixshm: system calls can incorrectly free memory of largepage objects</title>
      <link>https://vulnogram.org/CVE-2026-49428</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49428</guid>
      <description>Certain system calls, such open(2) with the O_TRUNC flag set, and fspacectl(2), could incorrectly free memory in largepage objects. These operations are not permitted on largepage objects, but the implementation did not verify this. An unprivileged l…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 05:57:04 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49427 · 8.8 HIGH — posixshm: largepage shared memory objects not explicitly wired</title>
      <link>https://vulnogram.org/CVE-2026-49427</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49427</guid>
      <description>Pages belonging to largepage shared memory objects were not explicitly wired. When sendfile(2) transmitted such an object with the SF_NOCACHE flag, it freed the underlying pages after transmission even though existing mappings still referred to them.…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 05:56:53 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49422 · 8.4 HIGH — Use-after-free in TCP RACK stack option handler</title>
      <link>https://vulnogram.org/CVE-2026-49422</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49422</guid>
      <description>The RACK setsockopt(2) handler drops the connection lock in order to copy option data from userspace, then reacquires the lock. After reacquiring, it verifies that the TCP stack had not been switched away, but did not reload its pointer to the stack&apos;…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 05:28:32 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49421 · 7.1 HIGH — unlinkat(2) ignores AT_RESOLVE_BENEATH flag</title>
      <link>https://vulnogram.org/CVE-2026-49421</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49421</guid>
      <description>The kernel function that implements unlinkat(2) and funlinkat(2) validated the AT_RESOLVE_BENEATH flag but failed to pass it through to the underlying path lookup. The flag was silently dropped, so path resolution was not actually restricted. A proce…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 05:25:43 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49420 · 8.8 HIGH — Buffer overflow in libalias RTSP handler</title>
      <link>https://vulnogram.org/CVE-2026-49420</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49420</guid>
      <description>The RTSP handler in libalias rewrote outgoing packets into a fixed-length stack buffer without checking whether the rewritten data fit in the buffer, or whether the result fit back in the original packet. A host sending crafted RTSP traffic from insi…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 05:20:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49431 · 3.3 LOW — Incorrect user validation in ZFS_IOC_SET_PROP ioctl</title>
      <link>https://vulnogram.org/CVE-2026-49431</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49431</guid>
      <description>The ZFS_IOC_SET_PROP ioctl, used by zfs-set(8), incorrectly validated the calling user such that an unprivileged user is able to set metadata on a dataset indicating that the dataset has received properties from a zfs-recv(8) stream. Any local user c…</description>
      <category>Low</category>
      <pubDate>Wed, 19 Aug 2026 05:15:37 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49430 · 7.8 HIGH — Kernel heap overflow in ZFS_IOC_RECV_NEW ioctl</title>
      <link>https://vulnogram.org/CVE-2026-49430</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49430</guid>
      <description>The ZFS_IOC_RECV_NEW ioctl, in the heal receive path, similarly truncated a 64-bit payload size to a 32-bit integer for allocation, then used the original 64-bit size as the length for a byteswap operation. A local user with the &quot;receive&quot; delegated Z…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 05:15:29 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49429 · 7.8 HIGH — Kernel heap overflow in ZFS_IOC_USERSPACE_MANY ioctl</title>
      <link>https://vulnogram.org/CVE-2026-49429</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49429</guid>
      <description>The ZFS_IOC_USERSPACE_MANY ioctl, used by zfs-userspace(8), truncated a 64-bit output buffer size to a 32-bit integer for the kernel allocation, but used the original 64-bit size as the buffer limit when writing records. A local user with the &quot;userus…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 05:15:21 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49415 · 8.8 HIGH — Local privilege escalation via execve(2) TOCTOU race</title>
      <link>https://vulnogram.org/CVE-2026-49415</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49415</guid>
      <description>During execve(2) of a SUID binary, the new virtual address space is installed before the process credentials are updated. During this window, a process running as the same user can access the target process&apos;s memory via procfs or linprocfs, because t…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 04:38:24 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49419 · 8.8 HIGH — Jail reference count underflow</title>
      <link>https://vulnogram.org/CVE-2026-49419</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49419</guid>
      <description>When the JAIL_AT_DESC flag is specified, kern_jail_set() and kern_jail_get() released the reference to the caller&apos;s current prison before looking up the jail descriptor. If the descriptor lookup failed, error-handling paths released the same referenc…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 04:32:39 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49418 · 8.8 HIGH — Use-after-free in device pager page list</title>
      <link>https://vulnogram.org/CVE-2026-49418</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49418</guid>
      <description>When msync(MS_INVALIDATE) is called on a mapping of an unmanaged device object, the physical pages in the mapping range are marked invalid but remain in the pager&apos;s page list. A subsequent page fault will cause the fault handler to re-insert the page…</description>
      <category>High</category>
      <pubDate>Wed, 19 Aug 2026 04:14:17 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49416 · 7.8 HIGH — Integer overflow in vt(4) CONS_HISTORY ioctl</title>
      <link>https://vulnogram.org/CVE-2026-49416</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49416</guid>
      <description>The CONS_HISTORY ioctl handler did not adequately validate the requested history size. A large value caused an integer overflow in the buffer size calculation, resulting in a heap allocation smaller than expected. Subsequent initialization of the buf…</description>
      <category>High</category>
      <pubDate>Sat, 27 Jun 2026 09:25:12 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49414 · 7.8 HIGH — ASLR bypass for setuid executables via procctl(2)</title>
      <link>https://vulnogram.org/CVE-2026-49414</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49414</guid>
      <description>The ELF image activator cleared per-process ASLR preference flags for setuid binaries after the code that computes the PIE base address, rather than before. As a result, a user-requested ASLR disable was still in effect at the point where the base ad…</description>
      <category>High</category>
      <pubDate>Sat, 27 Jun 2026 09:22:23 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49413 · 7.1 HIGH — Flaw in Linuxulator execution of setugid binaries</title>
      <link>https://vulnogram.org/CVE-2026-49413</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49413</guid>
      <description>The Linuxulator determined whether a binary was set-user-ID or set-group-ID by checking the P_SUGID process flag. During execve(2), this flag is not yet set at the point where the auxiliary vector is constructed, so AT_SECURE was incorrectly set to z…</description>
      <category>High</category>
      <pubDate>Sat, 27 Jun 2026 09:08:23 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-49412 · 7.8 HIGH — Use-after-free bug in the IPV6_MSFILTER socket option handler</title>
      <link>https://vulnogram.org/CVE-2026-49412</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-49412</guid>
      <description>The kernel handler for IPV6_MSFILTER dropped a serializing lock in order to copy the source-filter list from userspace, then reacquired the lock. During this window another thread could free the multicast filter structure, leaving the handler with a…</description>
      <category>High</category>
      <pubDate>Sat, 27 Jun 2026 09:02:55 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-45259 · 6.5 MEDIUM — sigqueue(2) missing capability mode restriction</title>
      <link>https://vulnogram.org/CVE-2026-45259</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-45259</guid>
      <description>sigqueue(2) was marked as permitted in capability mode with the introduction of Capsicum in 2011, but the implementation of kern_sigqueue did not include a capability mode check restricting signal delivery to the calling process&apos;s own PID. A process…</description>
      <category>Medium</category>
      <pubDate>Sat, 27 Jun 2026 08:59:17 GMT</pubDate>
    </item>
  </channel>
</rss>
