Threat database

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

A vulnerability in CoreDNS's rewrite-plugin can cause a nil-pointer panic leading to a remote denial of service (DoS) when a downstream plugin returns a response without an OPT record in the EDNS0 section. This issue affects CoreDNS version 3.0. No CVSS score or detailed vendor advisory is available.

A vulnerability in CoreDNS's proxyproto plugin causes a panic when processing a Proxy Protocol version 2 datagram with a non-UDP transport, resulting in a remote denial of service triggered by a single 28-byte packet. This affects CoreDNS version 3.0. No CVSS score is available for this issue.

A vulnerability exists in GitHub CLI version 3.0 where the 'gh codespace jupyter' command could allow remote code execution when connecting to a malicious Codespace. This issue is tracked as CVE-2026-59831 and is associated with CWE-829 (Inclusion of Functionality from Untrusted Control Sphere). No patch or official remediation has been provided yet. There are no known exploits in the wild at this time.

A use-after-free (UAF) vulnerability in the Linux kernel's Bluetooth subsystem was resolved. The flaw occurs due to a race condition between socket cleanup and connection deletion functions, leading to use of freed memory. This vulnerability affects the handling of listening sockets and concurrent HCI disconnect events. The issue was identified through KASAN and SMP testing, showing multiple use-after-free reports before the fix. The vulnerability is rated high severity due to its potential impact on confidentiality, integrity, and availability.

CVE-2026-40553 is a stack-based buffer overflow vulnerability affecting version 3.0 of gawk. The vulnerability is categorized under CWE-121. There is no CVSS score available, and no known exploits in the wild have been reported. No patch or remediation information is provided in the available data.

CVE-2026-40468 is a heap buffer overflow vulnerability affecting version 3.0 of the gawk software. The vulnerability is identified by Microsoft Security Response Center but lacks detailed technical information and a CVSS score. No known exploits are reported in the wild, and there is no information about available patches or fixes.

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

CVE-2026-53336 is a vulnerability identified in Microsoft software version 3.0 related to the nvmem layouts onie-tlv component, specifically addressing a hang condition when encountering unknown types. The provided description does not include detailed technical information or exploitation methods. No CVSS score is available for this vulnerability.

CVE-2026-53339 is a vulnerability related to a NULL pointer dereference in the i2c qcom-cci driver, specifically in the cci_remove() function. The vulnerability affects version 3.0 of the Microsoft product referenced. No CVSS score or detailed impact information is provided. There is no indication of known exploits in the wild or available patches.

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

A vulnerability affecting certain Arm CPUs in the Linux kernel has been addressed. The issue involves errata where a broadcast TLBI;DSB sequence may complete before the global observation of writes translated by an invalidated TLB entry. This does not affect the invalidation of TLB entries themselves but impacts memory access completion. The mitigation involves applying an additional TLBI;DSB sequence to ensure proper global observation of memory writes. The ARM64_WORKAROUND_REPEAT_TLBI workaround is recommended for affected CPUs. This vulnerability is tracked as CVE-2026-53354 and affects Linux kernel version 3.0.

A vulnerability in the Linux kernel's KVM subsystem related to handling memory dirtying without a running vCPU when the VM is dying has been resolved. The issue involves a WARN triggered incorrectly during VM destruction, which could lead to a memory leak for x86 SEV-ES guests. The fix ensures that warnings about dirtying memory without a running vCPU only occur if the VM is still alive, preventing false positives and memory leaks. This vulnerability does not impact confidentiality or integrity but can cause availability issues due to memory leaks.

A vulnerability in the Linux kernel related to the debugobjects subsystem has been resolved. The issue occurs on real-time (RT) enabled kernels where the fill_pool() function calls rtlock_lock(), which asserts if the current task's pi_blocked_on field is set. This condition can corrupt the priority inheritance chain because a task can only block on one lock. The fix prevents fill_pool() from executing when pi_blocked_on is set, avoiding this assertion failure.

In the Linux kernel, the following vulnerability has been resolved: nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty() nilfs_ioctl_mark_blocks_dirty() uses bd_oblocknr to detect dead blocks by comparing it with the current block number bd_blocknr. If they differ, the block is considered dead and skipped. However, bd_oblocknr should never be 0 since block 0 typically stores the primary superblock and is never a valid GC target block. A corrupted ioctl request with bd_oblocknr set to 0 causes the comparison to incorrectly match when the lookup returns -ENOENT and sets bd_blocknr to 0, bypassing the dead block check and calling nilfs_bmap_mark() on a non-existent block. This causes nilfs_btree_do_lookup() to return -ENOENT, triggering the WARN_ON(ret == -ENOENT). Fix this by rejecting ioctl requests with bd_oblocknr set to 0 at the beginning of each iteration. [ryusuke: slightly modified the commit message and comments for accuracy]