Menu

Star on GitHub · 3.2k

CVE-2026-63804

7.8 · HIGH

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 s…

Published Jul 19, 2026CWE-416EPSS 0.13%

Overview

CVE-2026-63804 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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 su

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-63804?

CVE-2026-63804 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-63804?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-63804?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-63804?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-63804 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all