CVE-2026-63804
Last modified
CVE-2026-63804 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: gfs2: fix use-after-free in gfs2_qd_dealloc gfs2_qd_dealloc(), called as an RCU callback from gfs2_qd_dispose(), accesses the superblock object sdp through qd->qd_sbd after freeing qd. It does so to decrement sd_quota_count and wake up sd_kill_wait. However, by the time the RCU callback runs, gfs2_put_super() may have already freed sdp via free_sbd(). This can happen when gfs2_quota_cleanup() is called during unmount: it disposes of quota objects via call_rcu() and then waits on sd_kill_wait with a 60-second timeout. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: gfs2: fix use-after-free in gfs2_qd_dealloc gfs2_qd_dealloc(), called as an RCU callback from gfs2_qd_dispose(), accesses the superblock object sdp through qd->qd_sbd after freeing qd. It does so to decrement sd_quota_count and wake up sd_kill_wait. However, by the time the RCU callback runs, gfs2_put_super() may have already freed sdp via free_sbd(). This can happen when gfs2_quota_cleanup() is called during unmount: it disposes of quota objects via call_rcu() and then waits on sd_kill_wait with a 60-second timeout. If the timeout expires, or if gfs2_gl_hash_clear() triggers additional qd_put() calls that schedule more RCU callbacks after the wait completes, gfs2_put_super() will proceed to free the superblock while RCU callbacks referencing it are still pending. Add an rcu_barrier() before free_sbd() in gfs2_put_super() to ensure all pending RCU callbacks (including gfs2_qd_dealloc) have completed before the superblock is freed.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.6, < 6.6.144 |
| Linux | Linux Kernel | >= 6.7, < 6.12.95 |
| Linux | Linux Kernel | >= 6.13, < 6.18.38 |
| Linux | Linux Kernel | >= 6.19, < 7.1.3 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-63804?
How severe is CVE-2026-63804?
How do I fix CVE-2026-63804?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-63798In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-63799In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63800In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-63801In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-63802In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63803In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63805In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63806In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-63807In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-63808In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-63809In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-6381The WP Maps WordPress plugin before 4.9.3 does not properly…7.5
Are you affected by CVE-2026-63804?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
