Skip to main content

Threats Tagged 'cve-2025-40245'

View all threats tagged with 'cve-2025-40245'. Filter and sort to focus on specific types of threats.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Tag: cve-2025-40245

Threats Tagged 'cve-2025-40245'

Click on any threat for detailed analysis and mitigation recommendations

A high-severity vulnerability (CVE-2025-40214) in the Linux kernel's Unix domain sockets subsystem was resolved by initializing scc_index in unix_add_edge(). This flaw could lead to privilege escalation on Container-Optimized OS nodes, affecting multiple Google Kubernetes Engine (GKE) cluster types except those using GKE Sandbox. Patch versions have been released for various Container-Optimized OS node pools and Ubuntu Linux kernel packages. Bare metal GDC software is not affected. Users are advised to update to the specified patched kernel versions and reboot to apply fixes.

Join the discussion

A vulnerability in the Linux kernel on the nios2 architecture with CONFIG_FLATMEM set could cause kernel-level paging failures and panics due to incorrect memory limit calculations. The issue arises because memblock.current_limit is not properly initialized during boot, potentially allowing max_low_pfn to exceed valid memory ranges. This has been resolved by ensuring memblock.current_limit is correctly set based on available memory limits.

Join the discussion

In the Linux kernel, the following vulnerability has been resolved: nios2: ensure that memblock.current_limit is set when setting pfn limits On nios2, with CONFIG_FLATMEM set, the kernel relies on memblock_get_current_limit() to determine the limits of mem_map, in particular for max_low_pfn. Unfortunately, memblock.current_limit is only default initialized to MEMBLOCK_ALLOC_ANYWHERE at this point of the bootup, potentially leading to situations where max_low_pfn can erroneously exceed the value of max_pfn and, thus, the valid range of available DRAM. This can in turn cause kernel-level paging failures, e.g.: [ 76.900000] Unable to handle kernel paging request at virtual address 20303000 [ 76.900000] ea = c0080890, ra = c000462c, cause = 14 [ 76.900000] Kernel panic - not syncing: Oops [ 76.900000] ---[ end Kernel panic - not syncing: Oops ]--- This patch fixes this by pre-calculating memblock.current_limit based on the upper limits of the available memory ranges via adjust_lowmem_bounds, a simplified version of the equivalent implementation within the arm architecture.

Join the discussion

Showing 1 to 3 of 3 results

Filters:Tag: cve-2025-40245
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses