huzaifas-sidhpurwala/RedHat-security-VeX huggingface dataset:
Keras: Denial of Service via crafted HDF5 weight loading file
CVE: CVE-2026-0897
Component: Keras
CWE: CWE-770
Severity: Important
CVSS v3: 7.5/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H
Release date: 2026-01-15T14:09:53.603000+00:00

A flaw was found in Keras. A remote attacker can cause a Denial of Service (DoS) by providing a specially crafted .keras archive containing a model weights file (model.weights.h5) that declares an extremely large data shape. This can lead to excessive memory allocation, resulting in memory exhaustion and a crash of the Python interpreter.

Statement: This vulnerability is rated Important for Red Hat OpenShift AI. A remote attacker can cause a Denial of Service (DoS) by providing a crafted `.keras` archive with an excessively large dataset shape, leading to memory exhaustion. This impacts Red Hat OpenShift AI components that utilize Keras for model handling.

Remediation:
For Red Hat OpenShift AI 2.25.3 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update:

https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
For Red Hat OpenShift AI 3.3 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update:

https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
The Model Transparency CLI Image is a containerized command-line tool for signing and verifying AI/ML workloads against a private Red Hat Trusted Artifact Signer (RHTAS) instance. It lets teams create signatures and attestations for model artifacts and validate them at build or deploy time using enterprise trust material (e.g., Fulcio/Rekor).

For details on using the Model Transparency CLI image, refer to the product documentation at https://access.redhat.com/documentation/en-us/red_hat_trusted_artifact_signer/1.3

You can find the release notes for this version of Red Hat Trusted Artifact Signer at https://access.redhat.com/documentation/en-us/red_hat_trusted_artifact_signer/1.3/html-single/release_notes/index
To mitigate this issue, avoid loading Keras model archives from untrusted sources. If processing untrusted Keras model archives is unavoidable, ensure they are processed within an isolated and resource-constrained environment to limit the impact of potential memory exhaustion attacks.
slab: fix kmalloc_nolock() context check for PREEMPT_RT
CVE: CVE-2026-23134
Component: kernel
Severity: Moderate
Release date: 2026-02-14T00:00:00+00:00

In the Linux kernel, the following vulnerability has been resolved:

slab: fix kmalloc_nolock() context check for PREEMPT_RT

On PREEMPT_RT kernels, local_lock becomes a sleeping lock. The current
check in kmalloc_nolock() only verifies we're not in NMI or hard IRQ
context, but misses the case where preemption is disabled.

When a BPF program runs from a tracepoint with preemption disabled
(preempt_count > 0), kmalloc_nolock() proceeds to call
local_lock_irqsave() which attempts to acquire a sleeping lock,
triggering:

  BUG: sleeping function called from invalid context
  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 6128
  preempt_count: 2, expected: 0

Fix this by checking !preemptible() on PREEMPT_RT, which directly
expresses the constraint that we cannot take a sleeping lock when
preemption is disabled. This encompasses the previous checks for NMI
and hard IRQ contexts while also catching cases where preemption is
disabled.


Remediation:
util-linux: Access control bypass due to improper hostname canonicalization
CVE: CVE-2026-3184
Component: util-linux
CWE: CWE-289
Severity: Low
CVSS v3: 3.6/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Release date: 2026-02-25T04:04:00+00:00

No description is available for this CVE.

Statement: This issue was rated as a Low severity issue. This is an authorization policy bypass limited to host-based access control decisions. It does not bypass authentication or grant elevated privileges. Exploitation is configuration-dependent and primarily affects legacy or uncommon remote login pathways, but it can violate administrator intent and weaken PAM-based security policy enforcement.

Remediation:
TechDocs Mkdocs configuration key enables arbitrary code execution
CVE: CVE-2026-29186
Component: backstage/plugin-techdocs-node
CWE: CWE-791
Severity: Important
CVSS v3: 8.8/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L
Release date: 2026-03-07T15:03:51.422000+00:00

A flaw was found in Backstage. The backstage/plugin-techdocs-node package uses an allowlist to filter dangerous MkDocs configuration keys during the documentation build process. A gap in this allowlist allows attackers to craft an mkdocs.yml file that causes arbitrary Python code execution.

Statement: To exploit this issue, an attacker needs commit access to a repository that Backstage is configured to track and build in order to introduce a malicious mkdocs.yml file into the TechDocs build pipeline. Additionally, an attacker can execute arbitrary Python code but the payload is confined by the permissions granted to the TechDocs build process which is typically a restricted service account, limiting the impact of this vulnerability. Due to these reasons, this vulnerability has been rated with an important severity.

Remediation:
To mitigate this issue, enable docker isolation by updating the Backstage configuration to use 'runIn: docker' instead of 'runIn: local', confining the arbitrary Python code execution to a containerized environment. Additionally, limit commit access to repositories tracked by Backstage to trusted contributors only, and enforce mandatory pull request (PR) reviews for any modifications made to the mkdocs.yml file.
regmap: Fix race condition in hwspinlock irqsave routine
CVE: CVE-2026-23071
Component: kernel
CWE: CWE-821
Severity: Moderate
CVSS v3: 5.6/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Release date: 2026-02-04T00:00:00+00:00

A race condition vulnerability was found in the Linux kernel's regmap subsystem when using hardware spinlocks with IRQ save. The shared spinlock_flags member address was passed directly to hwspin_lock_timeout_irqsave(), allowing multiple contexts contending for the lock to overwrite the shared flags variable. This could corrupt the IRQ state for the current lock owner, leading to improper interrupt handling.

Statement: This race condition affects embedded systems using regmap with hardware spinlocks, primarily ARM-based SoCs with shared register access. Exploitation requires concurrent access from multiple contexts and specific timing. The corrupted IRQ state could cause interrupt handling issues, but practical exploitation for code execution is unlikely.

Remediation:
Use-after-free in the JavaScript: GC component
CVE: CVE-2026-2795
Component: firefox
Severity: Important
CVSS v3: 7.5/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Release date: 2026-02-24T13:33:26.111000+00:00

Use-after-free in the JavaScript: GC component. This vulnerability affects Firefox < 148 and Thunderbird < 148.

Statement: Red Hat Product Security rates the severity of this flaw as determined by the Mozilla Foundation Security Advisory.

Remediation:
Sandbox escape in the Messaging System component
CVE: CVE-2026-0881
Component: firefox
Severity: Important
CVSS v3: 7.5/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Release date: 2026-01-13T13:30:55.122000+00:00

Sandbox escape in the Messaging System component. This vulnerability affects Firefox < 147 and Thunderbird < 147.

Statement: Red Hat Product Security rates the severity of this flaw as determined by the Mozilla Foundation Security Advisory.

Remediation:
igc: Reduce TSN TX packet buffer from 7KB to 5KB per queue
CVE: CVE-2026-23122
Component: kernel
CWE: CWE-770
Severity: Moderate
CVSS v3: 4.7/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Release date: 2026-02-14T00:00:00+00:00

A flaw was found in the Linux kernel's igc (Intel I225/I226) Ethernet driver. The TX packet buffer configuration of 7KB per queue for Time-Sensitive Networking (TSN) mode can cause TX unit hangs under heavy timestamping workloads. This occurs because the buffer size exceeds the hardware's recommended configuration, leading to network interface unavailability.

Statement: This issue specifically affects Intel I225/I226 Ethernet controllers when using TSN features with hardware timestamping under heavy load. The fix aligns the buffer configuration with Intel's software user manual recommendations. Systems not using TSN or heavy timestamping workloads are unlikely to be affected.

Remediation:
To mitigate this issue, prevent the igc module from being loaded. See https://access.redhat.com/solutions/41278 for instructions on how to blacklist kernel modules.
tracing: Fix crash on synthetic stacktrace field usage
CVE: CVE-2026-23088
Component: kernel
CWE: CWE-843
Severity: Low
CVSS v3: 5.6/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Release date: 2026-02-04T00:00:00+00:00

