A buffer overflow vulnerability exists in the x509_inet_pton_ipv6() function in Mbed TLS versions 3.5.0 through 3.6.5. This issue is fixed in versions 3.6.6 and 4.1.0. The vulnerability is identified as CWE-121 (stack-based buffer overflow).
CVE-2026-43083 is a vulnerability in Microsoft software version 3.0 related to the net: ioam6 component, involving an out-of-bounds (OOB) condition and a missing lock. The vulnerability details are limited, with no CVSS score or exploit reports available. The affected version is explicitly stated as 3.0. No patch or remediation information is provided in the available data.
CVE-2026-43199 is a vulnerability related to the net/mlx5e driver component in Microsoft software, specifically addressing a "scheduling while atomic" issue in the IPsec MAC address query functionality. The affected version explicitly identified is version 3.0. No CVSS score is provided for this vulnerability. There are no known exploits in the wild at this time. No patch or remediation details are available from the provided data.
In the Linux kernel, the following vulnerability has been resolved:
net: Drop the lock in skb_may_tx_timestamp()
skb_may_tx_timestamp() may acquire sock::sk_callback_lock. The lock must
not be taken in IRQ context, only softirq is okay. A few drivers receive
the timestamp via a dedicated interrupt and complete the TX timestamp
from that handler. This will lead to a deadlock if the lock is already
write-locked on the same CPU.
Taking the lock can be avoided. The socket (pointed by the skb) will
remain valid until the skb is released. The ->sk_socket and ->file
member will be set to NULL once the user closes the socket which may
happen before the timestamp arrives.
If we happen to observe the pointer while the socket is closing but
before the pointer is set to NULL then we may use it because both
pointer (and the file's cred member) are RCU freed.
Drop the lock. Use READ_ONCE() to obtain the individual pointer. Add a
matching WRITE_ONCE() where the pointer are cleared.
CVE-2026-43244 is a vulnerability identified in Microsoft software version 3.0 related to the handling of zero-fragment socket buffers (skb) in the frag_list during partial sendmsg errors. The issue involves improper management of fragmented network packets which could potentially lead to unexpected behavior. No CVSS score is provided for this vulnerability. There are no known exploits in the wild at this time. No patch or remediation information is currently available from the vendor advisory.
CVE-2026-43197 is a vulnerability in Microsoft software version 3.0 related to the netconsole component, where out-of-bounds (OOB) reads may occur because a message is not null-terminated. The vulnerability could potentially lead to memory safety issues. No CVSS score or detailed impact information is provided. No known exploits are reported in the wild. No patch or remediation information is available from the vendor advisory.
CVE-2025-71285 is a vulnerability related to the net: qrtr component involving the MHI auto_queue feature for IPCR DL channels in Microsoft software version 3.0. The provided description does not include technical details about the nature of the vulnerability or its impact. No CVSS score is available for this issue.
CVE-2026-43234 is a vulnerability related to the handling of the NETDEV_CHANGEMTU event when unregistering a slave in Microsoft software version 3.0. The provided information does not include technical details about the nature of the vulnerability or its impact. No CVSS score or exploit details are available.
In the Linux kernel, the following vulnerability has been resolved:
dlm: validate length in dlm_search_rsb_tree
The len parameter in dlm_dump_rsb_name() is not validated and comes
from network messages. When it exceeds DLM_RESNAME_MAXLEN, it can
cause out-of-bounds write in dlm_search_rsb_tree().
Add length validation to prevent potential buffer overflow.
CVE-2026-43036 is a vulnerability related to the net subsystem involving the use of skb_header_pointer() for TCPv4 GSO frag_off check. The information provided is minimal and does not include technical details about the nature of the vulnerability or its impact. The affected version explicitly stated is version 3.0. There is no CVSS score or detailed vendor advisory available to clarify the severity or remediation status.
CVE-2026-31700 is a vulnerability in Microsoft software involving a time-of-check to time-of-use (TOCTOU) race condition on a memory-mapped virtual network header (vnet_hdr) in the tpacket_snd() function. The issue relates to the net/packet subsystem. No CVSS score or detailed impact information is provided.
CVE-2026-43116 is a vulnerability related to netfilter's ctnetlink component in Microsoft software version 3.0. The issue involves ensuring safe access to the master conntrack, which is a part of network connection tracking. No detailed technical exploitation or impact information is provided. There is no CVSS score available for this vulnerability.
CVE-2026-43088 is a vulnerability related to the net subsystem involving af_key and zero aligned sockaddr tail in PF_KEY exports. The vulnerability affects Microsoft product version 3.0. No detailed technical or impact information is provided beyond the identification of the issue. There is no CVSS score available for this vulnerability. No known exploits in the wild have been reported.
CVE-2026-46110 is a vulnerability in the stmmac network driver component related to handling RX memory exhaustion. It involves a potential NULL pointer dereference when the receive memory is exhausted. This could lead to a denial of service or system instability. The vulnerability affects Microsoft products including Azure Linux kernel version 3.0. No CVSS score is provided, and there are no known exploits in the wild. No patch or remediation details are currently available from the vendor advisory. Users should monitor official Microsoft Security Response Center communications for updates.
CVE-2026-46132 is a vulnerability related to the rtnetlink component in Microsoft software, specifically involving zeroing the ifla_vf_broadcast field to prevent a stack information leak in the rtnl_fill_vfinfo function. The affected version is exactly version 3.0. No CVSS score is provided.
CVE-2026-46120 is a vulnerability related to the ip6_gre component in Microsoft software, specifically involving the use of a cached t->net in the ip6erspan_changelink() function. No detailed impact or exploitation information is provided.
CVE-2026-46142 is a vulnerability in Microsoft software identified as 'net: libwx: fix VF illegal register access'. The issue relates to illegal register access within the libwx component. No CVSS score or detailed technical impact information is provided. The affected version is exactly version 3.0. There is no public information about exploitation in the wild or available patches.
CVE-2026-45841 is a vulnerability related to a divide-by-zero error in the netfilter component, specifically in nfnetlink_osf's OSF_WSS_MODULO function. The vulnerability affects Microsoft products including Azure Linux 3.0. No detailed technical description or exploit information is provided. There is no CVSS score assigned, and no known exploits in the wild have been reported. Patch or remediation status is not confirmed from the available data.
CVE-2026-45930 is a vulnerability related to the Microsoft Azure Linux kernel component 'mctp' where netlink message (nlmsg) responses were not properly initialized. The advisory references the Microsoft Support Lifecycle for software support details but does not provide specific technical or impact details. No CVSS score or exploit information is available.
CVE-2026-46027 is a vulnerability related to the net/smc component in Microsoft products, specifically involving early lgr access in the smc_clc_wait_msg function. The provided information does not include technical details about the nature of the vulnerability or its exploitation. There is no CVSS score or detailed impact description available. No known exploits in the wild have been reported. Patch status is not confirmed, and no vendor advisory with remediation details is provided.