CVE-2026-64356

linux: In the Linux kernel, the following vulnerability has been resolved: xfs: fix memory leak in xfs_dqinode_metadir_crea...

CVE-2026-64356 is fixed in 20 products on 1 platform, first by ALAS2023-2026-2045, released August 3, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
5.5
medium
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0018
7th percentile

In the Linux kernel, the following vulnerability has been resolved: xfs: fix memory leak in xfs_dqinode_metadir_create() If xfs_metadir_create() fails in xfs_dqinode_metadir_create(), the current code returns directly, leaking the allocated update and transaction state. If the subsequent commit fails, the caller-owned inode reference is left behind. Fix this memory leak by routing the create failure path through xfs_metadir_cancel(). For both create and commit failures, finish and release any inode returned to the caller, mirroring the unwind pattern in xfs_metadir_mkdir(). The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing v6.13-rc1. The tool is still under development and is not yet publicly available. Manual inspection confirms that the bug is still present in v7.1.1. An x86_64 allyesconfig build showed no new warnings. Runtime validation used kprobe fault injection during `mount -o uquota` on a metadir XFS image. Injecting xfs_metadir_create() reproduced the old active-update path that left mount stuck later in mount setup; after this change, the same injection reported cancel_hits=1 and irele_hits=1. Injecting xfs_metadir_commit() exercised the old inode-reference leak path; after this change, it reported irele_hits=1.

Where it's fixed

ProductFixed inFixReleased
Linux
bpftool6.18 · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
bpftool6.18-debuginfo · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
kernel-livepatch-6.18.39-79.141 · amzn 2023 1:1.0-0.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
kernel6.18 · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
kernel6.18-debuginfo · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
kernel6.18-debuginfo-common-aarch64 · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
kernel6.18-debuginfo-common-x86_64 · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
kernel6.18-devel · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
kernel6.18-headers · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
kernel6.18-modules-extra · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
kernel6.18-modules-extra-common · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
kernel6.18-tools · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
kernel6.18-tools-debuginfo · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
kernel6.18-tools-devel · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
linux · Debian 14 7.1.4-1 DEBIAN-CVE-2026-64356 Aug 7, 2026
microvm-kernel6.18 · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
perf6.18 · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
perf6.18-debuginfo · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
python3-perf6.18 · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026
python3-perf6.18-debuginfo · amzn 2023 1:6.18.39-79.141.amzn2023 ALAS2023-2026-2045 Aug 3, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.