A NULL pointer dereference vulnerability was found in the Linux kernel's tracing subsystem when using synthetic events with stacktrace fields. When a synthetic event is created based on another synthetic event that contains a stacktrace field, the stacktrace field is incorrectly treated as a normal field instead of a dynamic array. This causes trace_event_raw_event_synth() to dereference invalid memory when the event is enabled.

Statement: This vulnerability requires root privileges to configure synthetic tracing events through debugfs/tracefs. The specific trigger involves chaining synthetic events with stacktrace fields in histogram triggers. While the crash is reproducible with the described sequence, it requires deliberate configuration of complex tracing rules.

Remediation:
thunderbird: Information disclosure due to JIT miscompilation in the JavaScript Engine: JIT component
CVE: CVE-2026-2783
Component: firefox
Severity: Moderate
CVSS v3: 6.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Release date: 2026-02-24T13:33:16.921000+00:00

A flaw was found in Firefox and Thunderbird. The Mozilla Foundation's Security Advisory describes the following issue:
Information disclosure due to JIT miscompilation in the JavaScript Engine: JIT component

Statement: Red Hat Product Security rates the severity of this flaw as determined by the Mozilla Foundation Security Advisory.

Remediation:
pypdf: Denial of Service via crafted PDF with TreeObject outlines
CVE: CVE-2026-27024
Component: pypdf
CWE: CWE-835
Severity: Moderate
CVSS v3: 5.4/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Release date: 2026-02-20T21:10:07.864000+00:00

pypdf is a free and open-source pure-python PDF library. Prior to 6.7.1, an attacker who uses this vulnerability can craft a PDF which leads to an infinite loop. This requires accessing the children of a TreeObject, for example as part of outlines. This vulnerability is fixed in 6.7.1.


Remediation:
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
iommu/io-pgtable-arm: fix size_t signedness bug in unmap path
CVE: CVE-2026-23067
Component: kernel
CWE: CWE-190
Severity: Moderate
CVSS v3: 5.6/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Release date: 2026-02-04T00:00:00+00:00

An integer signedness bug was found in the Linux kernel's ARM IOMMU page table implementation. The __arm_lpae_unmap() function returns size_t (unsigned) but was returning -ENOENT (negative error code) on error. The negative value becomes a huge positive number (0xFFFFFFFFFFFFFFFE on 64-bit) which propagates through the call chain, causing IOVA address overflow in __iommu_unmap() and triggering a BUG_ON in iommu_pgsize() due to invalid address alignment.

Statement: This bug affects ARM-based systems using the LPAE (Large Physical Address Extension) IOMMU page table format. The crash occurs when attempting to unmap an already-unmapped PTE, which can happen during device driver cleanup or error recovery paths. The impact is limited to denial of service through a kernel panic.

Remediation:
Quill: Sensitive data exfiltration via Server-Side Request Forgery (SSRF)
CVE: CVE-2026-31959
Component: github.com/anchore/quill
CVSS v3: 5.2/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Release date: 2026-03-11T19:30:46.584000+00:00

A flaw was found in Quill. This Server-Side Request Forgery (SSRF) vulnerability occurs when Quill attempts to fetch Apple notarization submission logs. An attacker, capable of tampering with API responses from Apple's notarization service (e.g., in environments with TLS-intercepting proxies), can supply a malicious URL. This causes the Quill client to make requests to arbitrary internal or external network destinations, potentially leading to the exfiltration of sensitive data such as cloud provider credentials or internal service responses.

Statement: Red Hat Product Security has determined that this vulnerability does not affect any currently supported Red Hat product. This assessment may evolve based on further analysis and discovery. For more information about this vulnerability and the products it affects, please see the linked references.

Remediation:
thunderbird: Use-after-free in the JavaScript: WebAssembly component
CVE: CVE-2026-2804
Component: firefox
Severity: Moderate
CVSS v3: 6.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Release date: 2026-02-24T13:33:32.144000+00:00

Use-after-free in the JavaScript: WebAssembly component. This vulnerability affects Firefox < 148 and Thunderbird < 148.

