CVE-2025-68376
NoneCVSS
—
EPSS
0.2%
Published
Dec 24, 2025
CISA due date
—
Cloudanix analysis
A flaw in the Linux kernel's hardware tracing feature can cause crashes or allow attackers to interfere with system memory if they can change certain debug settings.
- Exploitation
- Local Privilege
- Attacker needs
- Local User
- Complexity
- Moderate
- Impact
- Privilege Gain
- Component
- OS kernel
- Class
- Use After Free
- Remediation
- Patch
- Effort
- Medium
- Patch risk
- Low
What it actually does
Use-after-free occurs in coresight ETR when operating in CS_MODE_SYSFS: changing buffer size allocates new memory (buf_new), updates sysfs_buf to it, and frees the prior buffer (buf_old), yet the active etr_buf pointer remains referencing the freed buf_old.
Why it matters to the business
Systems using affected Linux kernels or Chainguard kuma packages may experience kernel instability, crashes, or potential code execution when coresight ETR tracing is reconfigured via sysfs, increasing operational risk for embedded, automotive, or debug-enabled deployments.
How an attack unfolds
An attacker with access to the coresight sysfs interface enables ETR in CS_MODE_SYSFS, alters the buffer size to trigger allocation of a new buffer, then continues using the now-freed original buffer through the stale etr_buf reference, leading to memory corruption.
How to fix it
Update to fixed kernel commit 70acbc9c77686b7a521af6d7a543dcd9c324cf07 or later; for Chainguard packages upgrade kuma-2.6, kuma-cni-2.6, kuma-cp-2.6, kuma-dp-2.6 and related components to version 2.6.15-r4 or newer.
How to confirm the fix worked
Verify the running kernel contains commit 70acbc9c77686b7a521af6d7a543dcd9c324cf07; confirm Chainguard package versions are at or above 2.6.15-r4; test sysfs buffer resize operations under CS_MODE_SYSFS to ensure no use-after-free occurs.
Typical attack path
- Obtain local access or sufficient privileges to interact with /sys/bus/coresight/devices
- Enable ETR tracing in CS_MODE_SYSFS mode
- Modify the buffer size attribute to force reallocation
- Trigger continued ETR activity that dereferences the stale buffer pointer
- Exploit resulting use-after-free for denial of service or privilege escalation
How to detect it
Review kernel logs for coresight ETR related oops, slab-use-after-free warnings, or KASAN reports triggered after sysfs buffer resize operations; examine audit logs for unusual writes to coresight device attributes.
What your security team should do
- Prioritize patching kernels and Chainguard kuma packages within maintenance windows given the 306-day publication age
- Restrict untrusted access to coresight sysfs interfaces on systems where ETR tracing is enabled
- Monitor for kernel oops or panic events related to coresight ETR buffer handling
The record
In the Linux kernel, the following vulnerability has been resolved: coresight: ETR: Fix ETR buffer use-after-free issue When ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed and enabled again, currently sysfs_buf will point to the newly allocated memory(buf_new) and free the old memory(buf_old). But the etr_buf that is being used by the ETR remains pointed to buf_old, not updated to buf_new. In this case, it will result in a memory use-after-free issue. Fix this by checking ETR's mode before updating and releasing buf_old, if the mode is CS_MODE_SYSFS, then skip updating and releasing it.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Linux | Kernel | 6.6.0 | 6.17.13 |
| openSUSE:Leap 16.0 | dtb-aarch64 | 0 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-64kb | 0 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-azure | 0 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-default | 0 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-default-base | 0 | 6.12.0-160000.26.1.160000.2.7 |
| openSUSE:Leap 16.0 | kernel-docs | 0 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | 0 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | 0 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | 0 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-rt | 0 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-source | 0 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-syms | 0 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | 0 | 6.12.0-160000.26.1 |
| openSUSE:Tumbleweed | kernel-source | 0 | 6.18.5-1.1 |
| openSUSE:Tumbleweed | kernel-source-longterm | 0 | 6.18.16-1.1 |
Related vulnerabilities
- CVE-2026-23226 In the Linux kernel, the following vulnerability has been resolved: ksmbd: add chann_lock… Also affects Kernel
- CVE-2026-23225 In the Linux kernel, the following vulnerability has been resolved: sched/mmcid: Don't… Also affects Kernel
- CVE-2026-23230 In the Linux kernel, the following vulnerability has been resolved: smb: client: split… Also affects Kernel
- CVE-2026-23224 In the Linux kernel, the following vulnerability has been resolved: erofs: fix UAF issue… Also affects Kernel
- CVE-2026-23227 In the Linux kernel, the following vulnerability has been resolved: drm/exynos: vidi: use… Also affects Kernel
- CVE-2026-23223 In the Linux kernel, the following vulnerability has been resolved: xfs: fix UAF in… Also affects Kernel
- CVE-2026-23228 In the Linux kernel, the following vulnerability has been resolved: smb: server: fix leak… Also affects Kernel
- CVE-2026-23229 In the Linux kernel, the following vulnerability has been resolved: crypto: virtio - Add… Also affects Kernel