CVE-2024-38570: Linux Kernel use-after-free (CVSS 9.8)

Description

In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix potential glock use-after-free on unmount When a DLM lockspace is released and there ares still locks in that lockspace, DLM will unlock those locks automatically. Commit fb6791d100d1b started exploiting this behavior to speed up filesystem unmount: gfs2 would simply free glocks it didn't want to unlock and then release the lockspace. This didn't take the bast callbacks for asynchronous lock contention notifications into account, which remain active until until a lock is unlocked or its lockspace is released. To prevent those callbacks from accessing deallocated objects, put the glocks that should not be unlocked on the sd_dead_glocks list, release the lockspace, and only then free those glocks. As an additional measure, ignore unexpected ast and bast callbacks if the receiving glock is dead.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Linux Kernel≥ 3.8 < 6.6.33 · ≥ 6.7 < 6.8.12 · ≥ 6.9 < 6.9.3

Remediation

Fixed in

Linux Kernel≥ 6.6.33

Patch & vendor advisories

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-38570 being actively exploited?

CVE-2024-38570 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.68%.

How severe is CVE-2024-38570?

CVE-2024-38570 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.68% probability of exploitation.

Which products are affected by CVE-2024-38570?

Affected products include Linux Kernel.

How do I fix CVE-2024-38570?

Upgrade affected software to a fixed version, for example Linux Kernel 6.6.33 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-38570 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo