Search: update-app.top
133 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| Medium | 6.7 | EPSS 0.2% | CVE-2025-9907Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Product Security and Bug Fix Update Medium6.7EPSS 0.2%GCVE DatabaseCVE-2025-9907 Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to individual teams, while automation developers retain the freedom to write tasks that leverage existing knowledge without the overhead. Ansible Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless language. | GCVE Database | ||
| High | 7.8 | EPSS 0.2% | High7.8EPSS 0.2%GCVE DatabaseCVE-2025-40018 Published: 2025-12-02 Updated: 2026-03-25 Reference: CVE-2025-40018 2026-03-25 Update: Added patch versions for Ubuntu nodes with GKE. 2025-12-11 Update: Added patch versions and a severity rating for GDC (VMware). GKE Updated: 2026-03-25 Description Severity The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS nodes: CVE-2025-40018 GKE Standard clusters are impacted. GKE Autopilot clusters in the default configuration are not impacted, but might be vulnerable if you explicitly set the seccomp Unconfined profile or allow CAP_NET_ADMIN . Clusters using GKE Sandbox aren't impacted. What should I do? 2026-03-25 Update : The following versions of GKE are updated with code to fix this vulnerability on Ubuntu. Upgrade your Ubuntu node pools to the following versions or later: 1.35.1-gke.1396000 1.34.4-gke.1047000 1.33.8-gke.1026000 1.32.12-gke.1026000 1.31.14-gke.1336000 1.30.14-gke.1991000 The following minor versions are affected. Upgrade your Container-Optimized OS node pools to one of the following patch versions or later: 1.32.9-gke.1330000 1.29.15-gke.2236000 1.30.14-gke.1525000 1.31.13-gke.1231000 1.34.1-gke.2541000 1.28.15-gke.2966000 1.33.5-gke.1350000 You can apply patch versions from newer release channels if your cluster runs the same minor version in its own release channel. This feature lets you secure your nodes until the patch version becomes the default in your release channel. For details, see Run patch versions from a newer channel . High GDC (VMware) Updated: 2025-12-11 Description Severity The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS nodes: CVE-2025-40018 What should I do? The following versions of GDC (VMware) are updated with code to fix this vulnerability. Upgrade your GDC (VMware) clusters to the following versions or later: 1.31.1100-gke.40 Note: Patch versions and a severity assessment for GDC software for VMware are in progress. We'll update this bulletin with that information when it's available. High GKE on AWS Description Severity The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS nodes: CVE-2025-40018 What should I do? Note: Patch versions and a severity assessment for GKE on AWS are in progress. We'll update this bulletin with that information when it's available. Pending GKE on Azure Description Severity The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS nodes: CVE-2025-40018 What should I do? Note: Patch versions and a severity assessment for GKE on Azure are in progress. We'll update this bulletin with that information when it's available. Pending GDC (bare metal) Description Severity The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS nodes: CVE-2025-40018 What should I do? There is no action required. GDC software for bare metal isn't affected as it does not bundle an operating system in its distribution. None | GCVE Database | ||
| High | 7.3 | EPSS 0.5% | CVE-2025-62229Red Hat Security Advisory: tigervnc security update High7.3EPSS 0.5%GCVE DatabaseCVE-2025-62229 TigerVNC, a suite of VNC servers and clients used for remote desktop access, has multiple security vulnerabilities including use-after-free and value overflow issues in components of the Xorg server (xmayland and xwayland). These vulnerabilities are addressed in a Red Hat security update for Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions. The update fixes three CVEs: CVE-2025-62229, CVE-2025-62230, and CVE-2025-62231. The advisory rates the impact as Important and the severity as high. No CVSS score is provided in the advisory. The update is available and should be applied to affected systems. | GCVE Database | ||
| Medium | 6.7 | EPSS 0.2% | CVE-2025-9909Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.6 Product Security and Bug Fix Update Medium6.7EPSS 0.2%GCVE DatabaseCVE-2025-9909 Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to individual teams, while automation developers retain the freedom to write tasks that leverage existing knowledge without the overhead. Ansible Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless language. | GCVE Database | ||
| High | 7.0 | EPSS 0.1% | CVE-2025-34324Tinexta InfoCert S.p.A GoSign Desktop · Improper Verification of Cryptographic Signature High7.0EPSS 0.1%CVE Database V5CVE-2025-34324 GoSign Desktop versions 2.4.0 and earlier use an unsigned update manifest for distributing application updates. The manifest contains package URLs and SHA-256 hashes but is not digitally signed, so its authenticity relies solely on the underlying TLS channel. In affected versions, TLS certificate validation can be disabled when a proxy is configured, allowing an attacker who can intercept network traffic to supply a malicious update manifest and corresponding package with a matching hash. This can cause the client to download and install a tampered update, resulting in arbitrary code execution with the privileges of the GoSign Desktop user on Windows and macOS, or with elevated privileges on some Linux deployments. A local attacker who can modify proxy settings may also abuse this behavior to escalate privileges by forcing installation of a crafted update. | CVE Database V5 | ||
| Medium | – | EPSS 0.2% | MediumEPSS 0.2%GCVE DatabaseCVE-2025-40184 In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Fix debug checking for np-guests using huge mappings When running with transparent huge pages and CONFIG_NVHE_EL2_DEBUG then the debug checking in assert_host_shared_guest() fails on the launch of an np-guest. This WARN_ON() causes a panic and generates the stack below. In __pkvm_host_relax_perms_guest() the debug checking assumes the mapping is a single page but it may be a block map. Update the checking so that the size is not checked and just assumes the correct size. While we're here make the same fix in __pkvm_host_mkyoung_guest(). Info: # lkvm run -k /share/arch/arm64/boot/Image -m 704 -c 8 --name guest-128 Info: Removed ghost socket file "/.lkvm//guest-128.sock". [ 1406.521757] kvm [141]: nVHE hyp BUG at: arch/arm64/kvm/hyp/nvhe/mem_protect.c:1088! [ 1406.521804] kvm [141]: nVHE call trace: [ 1406.521828] kvm [141]: [<ffff8000811676b4>] __kvm_nvhe_hyp_panic+0xb4/0xe8 [ 1406.521946] kvm [141]: [<ffff80008116d12c>] __kvm_nvhe_assert_host_shared_guest+0xb0/0x10c [ 1406.522049] kvm [141]: [<ffff80008116f068>] __kvm_nvhe___pkvm_host_relax_perms_guest+0x48/0x104 [ 1406.522157] kvm [141]: [<ffff800081169df8>] __kvm_nvhe_handle___pkvm_host_relax_perms_guest+0x64/0x7c [ 1406.522250] kvm [141]: [<ffff800081169f0c>] __kvm_nvhe_handle_trap+0x8c/0x1a8 [ 1406.522333] kvm [141]: [<ffff8000811680fc>] __kvm_nvhe___skip_pauth_save+0x4/0x4 [ 1406.522454] kvm [141]: ---[ end nVHE call trace ]--- [ 1406.522477] kvm [141]: Hyp Offset: 0xfffece8013600000 [ 1406.522554] Kernel panic - not syncing: HYP panic: [ 1406.522554] PS:834003c9 PC:0000b1806db6d170 ESR:00000000f2000800 [ 1406.522554] FAR:ffff8000804be420 HPFAR:0000000000804be0 PAR:0000000000000000 [ 1406.522554] VCPU:0000000000000000 [ 1406.523337] CPU: 3 UID: 0 PID: 141 Comm: kvm-vcpu-0 Not tainted 6.16.0-rc7 #97 PREEMPT [ 1406.523485] Hardware name: FVP Base RevC (DT) [ 1406.523566] Call trace: [ 1406.523629] show_stack+0x18/0x24 (C) [ 1406.523753] dump_stack_lvl+0xd4/0x108 [ 1406.523899] dump_stack+0x18/0x24 [ 1406.524040] panic+0x3d8/0x448 [ 1406.524184] nvhe_hyp_panic_handler+0x10c/0x23c [ 1406.524325] kvm_handle_guest_abort+0x68c/0x109c [ 1406.524500] handle_exit+0x60/0x17c [ 1406.524630] kvm_arch_vcpu_ioctl_run+0x2e0/0x8c0 [ 1406.524794] kvm_vcpu_ioctl+0x1a8/0x9cc [ 1406.524919] __arm64_sys_ioctl+0xac/0x104 [ 1406.525067] invoke_syscall+0x48/0x10c [ 1406.525189] el0_svc_common.constprop.0+0x40/0xe0 [ 1406.525322] do_el0_svc+0x1c/0x28 [ 1406.525441] el0_svc+0x38/0x120 [ 1406.525588] el0t_64_sync_handler+0x10c/0x138 [ 1406.525750] el0t_64_sync+0x1ac/0x1b0 [ 1406.525876] SMP: stopping secondary CPUs [ 1406.525965] Kernel Offset: disabled [ 1406.526032] CPU features: 0x0000,00000080,8e134ca1,9446773f [ 1406.526130] Memory Limit: none [ 1406.959099] ---[ end Kernel panic - not syncing: HYP panic: [ 1406.959099] PS:834003c9 PC:0000b1806db6d170 ESR:00000000f2000800 [ 1406.959099] FAR:ffff8000804be420 HPFAR:0000000000804be0 PAR:0000000000000000 [ 1406.959099] VCPU:0000000000000000 ] EPSS 0.2%Vulnerability | GCVE Database | ||
| High | 8.7 | EPSS 0.6% | CVE-2025-59343Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Product Security and Bug Fix Update High8.7EPSS 0.6%GCVE DatabaseCVE-2025-59343 Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to individual teams, while automation developers retain the freedom to write tasks that leverage existing knowledge without the overhead. Ansible Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless language. Security Fix(es): * python3.11-django: Potential partial directory-traversal via archive.extract() (CVE-2025-59682) * automation-gateway: tar-fs symlink validation bypass (CVE-2025-59343) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Updates and fixes included: Automation Platform * Azure AD authentication now searches more fields to find the username override field specified. If not found it will log a warning message indicating which fields are valid (AAP-53789) * Support TLSv1.3 on server-to-server requests, where previously services which only supported TLSv1.3 would not work (AAP-49456) * Added a step in the subscription wizard that allows the user to configure automation analytics (AAP-55094) * Subscription credentials can no longer be viewed/edited from the system settings page (AAP-55014) * Fixed an issue where the settings displayed "Red Hat" inconsistently in the API and UI (AAP-54277) * Fixed a bug where platform auditors were not able to see Automation Execution and Platform level settings (AAP-53975) * Fixed an issue where some fields were missing the autocomplete = new-password setting (AAP-53934) * Fixed an issue where AAP could not set/create a playbook when using branch override (AAP-52566) * Empty strings are no longer displayed in the extra variables field on the Jobs > Details page (AAP-49448) * Added two new toggle options on the subscription wizard to allow for fetching subscriptions using basic authentication (AAP-47865) * Fixed validation of prompt-on-launch credentials in a workflow job template (AAP-40540) * Fixed an issue for comments in extra vars sections, all comments in YAML are now persisted on create and edit operations for a resource (AAP-37071) * Updated error handling in the Authenticator form to match other forms in the Platform UI (AAP-22928) * automation-gateway has been updated to 2.5.20251022 * automation-gateway-proxy has been updated to 2.5.10-3 for RHEL8 * automation-gateway-proxy has been updated to 2.6.6-4 for RHEL9 * python3.11-django-ansible-base has been updated to 2.5.20251022 Automation controller * Fixed an issue where the ansible.platform collection did not work with the default Red Hat Ansible Automation Platform credential type (AAP-55685) * Fixed an issue in callback receiver and dispatcher crash loop state caused by re-running the installer with modified inventory hostname (AAP-55638) * Added support for Red Hat username and password for the subscription management API (AAP-54976) * Fixes system_administrator role creation race condition which most commonly happened on new openshift deployments resulting in the default instance group not being created (AAP-54964) * Fixed an issue where Grafana notifications couldn't have an empty dashboard ID or panel ID (AAP-54654) * Improved stability on long-running jobs, clusters under heavy load and network flakiness in receptor (AAP-53742) * Fixed Platform Auditor to view controller settings (AAP-53345) * Added missing instruction to set an environment variable in the CLI in order to achieve compatibility with the current release (AAP-37812) * Fixed Platform Auditor to view Metrics API endpoint (AAP-36492) * automation-controller has been updated to 4.6.21 * receptor has been updated to 1.6.0 Automation hub * Fixed an issue where _ui/v2/ user detail displayed the data correctly (AAP-55957) * automation-hub has been updated to 4.10.9 * python3.11-galaxy-ng has been updated to 4.10.9 * python3.11-galaxy-importer has been updated to 0.4.34 Container-based Ansible Automation Platform * Set REDHAT_CANDLEPIN_VERIFY to correct CA pem so that controller can make requests to subscription.rhsm.redhat.com (AAP-55181) * Implemented preflight ansible-core version validation (AAP-54931) * Fixed a bug where Ansible would fail to gather the system's UUID for Linux on Power (AAP-54540) * containerized installer setup has been updated to 2.5-20 RPM-based Ansible Automation Platform * Fixed an issue where setting automationgateway_disable_https=false resulted in install failure (AAP-55475) * Set REDHAT_CANDLEPIN_VERIFY to correct CA pem so that controller can make requests to subscription.rhsm.redhat.com (AAP-55184) * Fixed issue where RESOURCE_KEY SECRET_KEY was not updated when restoring from a different environment (AAP-54944) * Fixed issue where EDA DE credentials fa | GCVE Database | ||
| Medium | 6.5 | EPSS 0.5% | Medium6.5EPSS 0.5%GCVE DatabaseCVE-2025-55191 An update is now available for Red Hat OpenShift GitOps. Bug Fix(es) and Enhancement(s): * GITOPS-7606 (ApplicationSet: Bitbucket SCM/PR generator leaks HTTP connections) * GITOPS-7953 (Default resource exclusions list not updated in ArgoCD CR template) * GITOPS-7955 ([1.18] ArgoCD UI fails when Progressive sync is enabled in AppSet but not controller) | GCVE Database | ||
| High | 7.5 | EPSS 0.4% | High7.5EPSS 0.4%GCVE DatabaseCVE-2025-22874 Red Hat OpenShift GitOps version 1.16.4 includes a security update addressing multiple issues related to command argument handling and security context errors in Redis components. The update fixes problems that occurred after upgrading to version 1.16, including inability to add multiple metrics application labels, Redis HA Proxy pod startup failures due to security context errors, and Redis container failures related to root user execution policies. | GCVE Database | ||
| Critical | 9.8 | EPSS 0.4% | Critical9.8EPSS 0.4%GCVE DatabaseCVE-2025-39948 In the Linux kernel, the following vulnerability has been resolved: ice: fix Rx page leak on multi-buffer frames The ice_put_rx_mbuf() function handles calling ice_put_rx_buf() for each buffer in the current frame. This function was introduced as part of handling multi-buffer XDP support in the ice driver. It works by iterating over the buffers from first_desc up to 1 plus the total number of fragments in the frame, cached from before the XDP program was executed. If the hardware posts a descriptor with a size of 0, the logic used in ice_put_rx_mbuf() breaks. Such descriptors get skipped and don't get added as fragments in ice_add_xdp_frag. Since the buffer isn't counted as a fragment, we do not iterate over it in ice_put_rx_mbuf(), and thus we don't call ice_put_rx_buf(). Because we don't call ice_put_rx_buf(), we don't attempt to re-use the page or free it. This leaves a stale page in the ring, as we don't increment next_to_alloc. The ice_reuse_rx_page() assumes that the next_to_alloc has been incremented properly, and that it always points to a buffer with a NULL page. Since this function doesn't check, it will happily recycle a page over the top of the next_to_alloc buffer, losing track of the old page. Note that this leak only occurs for multi-buffer frames. The ice_put_rx_mbuf() function always handles at least one buffer, so a single-buffer frame will always get handled correctly. It is not clear precisely why the hardware hands us descriptors with a size of 0 sometimes, but it happens somewhat regularly with "jumbo frames" used by 9K MTU. To fix ice_put_rx_mbuf(), we need to make sure to call ice_put_rx_buf() on all buffers between first_desc and next_to_clean. Borrow the logic of a similar function in i40e used for this same purpose. Use the same logic also in ice_get_pgcnts(). Instead of iterating over just the number of fragments, use a loop which iterates until the current index reaches to the next_to_clean element just past the current frame. Unlike i40e, the ice_put_rx_mbuf() function does call ice_put_rx_buf() on the last buffer of the frame indicating the end of packet. For non-linear (multi-buffer) frames, we need to take care when adjusting the pagecnt_bias. An XDP program might release fragments from the tail of the frame, in which case that fragment page is already released. Only update the pagecnt_bias for the first descriptor and fragments still remaining post-XDP program. Take care to only access the shared info for fragmented buffers, as this avoids a significant cache miss. The xdp_xmit value only needs to be updated if an XDP program is run, and only once per packet. Drop the xdp_xmit pointer argument from ice_put_rx_mbuf(). Instead, set xdp_xmit in the ice_clean_rx_irq() function directly. This avoids needing to pass the argument and avoids an extra bit-wise OR for each buffer in the frame. Move the increment of the ntc local variable to ensure its updated *before* all calls to ice_get_pgcnts() or ice_put_rx_mbuf(), as the loop logic requires the index of the element just after the current frame. Now that we use an index pointer in the ring to identify the packet, we no longer need to track or cache the number of fragments in the rx_ring. | GCVE Database | ||
| High | 7.1 | EPSS 0.2% | CVE-2025-39901Linux kernel · i40e: remove read access to debugfs files High7.1EPSS 0.2%GCVE DatabaseCVE-2025-39901 In the Linux kernel, the following vulnerability has been resolved: i40e: remove read access to debugfs files The 'command' and 'netdev_ops' debugfs files are a legacy debugging interface supported by the i40e driver since its early days by commit 02e9c290814c ("i40e: debugfs interface"). Both of these debugfs files provide a read handler which is mostly useless, and which is implemented with questionable logic. They both use a static 256 byte buffer which is initialized to the empty string. In the case of the 'command' file this buffer is literally never used and simply wastes space. In the case of the 'netdev_ops' file, the last command written is saved here. On read, the files contents are presented as the name of the device followed by a colon and then the contents of their respective static buffer. For 'command' this will always be "<device>: ". For 'netdev_ops', this will be "<device>: <last command written>". But note the buffer is shared between all devices operated by this module. At best, it is mostly meaningless information, and at worse it could be accessed simultaneously as there doesn't appear to be any locking mechanism. We have also recently received multiple reports for both read functions about their use of snprintf and potential overflow that could result in reading arbitrary kernel memory. For the 'command' file, this is definitely impossible, since the static buffer is always zero and never written to. For the 'netdev_ops' file, it does appear to be possible, if the user carefully crafts the command input, it will be copied into the buffer, which could be large enough to cause snprintf to truncate, which then causes the copy_to_user to read beyond the length of the buffer allocated by kzalloc. A minimal fix would be to replace snprintf() with scnprintf() which would cap the return to the number of bytes written, preventing an overflow. A more involved fix would be to drop the mostly useless static buffers, saving 512 bytes and modifying the read functions to stop needing those as input. Instead, lets just completely drop the read access to these files. These are debug interfaces exposed as part of debugfs, and I don't believe that dropping read access will break any script, as the provided output is pretty useless. You can find the netdev name through other more standard interfaces, and the 'netdev_ops' interface can easily result in garbage if you issue simultaneous writes to multiple devices at once. In order to properly remove the i40e_dbg_netdev_ops_buf, we need to refactor its write function to avoid using the static buffer. Instead, use the same logic as the i40e_dbg_command_write, with an allocated buffer. Update the code to use this instead of the static buffer, and ensure we free the buffer on exit. This fixes simultaneous writes to 'netdev_ops' on multiple devices, and allows us to remove the now unused static buffer along with removing the read access. | GCVE Database | ||
| Medium | 4.0 | EPSS 0.8% | CVE-2025-48432Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Product Security and Bug Fix Update Medium4.0EPSS 0.8%GCVE DatabaseCVE-2025-48432 Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to individual teams, while automation developers retain the freedom to write tasks that leverage existing knowledge without the overhead. Ansible Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless language. Security Fix(es): * automation-controller: Django SQL injection in FilteredRelation column aliases (CVE-2025-57833) * automation-controller: Django Path Injection Vulnerability (CVE-2025-48432) * python3.11-django: Django SQL injection in FilteredRelation column aliases (CVE-2025-57833) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Updates and fixes included: Automation Platform * Increased gateway control plane authorization performance to reduce or eliminate sporadic request errors (503, 504, 403) (AAP-53468) * Fixed a bug where the gateway does not generate the necessary metadata for the UI to render "Settings" > "Platform Gateway" when the accessing user is an auditor rather than an admin (AAP-53279) * If the GRPC server can not connect to the database it will now return a 503 to envoy instead of a 403 (AAP-51931) * Altered the help text for the setting ALLOW_OAUTH2_FOR_EXTERNAL_USERS (AAP-51886) * Fixed improperly formatted error message in SAML authenticator when passing invalid security settings. The error will now properly show the invalid fields and will also indicate what valid field values are (AAP-51705) * Improved debug logging of authenticator map processing, reasoning and results for clarity (AAP-51639) * Fixed an issue with authenticator maps not properly evaluating attribute 'in' conditions (AAP-51638) * When logging in with SAML authentication, user's groups will be correctly read from configured attribute instead of expecting groups to always be in "Group" attribute (AAP-51503) * Added scrolling to multiselect dialogs to make pagination visible for users (AAP-52209) * Fixed an issue that did not allow a user to save Schedule for Workflow job template when Limit has Prompt on Launch was enabled (AAP-49794) * automation-gateway has been updated to 2.5.20250924 * python3.11-django-ansible-base has been updated to 2.5.20250924 Automation controller * Galaxy credentials can now be created and edited without the need to specify an organization (AAP-52197) * Fixed a path injection vulnerability in Django so that internal HTTP response logging escapes request.path and remote attackers can't manipulate log output via crafted URLs (AAP-51443) * The export command works through the controller collection or with awxkit along when the correct environment variable is provided (AAP-49452) * Fixed double escaped quotes in api/v2/jobs/{id}/stdout/?format=txt (AAP-49077) * The export module in the collection now honors the CONTROLLER_OPTIONAL_API_URLPATTERN_PREFIX environment variable, fixing a bug where exports did not work on deployments using the platform gateway (AAP-39265) * automation-controller has been updated to 4.6.20 Automation hub * Added the GALAXY_API_SPEC_REQUIRE_AUTHENTICATION setting (defaults to false), which restricts access to the OpenAPI specification to authenticated users only (AAP-53578) * automation-hub has been updated to 4.10.8 * python3.11-galaxy-ng has been updated to 4.10.8 Container-based Ansible Automation Platform * Disable IPv6 binding on PostgreSQL and Redis services when IPv6 is disabled on the host (AAP-53546) * Fixed the restore and implemented a migration for the controller resource secret key value (AAP-53535) * Uploading ansible collections to Private Automation Hub isn't limited by the API pagination anymore (AAP-53526) * Execute the create_initial_data EDA command during restore (AAP-53382) * Fix an issue with the Private Automation Hub task name using quotes (AAP-53307) * Fixed a path issue for custom_ca_cert when checking postgres connection and version during preflight (AAP-53213) * Fix PostgreSQL configuration directory creation when TLS is disabled (AAP-52569) * X-Forwarded-For and Real-Ip headers are now added to the Nginx logs (AAP-52562) * containerized installer setup has been updated to 2.5-19 RPM-based Ansible Automation Platform * Fixed an issue where redis_mode=standalone and the Redis group were defined at the same time (AAP-53560) * Fixed an issue with EDA restores where database credentials were not updated for event stream (AAP-53529) * Fixed an issue where redis node list could not be created on EDA/gateway nodes which were not part of the redis group (AAP-53528) * Fixed an issue where backup was failing when the deployment had more than 1 EDA node without eda_node_type defined (AAP-528 | GCVE Database | ||
| Medium | 5.5 | EPSS 0.1% | Medium5.5EPSS 0.1%GCVE DatabaseCVE-2025-39844 In the Linux kernel, the following vulnerability has been resolved: mm: move page table sync declarations to linux/pgtable.h During our internal testing, we started observing intermittent boot failures when the machine uses 4-level paging and has a large amount of persistent memory: BUG: unable to handle page fault for address: ffffe70000000034 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI RIP: 0010:__init_single_page+0x9/0x6d Call Trace: <TASK> __init_zone_device_page+0x17/0x5d memmap_init_zone_device+0x154/0x1bb pagemap_range+0x2e0/0x40f memremap_pages+0x10b/0x2f0 devm_memremap_pages+0x1e/0x60 dev_dax_probe+0xce/0x2ec [device_dax] dax_bus_probe+0x6d/0xc9 [... snip ...] </TASK> It turns out that the kernel panics while initializing vmemmap (struct page array) when the vmemmap region spans two PGD entries, because the new PGD entry is only installed in init_mm.pgd, but not in the page tables of other tasks. And looking at __populate_section_memmap(): if (vmemmap_can_optimize(altmap, pgmap)) // does not sync top level page tables r = vmemmap_populate_compound_pages(pfn, start, end, nid, pgmap); else // sync top level page tables in x86 r = vmemmap_populate(start, end, nid, altmap); In the normal path, vmemmap_populate() in arch/x86/mm/init_64.c synchronizes the top level page table (See commit 9b861528a801 ("x86-64, mem: Update all PGDs for direct mapping and vmemmap mapping changes")) so that all tasks in the system can see the new vmemmap area. However, when vmemmap_can_optimize() returns true, the optimized path skips synchronization of top-level page tables. This is because vmemmap_populate_compound_pages() is implemented in core MM code, which does not handle synchronization of the top-level page tables. Instead, the core MM has historically relied on each architecture to perform this synchronization manually. We're not the first party to encounter a crash caused by not-sync'd top level page tables: earlier this year, Gwan-gyeong Mun attempted to address the issue [1] [2] after hitting a kernel panic when x86 code accessed the vmemmap area before the corresponding top-level entries were synced. At that time, the issue was believed to be triggered only when struct page was enlarged for debugging purposes, and the patch did not get further updates. It turns out that current approach of relying on each arch to handle the page table sync manually is fragile because 1) it's easy to forget to sync the top level page table, and 2) it's also easy to overlook that the kernel should not access the vmemmap and direct mapping areas before the sync. # The solution: Make page table sync more code robust and harder to miss To address this, Dave Hansen suggested [3] [4] introducing {pgd,p4d}_populate_kernel() for updating kernel portion of the page tables and allow each architecture to explicitly perform synchronization when installing top-level entries. With this approach, we no longer need to worry about missing the sync step, reducing the risk of future regressions. The new interface reuses existing ARCH_PAGE_TABLE_SYNC_MASK, PGTBL_P*D_MODIFIED and arch_sync_kernel_mappings() facility used by vmalloc and ioremap to synchronize page tables. pgd_populate_kernel() looks like this: static inline void pgd_populate_kernel(unsigned long addr, pgd_t *pgd, p4d_t *p4d) { pgd_populate(&init_mm, pgd, p4d); if (ARCH_PAGE_TABLE_SYNC_MASK & PGTBL_PGD_MODIFIED) arch_sync_kernel_mappings(addr, addr); } It is worth noting that vmalloc() and apply_to_range() carefully synchronizes page tables by calling p*d_alloc_track() and arch_sync_kernel_mappings(), and thus they are not affected by ---truncated--- EPSS 0.1%Vulnerability | GCVE Database | ||
| Medium | – | EPSS 0.2% | MediumEPSS 0.2%GCVE DatabaseCVE-2024-13484 An update is now available for Red Hat OpenShift GitOps. Security Fix(es): * openshift-gitops-operator-container: Namespace Isolation Break [gitops-1.16](CVE-2024-13484) Bug Fix(es): * Gitops operator is not accepting regular expression in sourceNamespaces - Application in non-controlplane namespaces (GITOPS-6675) * gitops-plugin Pods should comply with the Pod Security restricted policy (GITOPS-6777) * Missing ArgoCD commit ID in UI (GITOPS-6896) | GCVE Database | ||
| High | 7.4 | EPSS 13% | High7.4EPSS 13%GCVE DatabaseCVE-2025-3155 A security vulnerability identified as CVE-2025-3155 affects the Yelp help browser for the GNOME desktop on Red Hat Enterprise Linux 8. The flaw allows arbitrary file read, potentially exposing sensitive information. Red Hat has issued an important security update addressing this issue in Yelp and yelp-xsl packages. The update is available for multiple Red Hat Enterprise Linux 8 variants and related products. Users are advised to apply the update as detailed in the Red Hat advisory. | GCVE Database |
Page 8 of 10 · 5 duplicate CVE records merged