Republished vendor advisory. This CISA CSAF advisory was converted from Siemens ProductCERT's CSAF advisory.
General Recommendations: As a general security measure, Siemens strongly recommends to protect network access to devices with appropriate mechanisms. In order to operate the devices in a protected IT environment, Siemens recommends to configure the environment according to Siemens' operational guidelines for Industrial Security (Download: https://www.siemens.com/cert/operational-guidelines-industrial-security), and to follow the recommendations in the product manuals. Additional information on Industrial Security by Siemens can be found at: https://www.siemens.com/industrialsecurity
Additional Resources: For further inquiries on security vulnerabilities in Siemens products and solutions, please contact the Siemens ProductCERT: https://www.siemens.com/cert/advisories
Credit: Siemens ProductCERT
From CISA's machine-readable CSAF 2.0 advisory (JSON).
| CVE | Weakness | CVSS v3 | Details |
|---|---|---|---|
| CVE-2023-41910 | CWE-125 Out-of-bounds Read | 9.8 Critical |
CVE-2023-41910 An issue was discovered in lldpd before 1.0.17. By crafting a CDP PDU packet with specific CDP_TLV_ADDRESSES TLVs, a malicious actor can remotely force the lldpd daemon to perform an out-of-bounds read on heap memory. This occurs in cdp_decode in daemon/protocols/cdp.c. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2022-39189 | CWE-311 Missing Encryption of Sensitive Data | 7.8 High |
CVE-2022-39189 An issue was discovered the x86 KVM subsystem in the Linux kernel before 5.18.17. Unprivileged guest users can compromise the guest kernel because TLB flush operations are mishandled in certain KVM_VCPU_PREEMPTED situations. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2022-40304 | CWE-415 Double Free | 7.8 High |
CVE-2022-40304 An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be provoked. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-2124 | CWE-787 Out-of-bounds Write | 7.8 High |
CVE-2023-2124 An out-of-bounds memory access flaw was found in the Linux kernel’s XFS file system in how a user restores an XFS image after failure (with a dirty log journal). This flaw allows a local user to crash or potentially escalate their privileges on the system. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-21255 | CWE-787 Out-of-bounds Write | 7.8 High |
CVE-2023-21255 In multiple functions of binder.c, there is a possible memory corruption due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-35788 | CWE-787 Out-of-bounds Write | 7.8 High |
CVE-2023-35788 An issue was discovered in fl_set_geneve_opt in net/sched/cls_flower.c in the Linux kernel before 6.3.7. It allows an out-of-bounds write in the flower classifier code via TCA_FLOWER_KEY_ENC_OPTS_GENEVE packets. This may result in denial of service or privilege escalation. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-52474 | CWE-20 Improper Input Validation | 7.8 High |
CVE-2023-52474 In the Linux kernel, the following vulnerability has been resolved: IB/hfi1: Fix bugs with non-PAGE_SIZE-end multi-iovec user SDMA requests hfi1 user SDMA request processing has two bugs that can cause data corruption for user SDMA requests that have multiple payload iovecs where an iovec other than the tail iovec does not run up to the page boundary for the buffer pointed to by that iovec.a Here are the specific bugs: 1. user_sdma_txadd() does not use struct user_sdma_iovec->iov.iov_len. Rather, user_sdma_txadd() will add up to PAGE_SIZE bytes from iovec to the packet, even if some of those bytes are past iovec->iov.iov_len and are thus not intended to be in the packet. 2. user_sdma_txadd() and user_sdma_send_pkts() fail to advance to the next iovec in user_sdma_request->iovs when the current iovec is not PAGE_SIZE and does not contain enough data to complete the packet. The transmitted packet will contain the wrong data from the iovec pages. This has not been an issue with SDMA packets from hfi1 Verbs or PSM2 because they only produce iovecs that end short of PAGE_SIZE as the tail iovec of an SDMA request. Fixing these bugs exposes other bugs with the SDMA pin cache (struct mmu_rb_handler) that get in way of supporting user SDMA requests with multiple payload iovecs whose buffers do not end at PAGE_SIZE. So this commit fixes those issues as well. Here are the mmu_rb_handler bugs that non-PAGE_SIZE-end multi-iovec payload user SDMA requests can hit: 1. Overlapping memory ranges in mmu_rb_handler will result in duplicate pinnings. 2. When extending an existing mmu_rb_handler entry (struct mmu_rb_node), the mmu_rb code (1) removes the existing entry under a lock, (2) releases that lock, pins the new pages, (3) then reacquires the lock to insert the extended mmu_rb_node. If someone else comes in and inserts an overlapping entry between (2) and (3), insert in (3) will fail. The failure path code in this case unpins _all_ pages in either the original mmu_rb_node or the new mmu_rb_node that was inserted between (2) and (3). 3. In hfi1_mmu_rb_remove_unless_exact(), mmu_rb_node->refcount is incremented outside of mmu_rb_handler->lock. As a result, mmu_rb_node could be evicted by another thread that gets mmu_rb_handler->lock and checks mmu_rb_node->refcount before mmu_rb_node->refcount is incremented. 4. Related to #2 above, SDMA request submission failure path does not check mmu_rb_node->refcount before freeing mmu_rb_node object. If there are other SDMA requests in progress whose iovecs have pointers to the now-freed mmu_rb_node(s), those pointers to the now-freed mmu_rb nodes will be dereferenced when those SDMA requests complete. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2022-40303 | CWE-190 Integer Overflow or Wraparound | 7.5 High |
CVE-2022-40303 An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to access an array at a negative 2GB offset, typically leading to a segmentation fault. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-0464 | CWE-295 Improper Certificate Validation | 7.5 High |
CVE-2023-0464 A security vulnerability has been identified in all supported versions of OpenSSL related to the verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit this vulnerability by creating a malicious certificate chain that triggers exponential use of computational resources, leading to a denial-of-service (DoS) attack on affected systems. Policy processing is disabled by default but can be enabled by passing the `-policy` argument to the command line utilities or by calling the `X509_VERIFY_PARAM_set1_policies()` function. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-27321 | CWE-1325 Improperly Controlled Sequential Memory Allocation | 7.5 High |
CVE-2023-27321 OPC Foundation UA .NET Standard ConditionRefresh Resource Exhaustion Denial-of-Service Vulnerability. This vulnerability allows remote attackers to create a denial-of-service condition on affected installations of OPC Foundation UA .NET Standard. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of OPC UA ConditionRefresh requests. By sending a large number of requests, an attacker can consume all available resources on the server. An attacker can leverage this vulnerability to create a denial-of-service condition on the system. Was ZDI-CAN-20505. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-28319 | CWE-416 Use After Free | 7.5 High |
CVE-2023-28319 A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the fingerprint before it returns an error message containing the (now freed) hash. This flaw risks inserting sensitive heap-based data into the error message that might be shown to users or otherwise get leaked and revealed. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-0286 | CWE-20 Improper Input Validation | 7.4 High |
CVE-2023-0286 There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2022-45886 | CWE-20 Improper Input Validation | 7.0 High |
CVE-2022-45886 An issue was discovered in the Linux kernel through 6.0.9. drivers/media/dvb-core/dvb_net.c has a .disconnect versus dvb_device_open race condition that leads to a use-after-free. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2022-45919 | CWE-416 Use After Free | 7.0 High |
CVE-2022-45919 An issue was discovered in the Linux kernel through 6.0.10. In drivers/media/dvb-core/dvb_ca_en50221.c, a use-after-free can occur is there is a disconnect after an open, because of the lack of a wait_event. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-35823 | CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | 7.0 High |
CVE-2023-35823 An issue was discovered in the Linux kernel before 6.3.2. A use-after-free was found in saa7134_finidev in drivers/media/pci/saa7134/saa7134-core.c. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-35824 | CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | 7.0 High |
CVE-2023-35824 An issue was discovered in the Linux kernel before 6.3.2. A use-after-free was found in dm1105_remove in drivers/media/pci/dm1105/dm1105.c. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-35828 | CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | 7.0 High |
CVE-2023-35828 An issue was discovered in the Linux kernel before 6.3.2. A use-after-free was found in renesas_usb3_remove in drivers/usb/gadget/udc/renesas_usb3.c. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-35829 | CWE-416 Use After Free | 7.0 High |
CVE-2023-35829 An issue was discovered in the Linux kernel before 6.3.2. A use-after-free was found in rkvdec_remove in drivers/staging/media/rkvdec/rkvdec.c. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2024-0775 | CWE-20 Improper Input Validation | 6.7 Medium |
CVE-2024-0775 A use-after-free flaw was found in the __ext4_remount in fs/ext4/super.c in ext4 in the Linux kernel. This flaw allows a local user to cause an information leak problem while freeing the old quota file names before a potential failure, leading to a use-after-free. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2022-1015 | CWE-787 Out-of-bounds Write | 6.6 Medium |
CVE-2022-1015 A flaw was found in the Linux kernel in linux/net/netfilter/nf_tables_api.c of the netfilter subsystem. This flaw allows a local user to cause an out-of-bounds write issue. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2022-40225 | CWE-681 Incorrect Conversion between Numeric Types | 6.5 Medium |
CVE-2022-40225 Casting an internal value could lead to floating point exception under certain circumstances. This could allow an attacker to cause a denial of service condition on affected devices. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2022-4304 | CWE-326 Inadequate Encryption Strength | 5.9 Medium |
CVE-2022-4304 A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2022-4450 | CWE-415 Double Free | 5.9 Medium |
CVE-2022-4450 The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-0215 | CWE-416 Use After Free | 5.9 Medium |
CVE-2023-0215 The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL cms and smime command line applications are similarly affected. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2021-47178 | CWE-20 Improper Input Validation | 5.5 Medium |
CVE-2021-47178 In the Linux kernel, the following vulnerability has been resolved: scsi: target: core: Avoid smp_processor_id() in preemptible code. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-0160 | CWE-667 Improper Locking | 5.5 Medium |
CVE-2023-0160 A deadlock flaw was found in the Linux kernel’s BPF subsystem. This flaw allows a local user to potentially crash the system. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-0465 | CWE-295 Improper Certificate Validation | 5.3 Medium |
CVE-2023-0465 Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks. Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether. Policy processing is disabled by default but can be enabled by passing the `-policy` argument to the command line utilities or by calling the `X509_VERIFY_PARAM_set1_policies()` function. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-0466 | CWE-295 Improper Certificate Validation | 5.3 Medium |
CVE-2023-0466 The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-50763 | CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop') | 4.9 Medium |
CVE-2023-50763 The web server of affected products, if configured to allow the import of PKCS12 containers, could end up in an infinite loop when processing incomplete certificate chains. This could allow an authenticated remote attacker to create a denial of service condition by importing specially crafted PKCS12 containers. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2022-45887 | CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | 4.7 Medium |
CVE-2022-45887 An issue was discovered in the Linux kernel through 6.0.9. drivers/media/usb/ttusb-dec/ttusb_dec.c has a memory leak because of the lack of a dvb_frontend_detach call. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-1017 | CWE-787 Out-of-bounds Write | 4.4 Medium |
CVE-2023-1017 An out-of-bounds write vulnerability exists in TPM2.0's Module Library allowing writing of a 2-byte data past the end of TPM2.0 command in the CryptParameterDecryption routine. An attacker who can successfully exploit this vulnerability can lead to denial of service (crashing the TPM chip/process or rendering it unusable) and/or arbitrary code execution in the TPM context. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
| CVE-2023-2269 | CWE-667 Improper Locking | 4.4 Medium |
CVE-2023-2269 A denial of service problem was found, due to a possible recursive locking scenario, resulting in a deadlock in table_clear in drivers/md/dm-ioctl.c in the Linux Kernel Device Mapper-Multipathing sub-component. Vendor fix: Update to V2.4.8 or later version ↗ Affected, fixed & timelineAffected:
|
Scores and weakness types are as CISA or the republishing vendor stated them in this advisory; the linked CVE pages carry the independently enriched CVSS and SSVC assessments.
No coverage found in monitored research blogs or news feeds.
| CVE | CVSS | Affected |
|---|---|---|
| CVE-2022-39189 | 7.8 High | n/a n/a An issue was discovered the x86 KVM subsystem in the Linux kernel before 5.18.17. Unprivileged guest users can compromise the guest kernel because TL… |
| CVE-2022-40304 | 7.8 High | n/a n/a An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a hash table key, potentially leading to subsequ… |
| CVE-2023-35788 | 7.8 High | n/a n/a An issue was discovered in fl_set_geneve_opt in net/sched/cls_flower.c in the Linux kernel before 6.3.7. It allows an out-of-bounds write in the flow… |
| CVE-2021-47178 | 7.5 High | Linux Linux In the Linux kernel, the following vulnerability has been resolved: scsi: target: core: Avoid smp_processor_id() in preemptible code The BUG messag… |
| CVE-2022-40303 | 7.5 High | n/a n/a An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the XML_PARSE_HUGE parser option enabled, several i… |
| CVE-2022-4450 | 7.5 High | OpenSSL OpenSSL The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload da… |
| CVE-2023-0215 | 7.5 High | OpenSSL OpenSSL The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to supp… |
| CVE-2023-0464 | 7.5 High | OpenSSL OpenSSL A security vulnerability has been identified in all supported versions of OpenSSL related to the verification of X.509 certificate chains that inclu… |
| CVE-2023-27321 | 7.5 High | OPC Foundation UA .NET Standard OPC Foundation UA .NET Standard ConditionRefresh Resource Exhaustion Denial-of-Service Vulnerability. This vulnerability allows remote attackers to c… |
| CVE-2023-28319 | 7.5 High | n/a https://github.com/curl/curl A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA 256 hash. … |
| CVE-2023-0286 | 7.4 High | OpenSSL OpenSSL There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRI… |
| CVE-2023-35823 | 7.0 High | n/a n/a An issue was discovered in the Linux kernel before 6.3.2. A use-after-free was found in saa7134_finidev in drivers/media/pci/saa7134/saa7134-core.c. |
| CVE-2023-35824 | 7.0 High | n/a n/a An issue was discovered in the Linux kernel before 6.3.2. A use-after-free was found in dm1105_remove in drivers/media/pci/dm1105/dm1105.c. |
| CVE-2023-35828 | 7.0 High | n/a n/a An issue was discovered in the Linux kernel before 6.3.2. A use-after-free was found in renesas_usb3_remove in drivers/usb/gadget/udc/renesas_usb3.c. |
| CVE-2024-0775 | 6.7 Medium | Linux kernel A use-after-free flaw was found in the __ext4_remount in fs/ext4/super.c in ext4 in the Linux kernel. This flaw allows a local user to cause an infor… |
| CVE-2022-40225 | 6.5 Medium | Siemens SIPLUS TIM 1531 IRC A vulnerability has been identified in SIPLUS TIM 1531 IRC (6AG1543-1MX00-7XE0) (All versions < V2.4.8), TIM 1531 IRC (6GK7543-1MX00-0XE0) (All versi… |
| CVE-2022-4304 | 5.9 Medium | OpenSSL OpenSSL A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in … |
| CVE-2023-0465 | 5.3 Medium | OpenSSL OpenSSL Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain check… |
| CVE-2023-0466 | 5.3 Medium | OpenSSL OpenSSL The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. How… |
| CVE-2023-50763 | 4.9 Medium | Siemens SIMATIC CP 1542SP-1 A vulnerability has been identified in SIMATIC CP 1542SP-1 (6GK7542-6UX00-0XE0) (All versions < V2.3), SIMATIC CP 1542SP-1 IRC (6GK7542-6VX00-0XE0) (… |
| CVE-2022-45887 | 4.7 Medium | n/a n/a An issue was discovered in the Linux kernel through 6.0.9. drivers/media/usb/ttusb-dec/ttusb_dec.c has a memory leak because of the lack of a dvb_fro… |
| CVE-2023-0160 | 4.7 Medium | n/a kernel A deadlock flaw was found in the Linux kernel’s BPF subsystem. This flaw allows a local user to potentially crash the system. |
| CVE-2022-1015 | — | n/a kernel A flaw was found in the Linux kernel in linux/net/netfilter/nf_tables_api.c of the netfilter subsystem. This flaw allows a local user to cause an out… |
| CVE-2022-45886 | — | n/a n/a An issue was discovered in the Linux kernel through 6.0.9. drivers/media/dvb-core/dvb_net.c has a .disconnect versus dvb_device_open race condition t… |
| CVE-2022-45919 | — | n/a n/a An issue was discovered in the Linux kernel through 6.0.10. In drivers/media/dvb-core/dvb_ca_en50221.c, a use-after-free can occur is there is a disc… |
| CVE-2023-1017 | — | Trusted Computing Group TPM2.0 An out-of-bounds write vulnerability exists in TPM2.0's Module Library allowing writing of a 2-byte data past the end of TPM2.0 command in the CryptP… |
| CVE-2023-2124 | — | n/a Kernel An out-of-bounds memory access flaw was found in the Linux kernel’s XFS file system in how a user restores an XFS image after failure (with a dirty l… |
| CVE-2023-21255 | — | Google Android In multiple functions of binder.c, there is a possible memory corruption due to a use after free. This could lead to local escalation of privilege wi… |
| CVE-2023-2269 | — | n/a Kernel A denial of service problem was found, due to a possible recursive locking scenario, resulting in a deadlock in table_clear in drivers/md/dm-ioctl.c … |
| CVE-2023-35829 | — | n/a n/a An issue was discovered in the Linux kernel before 6.3.2. A use-after-free was found in rkvdec_remove in drivers/staging/media/rkvdec/rkvdec.c. |
| CVE-2023-41910 | — | n/a n/a An issue was discovered in lldpd before 1.0.17. By crafting a CDP PDU packet with specific CDP_TLV_ADDRESSES TLVs, a malicious actor can remotely for… |
| CVE-2023-52474 | — | Linux Linux In the Linux kernel, the following vulnerability has been resolved: IB/hfi1: Fix bugs with non-PAGE_SIZE-end multi-iovec user SDMA requests hfi1 us… |
Named by the advisory itself. Each CVE links to its tracked detail page.
Each vendor links to its Known Exploited Vulnerabilities catalog page. Only vendors that appear in the KEV catalog are listed, either because the publication cites one of their KEV entries or because it names them directly.