cve.bz

CVE-2025-40209 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix memory leak of qgroup_list in btrfs_add_qgroup_relation When btrfs_add_qgroup_relation() is called with invalid qgroup levels (src >= dst), the function returns -EINVAL directly without freeing the preallocated qgroup_list structure passed by the caller. This causes a memory leak because the caller unconditionally sets the pointer to NULL after the call, preventing any cleanup. The issue occurs because the level validation check happens before the mutex is acquired and before any error handling path that would free the prealloc pointer. On this early return, the cleanup code at the 'out' label (which includes kfree(prealloc)) is never reached. In btrfs_ioctl_qgroup_assign(), the code pattern is: prealloc = kzalloc(sizeof(*prealloc), GFP_KERNEL); ret = btrfs_add_qgroup_relation(trans, sa->src, sa->dst, prealloc); prealloc = NULL; // Always set to NULL regardless of return value ... kfree(prealloc); // This becomes kfree(NULL), does nothing When the level check fails, 'prealloc' is never freed by either the callee or the caller, resulting in a 64-byte memory leak per failed operation. This can be triggered repeatedly by an unprivileged user with access to a writable btrfs mount, potentially exhausting kernel memory. Fix this by freeing prealloc before the early return, ensuring prealloc is always freed on all error paths.
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 9th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-40209 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-40209?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-40209?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-40209 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.11 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.58
Linux6.176.17.8
Linuxlater releases6.18

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13linux6.12.63-1DEBIAN-CVE-2025-40209
Debian14linux6.17.8-1DEBIAN-CVE-2025-40209
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-40209
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-40209
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-40209
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2025-40209
Ubuntu24.04:LTSlinux-aws-6.17, linux-oracle-6.176.17.0-1007.7~24.04.1UBUNTU-CVE-2025-40209
Ubuntu24.04:LTSlinux-gcp-6.176.17.0-1008.8~24.04.1UBUNTU-CVE-2025-40209
Ubuntu24.04:LTSlinux-nvidia-6.176.17.0-1008.8UBUNTU-CVE-2025-40209
Ubuntu24.04:LTSlinux-oem-6.176.17.0-1011.11UBUNTU-CVE-2025-40209 USN-8048-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 16 moreno fix listedUBUNTU-CVE-2025-40209
Ubuntu25.10linux6.17.0-14.14UBUNTU-CVE-2025-40209 USN-8029-1
Ubuntu25.10linux-aws, linux-gcp, linux-oracle6.17.0-1007.7UBUNTU-CVE-2025-40209 USN-8029-2 USN-8030-1
Ubuntu25.10linux-azure, linux-raspi6.17.0-1008.8UBUNTU-CVE-2025-40209 USN-8029-1 USN-8029-3
5 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.9.1SUSE-SU-2026:20228-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.9.1SUSE-SU-2026:20220-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.9.1.160000.2.6SUSE-SU-2026:20220-1
SUSELinux Micro 6.2kernel-default-base6.12.0-160000.9.1.160000.2.6SUSE-SU-2026:20207-1
SUSELinux Micro 6.2kernel-rt, kernel-64kb, kernel-source and 1 more6.12.0-160000.9.1SUSE-SU-2026:20207-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.9.1SUSE-SU-2026:20564-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.9.1.160000.2.6openSUSE-SU-2026:20145-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.9.1openSUSE-SU-2026:20145-1
Alpaquita25linux-lts6.12.58-r0BELL-CVE-2025-40209
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-40209

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-40209.

References

Check your stackJSON