References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to nvd@nist.gov.

Known Affected Software Configurations Switch to CPE 2.2

Change History

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

NIST CWE-476

OR
     *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.11 up to (excluding) 6.11.3

https://git.kernel.org/stable/c/6cb9df81a2c462b89d2f9611009ab43ae8717841 No Types Assigned

https://git.kernel.org/stable/c/6cb9df81a2c462b89d2f9611009ab43ae8717841 Patch

https://git.kernel.org/stable/c/a5336035728d77efd76306940d742a6f23debe68 No Types Assigned

https://git.kernel.org/stable/c/a5336035728d77efd76306940d742a6f23debe68 Patch

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.

kernel.org https://git.kernel.org/stable/c/6cb9df81a2c462b89d2f9611009ab43ae8717841 [No types assigned]

kernel.org https://git.kernel.org/stable/c/a5336035728d77efd76306940d742a6f23debe68 [No types assigned]