Statement: Red Hat Product Security rates the severity of this flaw as determined by the Mozilla Foundation Security Advisory.

Remediation:
ydb: Denial of Service via memory leak
CVE: CVE-2026-24825
Component: ydb
CWE: CWE-401
Severity: Moderate
CVSS v3: 5.3/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Release date: 2026-01-27T09:02:51.165000+00:00

Missing Release of Memory after Effective Lifetime vulnerability in ydb-platform ydb (contrib/libs/yajl modules). This vulnerability is associated with program files yail_tree.C.

This issue affects ydb: through 24.4.4.2.

Statement: This MODERATE impact memory leak in the yajl modules of ydb can lead to a Denial of Service. A remote attacker could exploit this vulnerability by repeatedly triggering memory allocations without proper deallocation, causing resource exhaustion..

Remediation:
CVE: CVE-2026-2042
Component: Nagios Host monitoringwizard Command Injection Remote Code Execution Vulnerability
Release date: 2026-02-12T21:48:19.804000+00:00

Nagios Host monitoringwizard Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Nagios Host. Authentication is required to exploit this vulnerability.

The specific flaw exists within the monitoringwizard module. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-28245.

Statement: Red Hat Product Security has determined that this vulnerability does not affect any currently supported Red Hat product. This assessment may evolve based on further analysis and discovery. For more information about this vulnerability and the products it affects, please see the linked references.

Remediation:
Buffer Over-read in Wireshark
CVE: CVE-2026-3203
Component: wireshark
CWE: CWE-126
Severity: Moderate
CVSS v3: 5.4/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Release date: 2026-02-25T14:36:00.984000+00:00

A flaw was found in the RF4CE Profile dissector in Wireshark. This issue occurs when malformed packets are decoded from a pcap file or the network, causing a buffer over-read, resulting in a denial of service.

Statement: This issue will cause a crash in Wireshark with no other security impact. Also, this flaw can only be exploited when a malformed pcap file is processed. Due to these reasons, this vulnerability has been rated with a moderate severity.

Remediation:
If the RF4CE Profile protocol dissector is not being used, it can be disabled via the "Enabled Protocols" dialog box in the Wireshark GUI application. This will also disable the protocol dissector when using "tshark", the command line tool.

See the links below for instructions to disable a protocol in Wireshark, specifically the "Control Protocol Dissection" section and the "disabled_protos" configuration file option.

https://www.wireshark.org/docs/wsug_html_chunked/ChCustProtocolDissectionSection.html
https://www.wireshark.org/docs/wsug_html_chunked/ChAppFilesConfigurationSection.html
ImageMagick: Arbitrary code execution via a crafted XBM image file
CVE: CVE-2026-23876
Component: ImageMagick
CWE: CWE-787
Severity: Important
CVSS v3: 8.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Release date: 2026-01-20T01:01:38.527000+00:00

A flaw was found in ImageMagick. A heap buffer overflow, a type of memory corruption, in the XBM image decoder (ReadXBMImage) allows a remote attacker to write controlled data beyond the allocated memory buffer when processing a maliciously crafted image file. This can lead to arbitrary code execution, information disclosure, or a denial of service. The vulnerability can be triggered by any operation that reads or identifies an image.

Statement: This vulnerability is rated Important for Red Hat products as it affects ImageMagick, a widely used image manipulation suite. A heap buffer overflow in the XBM image decoder can be triggered by processing a specially crafted image file, potentially leading to arbitrary code execution or denial of service. Exploitation can occur through common image upload and processing pipelines.

Remediation:
To reduce the risk associated with this vulnerability, avoid processing untrusted XBM image files with ImageMagick. Implement strict input validation and sanitization for any image files processed by ImageMagick, especially those originating from external or untrusted sources. Deploying ImageMagick within a sandboxed or containerized environment can further limit the impact of a successful exploit by isolating the process and restricting its access to system resources.
ImageMagick: Out-of-bounds read or write due to integer overflow in DIB coder
CVE: CVE-2026-28693
Component: ImageMagick
CWE: CWE-190
Severity: Important
CVSS v3: 8.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Release date: 2026-03-09T21:42:28.143000+00:00

