CVE-2024-49956: gfs2: fix double destroy_workqueue error

Published Oct 21, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

gfs2: fix double destroyworkqueue error

When gfs2fillsuper() fails, destroyworkqueue() is called within gfs2glhashclear(), and the subsequent code path calls destroyworkqueue() on the same work queue again.

This issue can be fixed by setting the work queue pointer to NULL after the first destroyworkqueue() call and checking for a NULL pointer before attempting to destroy the work queue again.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

2 affected componentsFixes available
Linux Linux kernel>=6.11<6.11.3
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.22-16.12.25-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1
  2. Configuration

    When gfs2_fill_super() fails and destroy_workqueue() is called within gfs2_gl_hash_clear(), set the affected work queue pointer to NULL immediately after the first destroy_workqueue() call, and add a NULL-pointer check so destroy_workqueue() is not invoked again on the same work queue in the subsequent code path.

    Linux kernel (gfs2) workqueue pointer (gfs2 gl hash workqueue) = NULL after first destroy_workqueue() call; check for NULL before second destroy_workqueue()

Event History

Oct 21, 2024
CVE Published
via MITRE·06:02 PM
Data Sourced
via MITRE·06:02 PM
DescriptionSeverity
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Feb 20, 2025
Data Sourced
via Launchpad·12:44 AM
Description
Mar 28, 2025
Data Sourced
via Ubuntu·12:49 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-49956?

CVE-2024-49956 is classified as a low severity vulnerability affecting the Linux kernel.

2

How do I fix CVE-2024-49956?

To fix CVE-2024-49956, update the Linux kernel to versions 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.128-1, 6.12.12-1, or 6.12.15-1.

3

Which versions of the Linux kernel are affected by CVE-2024-49956?

CVE-2024-49956 affects the Linux kernel versions 6.11 and earlier.

4

What is the impact of CVE-2024-49956 on systems?

CVE-2024-49956 can lead to a potential denial of service due to the double destruction of a work queue.

5

Is CVE-2024-49956 specific to any particular Linux distribution?

CVE-2024-49956 affects the Linux kernel across multiple distributions, including Debian.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203