CVE-2025-39941CWE-362

CVE-2025-39941

High · published October 4, 2025

CVSS v3.1
7.8
EPSS
0%
Percentile
0.7
In the wild
Unconfirmed
What it is

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

zram: fix slot write race condition

Parallel concurrent writes to the same zram index result in leaked

zsmalloc handles. Schematically we can have something like this:

CPU0 CPU1

zram_slot_lock()

zs_free(handle)

zram_slot_lock()

zram_slot_lock()

zs_free(handle)

zram_slot_lock()

compress compress

handle = zs_malloc() handle = zs_malloc()

zram_slot_lock

zram_set_handle(handle)

zram_slot_lock

zram_slot_lock

zram_set_handle(handle)

zram_slot_lock

Either CPU0 or CPU1 zsmalloc handle will leak because zs_free() is done

too early. In fact, we need to reset zram entry right before we set its

new handle, all under the same slot lock scope.

The record
Technical detail
CVSS v3.1
7.8 · HIGH
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00098 · 0.7th percentile
Weakness
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Published
2025-10-04T12:15Z
Affected products (7)
ProductVersionsFixed in
linux/linux_kernel≥ 6.14, < 6.16.96.16.9
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
References (2)
EPSS history
Timeline
  • 04 OCT 07:31Z
    zram: fix slot write race condition
    cvelistv5