A flaw was found in ImageMagick, a free and open-source software used for editing and manipulating digital images. An integer overflow vulnerability in the DIB (Device Independent Bitmap) coder component can be exploited by a remote attacker. By processing a specially crafted image file, this flaw may lead to an out-of-bounds read or write, potentially resulting in arbitrary code execution, privilege escalation, information disclosure, or a Denial of Service (DoS).

Statement: This is an IMPORTANT vulnerability in ImageMagick where an integer overflow in the DIB image coder can lead to out-of-bounds read or write operations. This flaw could result in arbitrary code execution or denial of service when processing a specially crafted DIB image. Red Hat Enterprise Linux 6 ELS and 7 ELS are affected by this vulnerability.

Remediation:
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
net: cpsw: Execute ndo_set_rx_mode callback in a work queue
CVE: CVE-2026-23175
Component: kernel
Severity: None
Release date: 2026-02-14T00:00:00+00:00

In the Linux kernel, the following vulnerability has been resolved:

net: cpsw: Execute ndo_set_rx_mode callback in a work queue

Commit 1767bb2d47b7 ("ipv6: mcast: Don't hold RTNL for
IPV6_ADD_MEMBERSHIP and MCAST_JOIN_GROUP.") removed the RTNL lock for
IPV6_ADD_MEMBERSHIP and MCAST_JOIN_GROUP operations. However, this
change triggered the following call trace on my BeagleBone Black board:
  WARNING: net/8021q/vlan_core.c:236 at vlan_for_each+0x120/0x124, CPU#0: rpcbind/481
  RTNL: assertion failed at net/8021q/vlan_core.c (236)
  Modules linked in:
  CPU: 0 UID: 997 PID: 481 Comm: rpcbind Not tainted 6.19.0-rc7-next-20260130-yocto-standard+ #35 PREEMPT
  Hardware name: Generic AM33XX (Flattened Device Tree)
  Call trace:
   unwind_backtrace from show_stack+0x28/0x2c
   show_stack from dump_stack_lvl+0x30/0x38
   dump_stack_lvl from __warn+0xb8/0x11c
   __warn from warn_slowpath_fmt+0x130/0x194
   warn_slowpath_fmt from vlan_for_each+0x120/0x124
   vlan_for_each from cpsw_add_mc_addr+0x54/0x98
   cpsw_add_mc_addr from __hw_addr_ref_sync_dev+0xc4/0xec
   __hw_addr_ref_sync_dev from __dev_mc_add+0x78/0x88
   __dev_mc_add from igmp6_group_added+0x84/0xec
   igmp6_group_added from __ipv6_dev_mc_inc+0x1fc/0x2f0
   __ipv6_dev_mc_inc from __ipv6_sock_mc_join+0x124/0x1b4
   __ipv6_sock_mc_join from do_ipv6_setsockopt+0x84c/0x1168
   do_ipv6_setsockopt from ipv6_setsockopt+0x88/0xc8
   ipv6_setsockopt from do_sock_setsockopt+0xe8/0x19c
   do_sock_setsockopt from __sys_setsockopt+0x84/0xac
   __sys_setsockopt from ret_fast_syscall+0x0/0x54

This trace occurs because vlan_for_each() is called within
cpsw_ndo_set_rx_mode(), which expects the RTNL lock to be held.
Since modifying vlan_for_each() to operate without the RTNL lock is not
straightforward, and because ndo_set_rx_mode() is invoked both with and
without the RTNL lock across different code paths, simply adding
rtnl_lock() in cpsw_ndo_set_rx_mode() is not a viable solution.

To resolve this issue, we opt to execute the actual processing within
a work queue, following the approach used by the icssg-prueth driver.

Please note: To reproduce this issue, I manually reverted the changes to
am335x-bone-common.dtsi from commit c477358e66a3 ("ARM: dts: am335x-bone:
switch to new cpsw switch drv") in order to revert to the legacy cpsw
driver.


Remediation: