Look up another CVE · open CVE-2023-53261 in the interactive tracker

CVE-2023-53261

coresight: Fix memory leak in acpi_buffer->pointer

EPSS 0.1%

Published 2025-09-15 (13 months ago) by the Linux kernel CNA. Subsystem drivers/hwtracing. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2023-53261 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

Release	Status	Version	What this means
Debian 12bookworm	vulnerable	6.1.190-1	No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication.
Debian 13trixie	fixed	6.5.3-1	Update the kernel and reboot. Fixed in 6.5.3-1. A running kernel keeps the old code until the machine restarts.
Debian 14forky	fixed	6.5.3-1	Update the kernel and reboot. Fixed in 6.5.3-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesid	fixed	6.5.3-1	Update the kernel and reboot. Fixed in 6.5.3-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

There are memory leaks reported by kmemleak: ... unreferenced object 0xffff00213c141000 (size 1024): comm "systemd-udevd", pid 2123, jiffies 4294909467 (age 6062.160s) hex dump (first 32 bytes): 04 00 00 00 02 00 00 00 18 10 14 3c 21 00 ff ff ...........<!... 00 00 00 00 00 00 00 00 03 00 00 00 10 00 00 00 ................ backtrace: [<000000004b7c9001>] __kmem_cache_alloc_node+0x2f8/0x348 [<00000000b0fc7ceb>] __kmalloc+0x58/0x108 [<0000000064ff4695>] acpi_os_allocate+0x2c/0x68 [<000000007d57d116>] acpi_ut_initialize_buffer+0x54/0xe0 [<0000000024583908>] acpi_evaluate_object+0x388/0x438 [<0000000017b2e72b>] acpi_evaluate_object_typed+0xe8/0x240 [<000000005df0eac2>] coresight_get_platform_data+0x1b4/0x988 [coresight] ... The ACPI buffer memory (buf.pointer) should be freed. But the buffer is also used after returning from acpi_get_dsd_graph(). Move the temporary variables buf to acpi_coresight_parse_graph(), and free it before the function return to prevent memory leak.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/hwtracing/coresight/coresight-platform.c

What this is: ARM/CORESIGHT FRAMEWORK AND DRIVERSMAINTAINERS section matched on drivers/hwtracing/coresight/* · coresight@lists.linaro.org · Maintained
Kernel module: coresight

Check it on the machine

grep -w CONFIG_CORESIGHT /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w coresight

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

bookwormMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, i386/686, i386/686-pae, i386/rt/686-pae, ppc64el/powerpc64le
trixieMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, armel/rpi, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
forky, sidMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt-amd64, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x

M: a module where it is built at all; some flavours do not build it

Build switch: CONFIG_CORESIGHT

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Debian tracker CVE record NVD kernel CNA record

Signals

Published: 2025-09-15 (13 months ago)source
CVSS: no vector published, unrated
Attack vector: not published
EPSS: 0.13%, higher than 2.4% of all CVEssource
CISA KEV: not listedthe KEV catalogue
Debian urgency: not yet assignedsource
Subsystem: drivers/hwtracing

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
5.3	6.5.3	d1b60e7c9fee
5.3	6.6	1a9e02673e25

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2023-53261, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.