Skip to main content

Linux Kernel CVE-2025-38352

HIGH
Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367)
2025-07-22 416baaa9-dc9f-4396-8d5f-8c081fb06d67
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain low-priv local code execution
  2. Delivery
    Arm POSIX CPU timer on task
  3. Exploit
    Force task exit past exit_notify()
  4. Execution
    Race reap against posix_cpu_timer_del()
  5. Persist
    Corrupt kernel timer state
  6. Impact
    Escalate to root

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture TOCTOU prevention
Exploitation Conditions

Exploitation requires local, authenticated low-privileged code execution on the target (CVSS PR:L, AV:L) and a kernel built WITHOUT CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y - with that config enabled the race cannot occur. The attacker must drive an exiting non-autoreaping task past exit_notify() so it runs handle_posix_cpu_timers() from IRQ context, and arrange for the parent or an attached debugger to reap it precisely while a concurrent posix_cpu_timer_del() executes; this timing dependence is the primary limiting factor and makes success probabilistic rather than deterministic despite the AC:L rating. It is not remotely exploitable and requires no user interaction (UI:N), but it does require the ability to run code and manipulate process/timer lifecycle on the host.

Impact

The signals are somewhat contradictory and warrant careful triage. CVSS 3.1 (AV:L/AC:L/PR:L/UI:N, base 7.8) describes a local attack requiring existing low-privilege code execution - not remotely reachable - with high confidentiality, integrity, and availability impact consistent with kernel-level compromise. Against this, EPSS is low at 1.34% (69th percentile), which normally implies limited mass-exploitation likelihood; however, CISA KEV lists this as actively exploited, and a public PoC (chronomaly) exists. The low EPSS despite KEV listing suggests targeted rather than commodity/widespread exploitation, which is typical for local kernel LPE bugs used as one stage of a larger chain (e.g., after a browser or container escape). AC:L in the vector is optimistic for a race condition that depends on precise timing of task exit and reaping; real-world reliability likely varies by workload and kernel build, and the bug is entirely absent on kernels with CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y. Net: a genuine priority for multi-tenant and endpoint systems where untrusted local code runs, but not an internet-facing emergency.

Exploit ScenarioDerived

An attacker who already has low-privileged local code execution (for example, inside a container or via a sandboxed process after an initial compromise) arms a POSIX CPU timer and forces a task into the narrow exit/reap window to win the race between the firing timer and posix_cpu_timer_del(). Exploiting the resulting kernel-state corruption yields privilege escalation to root. A public PoC named chronomaly (https://github.com/farazsth98/chronomaly) demonstrates the technique, and the flaw is listed in CISA KEV as actively exploited.

Act Now Prioritize within 24-48h. Why: In CISA KEV with patch available.
Exploited in the wild (CISA KEV) Patch available 1.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 30, 2026

Local privilege escalation in the Linux kernel's POSIX CPU timers subsystem stems from a time-of-check/time-of-use race between handle_posix_cpu_timers() and posix_cpu_timer_del() when an exiting non-autoreaping task is reaped by its parent or debugger mid-teardown. This condition is confirmed actively exploited (CISA KEV) with publicly available exploit code, and while the CVSS 3.1 base score is 7.8 (local, low-complexity, low-privilege), EPSS estimates a modest 1.34% probability (69th percentile). An attacker with local code execution can trigger the race to corrupt timer state and escalate privileges on kernels built without CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y.

RemediationAI

Patch available per vendor advisory: apply the stable-kernel fix that adds the tsk->exit_state check in run_posix_cpu_timers(), delivered via the git.kernel.org stable commits (2c72fe18cc5f, 2f3daa04a932, 460188bc042a, 764a7a5dfda2, 78a4b8e3795b, c076635b3a42, c29d5318708e, f90fff1e152d) and packaged by distributions. Debian users should upgrade per the LTS announcements at https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html and https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html, then reboot into the patched kernel. As a build-time mitigation where feasible, enabling CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y eliminates the race entirely because exit_task_work() runs before exit_notify() - the trade-off is that this is a kernel rebuild, not a runtime toggle. Where patching is delayed, reduce exposure by limiting untrusted local code execution: restrict shell/container access on multi-tenant hosts and tighten sandboxing, accepting that these are compensating controls that shrink attacker opportunity rather than close the race. Given active exploitation (CISA KEV), prioritize patching on any host that runs untrusted local workloads and consult https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-38352 for CISA due-date guidance.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw lives in the kernel's posix-cpu-timers code, which manages per-process and per-thread CPU-time timers. The root cause is CWE-367 (Time-of-check Time-of-use race condition): when an exiting task that is not self-reaping has already passed exit_notify() and then runs handle_posix_cpu_timers() from IRQ context, the parent or an attached debugger can reap it immediately after unlock_task_sighand(). A concurrent posix_cpu_timer_del() then fails to observe timer->it.cpu.firing != 0 because cpu_timer_task_rcu() and/or lock_task_sighand() fail against the now-reaped task, leaving the timer-deletion path racing against a firing timer. The upstream fix adds a tsk->exit_state check in run_posix_cpu_timers(); the race does not occur when CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, since exit_task_work() runs before exit_notify() (and task_work_add() would fail regardless). CPE data identifies affected products as generic linux:linux_kernel (including 6.16 rc1) and debian:debian_linux 11.0.

Know when Debian Linux gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

Local low-priv trigger (AV:L/PR:L); race timing makes it AC:H not AC:L; successful win yields full kernel compromise (C/I/A:H).

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE 7.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Red Hat 7.8 HIGH

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Added to CISA KEV
Jul 30, 2026 - 07:02 CISA
CVE Published
Jul 22, 2025 - 08:15 cve.org
HIGH 7.8

DescriptionCVE.org

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

posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()

If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand().

If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail.

Add the tsk->exit_state check into run_posix_cpu_timers() to fix this.

This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.

Executive ViewAI

Why It Matters

A Linux kernel privilege escalation vulnerability (CVE-2025-38352) confirmed actively exploited (CISA KEV) allows attackers with low-privilege local access to gain full root control, creating immediate risk for any organization running Linux systems. This enables unauthorized data access and lateral movement for attackers operating from within your network or cloud infrastructure.

Business Impact: Severe
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

Threat Score
4.6/10
Composite threat intelligence
EPSS Score
1.3%
Top 31% exploitable
Prevalence
Ubiquitous
Linux kernel underpies a vast fraction of servers, cloud, and endpoints
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV Yes
Public POC Yes
EPSS 1.3%
Patch available Yes
Active threat Yes
Deciding rule
In CISA KEV with patch available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
Active
System Exposure· derived
Small
Automatable· derived
No
Human Impact
Very High

Priority Score

110
Low Medium High Critical
KEV: +50
EPSS: +1
CVSS: +39
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Affected Products (CPE)CVE.org

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.16:rc1:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
CVE-2021-44228 CRITICAL POC
10.0 Dec 10

Apache Log4j2 contains a critical JNDI injection vulnerability known as 'Log4Shell' that allows unauthenticated remote c

CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2014-6271 CRITICAL POC
9.8 Sep 24

GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which

CVE-2017-7494 CRITICAL POC
9.8 May 30

Samba since version 3.5.0 and before 4.6.4, 4.5.10 and 4.4.14 is vulnerable to remote code execution vulnerability, allo

CVE-2012-0507 CRITICAL POC
9.8 Jun 07

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2022-30333 HIGH POC
7.5 May 09

RARLAB UnRAR before 6.12 on Linux and UNIX allows directory traversal to write to files during an extract (aka unpack) o

CVE-2016-3714 HIGH POC
8.4 May 05

The (1) EPHEMERAL, (2) HTTPS, (3) MVG, (4) MSL, (5) TEXT, (6) SHOW, (7) WIN, and (8) PLT coders in ImageMagick before 6.

CVE-2017-12617 HIGH POC
8.1 Oct 04

When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTT

CVE-2020-1938 CRITICAL POC
9.8 Feb 24

When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Rate

CVE-2018-7602 CRITICAL POC
9.8 Jul 19

A remote code execution vulnerability exists within multiple subsystems of Drupal 7.x and 8.x. Rated critical severity (

Vendor StatusVendor

SUSE

Severity: Important
Product Status
Container suse/hpc/warewulf4-x86_64/sle-hpc-node:15.6.17.8.103 Image SLES15-SP6 Image SLES15-SP6-BYOS Image SLES15-SP6-BYOS-Azure Image SLES15-SP6-BYOS-EC2 Image SLES15-SP6-BYOS-GCE Image SLES15-SP6-CHOST-BYOS Image SLES15-SP6-CHOST-BYOS-Aliyun Image SLES15-SP6-CHOST-BYOS-Azure Image SLES15-SP6-CHOST-BYOS-EC2 Image SLES15-SP6-CHOST-BYOS-GCE Image SLES15-SP6-CHOST-BYOS-GDC Image SLES15-SP6-CHOST-BYOS-SAP-CCloud Image SLES15-SP6-EC2 Image SLES15-SP6-EC2-ECS-HVM Image SLES15-SP6-GCE Image SLES15-SP6-HPC-BYOS Image SLES15-SP6-HPC-BYOS-Azure Image SLES15-SP6-HPC-BYOS-EC2 Image SLES15-SP6-HPC-BYOS-GCE Image SLES15-SP6-HPC-EC2 Image SLES15-SP6-HPC-GCE Image SLES15-SP6-Hardened-BYOS Image SLES15-SP6-Hardened-BYOS-Azure Image SLES15-SP6-Hardened-BYOS-EC2 Image SLES15-SP6-Hardened-BYOS-GCE Image SLES15-SP6-SAP Image SLES15-SP6-SAP-Azure Image SLES15-SP6-SAP-EC2 Image SLES15-SP6-SAP-GCE Image SLES15-SP6-SAPCAL Image SLES15-SP6-SAPCAL-Azure Image SLES15-SP6-SAPCAL-EC2 Image SLES15-SP6-SAPCAL-GCE Affected
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.44 Container suse/sl-micro/6.1/base-os-container:2.2.1-5.27 Affected
Container suse/sl-micro/6.0/kvm-os-container:2.1.3-6.67 Container suse/sl-micro/6.1/kvm-os-container:2.2.1-5.29 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.76 Container suse/sl-micro/6.1/rt-os-container:2.2.1-5.14 Affected
Container suse/sle-micro-rancher/5.2:latest Image SLES15-SP3-Micro-5-2-BYOS-Azure Affected

References

Advisories & patches
PATCH https://git.kernel.org/stable/c/2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff PATCH https://git.kernel.org/stable/c/2f3daa04a9328220de46f0d5c919a6c0073a9f0b PATCH https://git.kernel.org/stable/c/460188bc042a3f40f72d34b9f7fc6ee66b0b757b PATCH https://git.kernel.org/stable/c/764a7a5dfda23f69919441f2eac2a83e7db6e5bb PATCH https://git.kernel.org/stable/c/78a4b8e3795b31dae58762bc091bb0f4f74a2200 PATCH https://git.kernel.org/stable/c/c076635b3a42771ace7d276de8dc3bc76ee2ba1b PATCH https://git.kernel.org/stable/c/c29d5318708e67ac13c1b6fc1007d179fb65b4d7 PATCH https://git.kernel.org/stable/c/f90fff1e152dedf52b932240ebbd670d83330eca ADVISORY https://access.redhat.com/errata/RHSA-2025:15471 ADVISORY https://access.redhat.com/errata/RHSA-2025:15472 ADVISORY https://access.redhat.com/errata/RHSA-2025:15646 ADVISORY https://access.redhat.com/errata/RHSA-2025:15647 ADVISORY https://access.redhat.com/errata/RHSA-2025:15648 ADVISORY https://access.redhat.com/errata/RHSA-2025:15649 ADVISORY https://access.redhat.com/errata/RHSA-2025:15656 ADVISORY https://access.redhat.com/errata/RHSA-2025:15657 ADVISORY https://access.redhat.com/errata/RHSA-2025:15658 ADVISORY https://access.redhat.com/errata/RHSA-2025:15660 ADVISORY https://access.redhat.com/errata/RHSA-2025:15661 ADVISORY https://access.redhat.com/errata/RHSA-2025:15662 ADVISORY https://access.redhat.com/errata/RHSA-2025:15668 ADVISORY https://access.redhat.com/errata/RHSA-2025:15669 ADVISORY https://access.redhat.com/errata/RHSA-2025:15670 ADVISORY https://access.redhat.com/errata/RHSA-2025:15798 ADVISORY https://access.redhat.com/errata/RHSA-2025:15921 ADVISORY https://access.redhat.com/errata/RHSA-2025:15931 ADVISORY https://access.redhat.com/errata/RHSA-2025:15932 ADVISORY https://access.redhat.com/errata/RHSA-2025:15933 ADVISORY https://access.redhat.com/errata/RHSA-2025:16008 ADVISORY https://access.redhat.com/errata/RHSA-2025:16045 ADVISORY https://vuldb.com/vuln/317224 ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:02853/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:02923/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:02969/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:02996/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:02997/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:03011/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:03023/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:03204/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:03283/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:03310/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:03314/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:03344/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:03383/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:03384/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:20577/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:20586/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:20601/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:20602/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:20994/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:20996/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:21074/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:21139/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:21179/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2025:4315/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0170/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0487/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0489/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0515/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0518/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0521/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0526/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0528/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0535/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0539/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0543/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0546/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0548/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0554/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0556/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0560/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:0565/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20309/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20330/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20455/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20456/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20457/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20458/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20459/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20460/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20461/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20462/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20463/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20464/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20465/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20470/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20499/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20500/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20501/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20502/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20503/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20504/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20511/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20512/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20513/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20514/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20515/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20516/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20560/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20635/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20644/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:20645/ REF https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html REF https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html REF https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-38352

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy