huzaifas-sidhpurwala/RedHat-security-VeX huggingface dataset:
padata: Fix pd UAF once and for all
CVE: CVE-2025-38584
Component: kernel
CWE: CWE-362
Severity: Moderate
CVSS v3: 4.7/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Release date: 2025-08-19T00:00:00+00:00

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

padata: Fix pd UAF once and for all

There is a race condition/UAF in padata_reorder that goes back
to the initial commit.  A reference count is taken at the start
of the process in padata_do_parallel, and released at the end in
padata_serial_worker.

This reference count is (and only is) required for padata_replace
to function correctly.  If padata_replace is never called then
there is no issue.

In the function padata_reorder which serves as the core of padata,
as soon as padata is added to queue->serial.list, and the associated
spin lock released, that padata may be processed and the reference
count on pd would go away.

Fix this by getting the next padata before the squeue->serial lock
is released.

In order to make this possible, simplify padata_reorder by only
calling it once the next padata arrives.

Statement: The issue requires local access and the ability to trigger cachestat against shmem in specific race conditions, so Privileges Required = Low for the CVSS. Because of the high timing sensitivity, Attack Complexity = High. The impact is limited to Availability (A:H) since the bug can cause kernel crashes or DoS only.

Remediation:
CVE: CVE-2025-2773
Component: BEC Technologies Multiple Routers sys ping Command Injection Remote Code Execution Vulnerability
Release date: 2025-03-25T23:23:57.643000+00:00

BEC Technologies Multiple Routers sys ping Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of BEC Technologies Multiple Routers. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed.

The specific flaw exists within the management interface, which listens on TCP port 22 by default. 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 device. Was ZDI-CAN-25903.

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:
Heap Buffer Overflow in FFmpeg avformat
CVE: CVE-2025-22920
Component: ffmpeg
CVSS v3: 6.4/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Release date: 2025-02-18T00:00:00+00:00

A flaw was found in FFmpeg. This vulnerability allows attackers to trigger memory corruption via supplying a crafted media file in avformat when processing tile grid group streams, leading to a Denial of Service (DoS).

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:
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.
Redis Hyperloglog Out-of-Bounds Write Vulnerability
CVE: CVE-2025-32023
Component: redis
CWE: CWE-787
Severity: Important
CVSS v3: 9.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Release date: 2025-07-07T15:22:19.155000+00:00

A flaw was found in Redis. This flaw allows an authenticated user to trigger an integer overflow by sending a specially crafted string, resulting in a stack or heap out-of-bounds write during hyperloglog operations. This issue potentially results in remote code execution.

Statement: This flaw can only be exploited by an authenticated attacker when the Redis server has hyperloglog operations implemented, limiting the impact of this issue.

Remediation:
Prevent users, specially unprivileged or untrusted users, to execute hyperloglog operations by using ACL to restrict hyperloglog commands.
Out of bounds read in Media
CVE: CVE-2025-1919
Component: chromium-browser
CVSS v3: 6.4/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Release date: 2025-03-05T03:48:36.844000+00:00

Out of bounds read in Media in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: Medium)

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:
Kibana: Origin Validation Error leads to Server-Side Request Forgery
CVE: CVE-2025-37734
Component: kibana
CWE: CWE-346
Severity: Moderate
CVSS v3: 4.5/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Release date: 2025-11-12T09:57:22.782000+00:00

A flaw was found in Kibana. This vulnerability allows Server-Side Request Forgery via a forged Origin HTTP header.

Statement: This vulnerability doesn't affected any supported Red Hat product as this vulnerability affects Kibana through the following versions:

    8.12.0 up to and including 8.19.6
    9.1.0 up to and including 9.1.6
    9.2.0

While the Kibana version shipped with OpenShift Logging 5.8 is Kibana-6.8.1

Remediation:
ParsePKCS1PrivateKey panic with partial keys in crypto/x509
CVE: CVE-2025-22865
Component: crypto/x509
CWE: CWE-228
Severity: Important
CVSS v3: 7.5/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Release date: 2025-01-28T01:03:25.121000+00:00

A flaw was found in the crypto/x509 golang library. When using ParsePKCS1PrivateKey to parse an RSA key missing the CRT values, causes a panic when verifying the key is well formed.

Statement: This vulnerability affects only the Go 1.24 release candidates. Red Hat products do not utilize Go 1.24, except Red Hat Ceph Storage 8 which includes a Grafana container that uses Go 1.24 and is therefore affected by this issue.

Remediation:
Before applying this update, make sure all previously released errata relevant to your system have been applied.

For details on how to apply this update, refer to:

https://access.redhat.com/articles/2789521

For supported configurations, refer to:

https://access.redhat.com/articles/1548993
Before applying this update, make sure all previously released errata relevant to your system have been applied.

For details on how to apply this update, refer to:

https://access.redhat.com/articles/2789521

For supported configurations, refer to:

https://access.redhat.com/articles/1548993
scsi: sg: Do not sleep in atomic context
CVE: CVE-2025-40259
Component: kernel
Severity: Moderate
CVSS v3: 7.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Release date: 2025-12-04T00:00:00+00:00

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

scsi: sg: Do not sleep in atomic context

sg_finish_rem_req() calls blk_rq_unmap_user(). The latter function may
sleep. Hence, call sg_finish_rem_req() with interrupts enabled instead
of disabled.


Remediation:
CVE: CVE-2025-14404
Component: PDFsam Enhanced XLS File Insufficient UI Warning Remote Code Execution Vulnerability
Release date: 2025-12-11T20:58:48.004000+00:00

PDFsam Enhanced XLS File Insufficient UI Warning Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of PDFsam Enhanced. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the processing of XLS files. The issue results from allowing the execution of dangerous script without user warning. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-27498.

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:
net: usb: rtl8150: fix memory leak on usb_submit_urb() failure
CVE: CVE-2025-71154
Component: kernel
CWE: CWE-401
Severity: Low
CVSS v3: 3.9/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Release date: 2025-01-01T00:00:00+00:00

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

net: usb: rtl8150: fix memory leak on usb_submit_urb() failure

In async_set_registers(), when usb_submit_urb() fails, the allocated
  async_req structure and URB are not freed, causing a memory leak.

  The completion callback async_set_reg_cb() is responsible for freeing
  these allocations, but it is only called after the URB is successfully
  submitted and completes (successfully or with error). If submission
  fails, the callback never runs and the memory is leaked.

  Fix this by freeing both the URB and the request structure in the error
  path when usb_submit_urb() fails.

Statement: The driver leaks memory when usb_submit_urb() fails because the cleanup normally performed by the completion callback never runs on submission errors. Repeated failures can accumulate leaked async_req and URB allocations, impacting system availability.

Remediation:
NULL pointer dereference in wasm::Function::getLocalType() when processing a malformed WebAssembly binary
CVE: CVE-2025-14957
Component: binaryen
CVSS v3: 5.6/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Release date: 2025-12-19T17:02:16.843000+00:00

A flaw was found in Binaryen. A NULL pointer dereference can be triggered in the wasm::Function::getLocalType function when processing a malformed WebAssembly binary, resulting in a denial of service.

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:
Linux kernel: Denial of Service due to null pointer dereference in perf/x86 PEBS processing
CVE: CVE-2025-68375
Component: kernel
CWE: CWE-476
Severity: Low
CVSS v3: 5.6/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Release date: 2025-12-24T00:00:00+00:00

A flaw was found in the Linux kernel's perf/x86 component. A local user can exploit a race condition during the processing of Performance Event-Based Sampling (PEBS) records. This occurs when an interrupt throttle stops event processing while draining PEBS records, leading to a null pointer dereference. The consequence is a system crash, resulting in a Denial of Service (DoS).


Remediation:
bpf: Do not let BPF test infra emit invalid GSO types to stack
CVE: CVE-2025-68725
Component: kernel
Severity: Low
CVSS v3: 5.6/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Release date: 2025-12-24T00:00:00+00:00

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

bpf: Do not let BPF test infra emit invalid GSO types to stack

Yinhao et al. reported that their fuzzer tool was able to trigger a
skb_warn_bad_offload() from netif_skb_features() -> gso_features_check().
When a BPF program - triggered via BPF test infra - pushes the packet
to the loopback device via bpf_clone_redirect() then mentioned offload
warning can be seen. GSO-related features are then rightfully disabled.

We get into this situation due to convert___skb_to_skb() setting
gso_segs and gso_size but not gso_type. Technically, it makes sense
that this warning triggers since the GSO properties are malformed due
to the gso_type. Potentially, the gso_type could be marked non-trustworthy
through setting it at least to SKB_GSO_DODGY without any other specific
assumptions, but that also feels wrong given we should not go further
into the GSO engine in the first place.

The checks were added in 121d57af308d ("gso: validate gso_type in GSO
handlers") because there were malicious (syzbot) senders that combine
a protocol with a non-matching gso_type. If we would want to drop such
packets, gso_features_check() currently only returns feature flags via
netif_skb_features(), so one location for potentially dropping such skbs
could be validate_xmit_unreadable_skb(), but then otoh it would be
an additional check in the fast-path for a very corner case. Given
bpf_clone_redirect() is the only place where BPF test infra could emit
such packets, lets reject them right there.


Remediation:
i2c: rtl9300: Fix out-of-bounds bug in rtl9300_i2c_smbus_xfer
CVE: CVE-2025-39680
Component: kernel
Severity: None
Release date: 2025-09-05T00:00:00+00:00

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

i2c: rtl9300: Fix out-of-bounds bug in rtl9300_i2c_smbus_xfer

The data->block[0] variable comes from user. Without proper check,
the variable may be very large to cause an out-of-bounds bug.

Fix this bug by checking the value of data->block[0] first.

1. commit 39244cc75482 ("i2c: ismt: Fix an out-of-bounds bug in
   ismt_access()")
2. commit 92fbb6d1296f ("i2c: xgene-slimpro: Fix out-of-bounds bug in
   xgene_slimpro_i2c_xfer()")


Remediation:
iavf: Implement settime64 with -EOPNOTSUPP
CVE: CVE-2025-68752
Component: kernel
CWE: CWE-476
Severity: Moderate
CVSS v3: 5.6/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Release date: 2025-01-01T00:00:00+00:00

A NULL pointer dereference vulnerability was found in the Intel Adaptive Virtual Function (iavf) network driver in the Linux kernel. The driver registers a PTP clock device but does not implement the settime64() callback. When ptp_clock_settime() is called, it assumes the callback exists and dereferences a NULL function pointer, causing a kernel crash.

Statement: This vulnerability requires local access and the ability to interact with PTP clock devices. Exploitation leads to a kernel panic but does not allow code execution or data compromise. Systems using iavf virtual network adapters in virtualized environments with PTP enabled are affected.

Remediation:
To mitigate this issue, prevent the iavf module from being loaded if Intel Adaptive Virtual Function network devices are not required. See https://access.redhat.com/solutions/41278 for instructions on how to blacklist a kernel module.
iommu: disable SVA when CONFIG_X86 is set
CVE: CVE-2025-71089
Component: kernel
CWE: CWE-820
Severity: Moderate
CVSS v3: 7.9/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Release date: 2025-01-01T00:00:00+00:00

A security vulnerability was found in the Linux kernel's IOMMU Shared Virtual Addressing (SVA) implementation on x86 architecture. When SVA is enabled, the IOMMU caches kernel page table entries. Since the kernel lacks a mechanism to notify the IOMMU when kernel page table pages are freed and reallocated, the IOMMU can retain stale entries pointing to reused memory. This can lead to use-after-free or write-after-free conditions, potentially enabling arbitrary physical memory DMA access or privilege escalation.

Statement: This is a significant security vulnerability affecting x86 systems with IOMMU SVA support enabled. While SVA contexts are unprivileged and cannot directly access kernel mappings, the IOMMU still walks and caches intermediate kernel page table entries. An attacker could potentially exploit the stale cache entries to gain arbitrary DMA access or escalate privileges. The fix disables SVA on x86 until proper cache invalidation mechanisms are implemented.

Remediation:
Insufficient validation of bracketed IPv6 hostnames in net/url
CVE: CVE-2025-47912
Component: net/url
CWE: CWE-1286
Severity: Moderate
CVSS v3: 5.3/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Release date: 2025-10-29T22:10:13.435000+00:00

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.


Remediation:
code execution when processing a malicious Perceiver model file
CVE: CVE-2025-14920
Component: transformers
CWE: CWE-502
Severity: Important
CVSS v3: 8.7/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Release date: 2025-12-23T21:04:36.809000+00:00

A flaw was found in the Hugging Face Transformers library. The parsing of model files fails to validate user-supplied data, causing a deserialization of untrusted data. An attacker can exploit this issue by providing a malicious Perceiver model or convincing a user to visit a malicious page, resulting in arbitrary code execution in the context of the current process.

Statement: To exploit this issue, an attacker must convince a user to process a specially crafted Perceiver model file or visiting a malicious page, limiting the possibility of exploitation. Additionally, model files are not typically processed by users with administrative privileges, limiting the potential for a full system compromise. Due to these reasons, this vulnerability has been rated with an important severity.

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/
To mitigate this issue, users should avoid processing Perceiver model files from untrusted or unverified sources. Ensure that all Perceiver model files processed by the Hugging Face Transformers library originate from trusted repositories or have been verified for integrity. If that is not possible, consider processing untrusted models within an isolated sandbox environment.
net: sxgbe: fix potential NULL dereference in sxgbe_rx()
CVE: CVE-2025-68302
Component: kernel
Severity: Moderate
Release date: 2025-12-16T00:00:00+00:00

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

net: sxgbe: fix potential NULL dereference in sxgbe_rx()

Currently, when skb is null, the driver prints an error and then
dereferences skb on the next line.

To fix this, let's add a 'break' after the error message to switch
to sxgbe_rx_refill(), which is similar to the approach taken by the
other drivers in this particular case, e.g. calxeda with xgmac_rx().

Found during a code review.


Remediation:
ext4: fix string copying in parse_apply_sb_mount_options()
CVE: CVE-2025-71123
Component: kernel
CWE: CWE-170
Severity: Low
CVSS v3: 3.4/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Release date: 2025-01-01T00:00:00+00:00

A buffer overflow warning was found in the Linux kernel's ext4 filesystem. In parse_apply_sb_mount_options(), strscpy_pad() is incorrectly used to copy a potentially non-NUL-terminated string (s_mount_opts from superblock) into a NUL-terminated buffer. When the source string lacks NUL termination, FORTIFY_SOURCE detects a buffer overflow as strnlen reads 65 bytes from a 64-byte buffer.

Statement: This vulnerability was discovered by syzkaller and affects ext4 filesystem mount operations when the superblock contains improperly formatted mount options. The FORTIFY_SOURCE mechanism detects and reports the overflow, generating a kernel warning. The issue can be triggered by mounting a specially crafted ext4 filesystem image.

Remediation:
From CVEorg collector
CVE: CVE-2025-24495
Component: microcode_ctl
CWE: CWE-1419
Severity: Moderate
CVSS v3: 5.4/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
Release date: 2025-05-13T21:02:51.390000+00:00

A flaw was found in the Branch Prediction Unit (BPU) of Intel's Lion Core CPUs that make it possible for an attacker to bypass Indirect Branch Predictor Barrier (IBPB) protections. By employing branch predictor training techniques as described in the "Training Solo" publication, an attacker with local privileges could use this bypass to exfiltrate sensitive data from an affected system, including from host hypervisors or neighboring guests in virtualized environments.

Statement: This vulnerability was disclosed as part of the "Training Solo" report. Training Solo is a technique similar to Spectre-v2 which bypasses extant protections like IBPB or IBRS. While the technique primarily bypasses those protections by performing branch predictor training in a privileged domain, CVE-2025-24495 specifically relates to a hardware flaw in Intel's Lion Core CPUs. Intel has released a microcode update to address this flaw.

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. As this is a bypass of previous mitigations for existing hardware flaws, we do not expect that mitigations specifically for this issue will be available.
wifi: ath12k: Avoid memory leak while enabling statistics
CVE: CVE-2025-37743
Component: kernel
CWE: CWE-401
Severity: Low
CVSS v3: 5.6/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Release date: 2025-05-01T00:00:00+00:00

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

wifi: ath12k: Avoid memory leak while enabling statistics

Driver uses monitor destination rings for extended statistics mode and
standalone monitor mode. In extended statistics mode, TLVs are parsed from
the buffer received from the monitor destination ring and assigned to the
ppdu_info structure to update per-packet statistics. In standalone monitor
mode, along with per-packet statistics, the packet data (payload) is
captured, and the driver updates per MSDU to mac80211.

When the AP interface is enabled, only extended statistics mode is
activated. As part of enabling monitor rings for collecting statistics,
the driver subscribes to HAL_RX_MPDU_START TLV in the filter
configuration. This TLV is received from the monitor destination ring, and
kzalloc for the mon_mpdu object occurs, which is not freed, leading to a
memory leak. The kzalloc for the mon_mpdu object is only required while
enabling the standalone monitor interface. This causes a memory leak while
enabling extended statistics mode in the driver.

Fix this memory leak by removing the kzalloc for the mon_mpdu object in
the HAL_RX_MPDU_START TLV handling. Additionally, remove the standalone
monitor mode handlings in the HAL_MON_BUF_ADDR and HAL_RX_MSDU_END TLVs.
These TLV tags will be handled properly when enabling standalone monitor
mode in the future.

Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1
Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3


Remediation:
drm/v3d: Ensure job pointer is set to NULL after job completion
CVE: CVE-2025-21697
Component: kernel
CWE: CWE-476
Severity: Moderate
CVSS v3: 5.6/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Release date: 2025-02-12T00:00:00+00:00

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

drm/v3d: Ensure job pointer is set to NULL after job completion

After a job completes, the corresponding pointer in the device must
be set to NULL. Failing to do so triggers a warning when unloading
the driver, as it appears the job is still active. To prevent this,
assign the job pointer to NULL after completing the job, indicating
the job has finished.


Remediation: