CVE-2024-40951: ocfs2: fix NULL pointer dereference in ocfs2_abort_trigger()
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: fix NULL pointer dereference in ocfs2aborttrigger()
bdev->bdsuper has been removed and commit 8887b94d9322 change the usage from bdev->bdsuper to bassocmap->host->isb. Since ocfs2 hasn't set bh->bassocmap, it will trigger NULL pointer dereference when calling into ocfs2aborttrigger().
Actually this was pointed out in history, see commit 74e364ad1b13. But I've made a mistake when reviewing commit 8887b94d9322 and then re-introduce this regression.
Since we cannot revive bdev in buffer head, so fix this issue by initializing all types of ocfs2 triggers when fill super, and then get the specific ocfs2 trigger from ocfs2cachinginfo when access journal.
[joseph.qi@linux.alibaba.com: v2]
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-40951?
CVE-2024-40951 has been classified as a medium-severity vulnerability due to the potential for denial-of-service conditions.
How do I fix CVE-2024-40951?
To fix CVE-2024-40951, update to the recommended Linux kernel versions or patches provided by your distribution.
Which versions of the Linux kernel are affected by CVE-2024-40951?
CVE-2024-40951 affects versions of the Linux kernel between 6.6 and 6.9.7, along with specific release candidates like 6.10-rc1 to 6.10-rc4.
What component of the Linux kernel is impacted by CVE-2024-40951?
CVE-2024-40951 specifically impacts the OCFS2 file system component of the Linux kernel.
Is there a known exploit for CVE-2024-40951?
As of now, there are no publicly available exploits for CVE-2024-40951, but it is advisable to patch systems to prevent potential attacks.