CVE-2026-72223

nvdimm/btt: Free arena sub-allocations on discover_arenas() error path

N/A

Published: August 15, 2026 at 05:54 AM UTC

Updated: August 17, 2026 at 06:18 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: nvdimm/btt: Free arena sub-allocations on discover_arenas() error path Memory allocated by btt_freelist_init(), btt_rtt_init(), and btt_maplocks_init() is not freed on some discover_arenas() error paths. This leaks memory when arena discovery fails. Add the missing kfree() calls to release the allocations before returning an error. [ as: commit message and log edits ]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

4.2 ≤ v < 5.10.2614.2 ≤ v < 5.15.2124.2 ≤ v < 6.1.1784.2 ≤ v < 6.12.974.2 ≤ v < 6.18.404.2 ≤ v < 6.6.1454.2 ≤ v < 7.1.54.2 ≤ v < 7.24.25212e11fde4d40fa627668b4f2222d20db488f71

Vendor states this is fixed in 0b0d9404951aacc9717aa61e77af4a6e9e8f8249 (fixed)

Vendor states this is fixed in 13fe4cd9ddd0aacb7777812328be525a11ea3fea (fixed)

Vendor states this is fixed in 2d0364937550a7b3e2592629c2a68753ac020b28 (fixed)

Vendor states this is fixed in 30d490bb2c4cd220e7dedf862ab6a09eb5dcbad5 (fixed)

Vendor states this is fixed in 7563f69caa9143a491d5f26e563255c734751545 (fixed)

Vendor states this is fixed in 873ced7f345e99f7ee16f9ff226515580332ecc4 (fixed)

Vendor states this is fixed in ba59b96d8d21dc8729fca44a022ca5919c1848c9 (fixed)

Vendor states this is fixed in eeb95774bc79268e2b78ebf01d8781560b5bd671 (fixed)

Vendor states this is fixed in 4.2 (unaffected)

Vendor states this is fixed in 5.10.261 (unaffected)

Vendor states this is fixed in 5.15.212 (unaffected)

Vendor states this is fixed in 6.1.178 (unaffected)