Category: FreeBSD
-
FreeBSD security vulnerability (CVE-2025-0662)
CVE-2025-0662 identifies a vulnerability in FreeBSD’s ktrace facility, which is used for tracing kernel and user programs. In certain scenarios, ktrace logs variable-sized sockaddr structures to userspace. When the actual sockaddr is shorter than its full size, the entire structure is still copied, resulting in up to 14 bytes of uninitialized kernel memory being exposed…
-
FreeBSD security vulnerability (CVE-2025-0374)
CVE-2025-0374 is a security vulnerability identified in FreeBSD’s etcupdate utility. When etcupdate encounters conflicts during file merging, it saves a version containing conflict markers in /var/db/etcupdate/conflicts. This temporary file does not preserve the original file’s permissions and is world-readable, potentially exposing sensitive information. Files that typically have restricted access, such as /etc/master.passwd, could be affected.…
-
FreeBSD security vulnerability (CVE-2025-0373)
CVE-2025-0373 is a security vulnerability identified in certain filesystems of FreeBSD operating systems. Specifically, on 64-bit systems, the function VOP_VPTOFH() in the cd9660, tarfs, and ext2fs filesystems contains a stack buffer overflow that overflows the destination FID buffer by 4 bytes. This vulnerability can be exploited when an NFS server exports one of these affected…
-
FreeBSD security vulnerability (CVE-2024-41721)
CVE-2024-41721 refers to a vulnerability in FreeBSD’s USB subsystem, specifically related to the XHCI (eXtensible Host Controller Interface) emulation in the bhyve hypervisor. The flaw arises from insufficient boundary validation, leading to an out-of-bounds read on the heap. This vulnerability can potentially allow an attacker to perform arbitrary writes and execute remote code. Affected versions…
-
FreeBSD security vulnerability (CVE-2024-43102)
CVE-2024-43102 is a critical vulnerability affecting FreeBSD, specifically related to the improper handling of anonymous shared memory mappings in the kernel. This vulnerability is tied to the UMTX_SHM_DESTROY operation within the UMTX_OP_SHM API. If exploited, it can lead to a premature freeing of memory, which may result in a kernel panic or enable further “use-after-free”…