gfs2: fix double destroy_workqueue error
In the Linux kernel, the following vulnerability has been resolved: gfs2: fix double destroy_workqueue error When gfs2_fill_super() fails, destroy_workqueue() is called within gfs2_gl_hash_clear(), and the subsequent code path calls destroy_workqueue() on the same work queue again. This issue can be fixed by setting the work queue pointer to NULL after the first destroy_workqueue() call and checking for a NULL pointer before attempting to destroy the work queue again.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.11.3
- CVEs
- CVE-2024-49956
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 18:18 UTC · Revision 1
Source evidence
In the Linux kernel, the following vulnerability has been resolved: gfs2: fix double destroy_workqueue error When gfs2_fill_super() fails, destroy_workqueue() is called within gfs2_gl_hash_clear(), and the subsequent code path calls destroy_workqueue() on the same work queue again. This issue can be fixed by setting the work queue pointer to NULL after the first destroy_workqueue() call and checking for a NULL pointer before attempting to destroy the work queue again.
osv:CVE-2024-49956
Kernel
Fixed versions: 6.11.3
Complete source record
{
"id": "96984cdb8420b5e55c8880224d17ca1fab89b7aa1c71f30e7d35b70d1c8e819c",
"url": "https://osv.dev/vulnerability/CVE-2024-49956",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "gfs2: fix double destroy_workqueue error",
"summary": "In the Linux kernel, the following vulnerability has been resolved: gfs2: fix double destroy_workqueue error When gfs2_fill_super() fails, destroy_workqueue() is called within gfs2_gl_hash_clear(), and the subsequent code path calls destroy_workqueue() on the same work queue again. This issue can be fixed by setting the work queue pointer to NULL after the first destroy_workqueue() call and checking for a NULL pointer before attempting to destroy the work queue again.",
"evidence": "osv:CVE-2024-49956",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.11.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2024-49956",
"aliases": [
"CVE-2024-49956"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "30e388d573673474cbd089dec83688331c117add"
},
{
"fixed": "a5336035728d77efd76306940d742a6f23debe68"
},
{
"fixed": "6cb9df81a2c462b89d2f9611009ab43ae8717841"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-49956.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.11.0"
},
{
"fixed": "6.11.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-49956.json"
}
}
],
"modified": "2026-10-28T02:30:48.009382887Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/6cb9df81a2c462b89d2f9611009ab43ae8717841",
"https://git.kernel.org/stable/c/a5336035728d77efd76306940d742a6f23debe68",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/49xxx/CVE-2024-49956.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-49956",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/49xxx/CVE-2024-49956.json"
}
},
"related_cves": [
{
"value": "CVE-2024-49956",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 515869,
"published_at": "2024-10-21T18:02:10.385+00:00"
}