Skip to main content

Threats Tagged 'cve-2025-40242'

View all threats tagged with 'cve-2025-40242'. 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-40242

Threats Tagged 'cve-2025-40242'

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 high-severity race condition vulnerability in the Linux kernel's gfs2 filesystem was resolved. The issue occurs in the gdlm_put_lock() function where a small timing window allows the DFL_UNMOUNT flag to be set while the lockspace has not yet been released. During this window, calls to gdlm_ast() and gdlm_bast() may dereference freed glock objects, leading to potential kernel memory corruption. The fix ensures that glock objects are only freed after the lockspace has been fully released.

Join the discussion

In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix unlikely race in gdlm_put_lock In gdlm_put_lock(), there is a small window of time in which the DFL_UNMOUNT flag has been set but the lockspace hasn't been released, yet. In that window, dlm may still call gdlm_ast() and gdlm_bast(). To prevent it from dereferencing freed glock objects, only free the glock if the lockspace has actually been released.

Join the discussion

Showing 1 to 3 of 3 results

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

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses