# CVE-2024-40951: linux: In the Linux kernel, the following vulnerability has been resolved:  ocfs2: fix NULL pointer dereference in ocfs2_abo...

CVE-2024-40951 is fixed in linux on 1 platform, first by DEBIAN-CVE-2024-40951, released July 12, 2024. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2024-40951
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0024
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Jul 12, 2024

## Description

In the Linux kernel, the following vulnerability has been resolved:  ocfs2: fix NULL pointer dereference in ocfs2_abort_trigger()  bdev->bd_super has been removed and commit 8887b94d9322 change the usage from bdev->bd_super to b_assoc_map->host->i_sb.  Since ocfs2 hasn't set bh->b_assoc_map, it will trigger NULL pointer dereference when calling into ocfs2_abort_trigger().  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 ocfs2_caching_info when access journal.  [joseph.qi@linux.alibaba.com: v2]

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 13.5 (trixie) | 6.9.7-1 | [DEBIAN-CVE-2024-40951](https://patchblox.com/security/data/fix/linux/debian-cve-2024-40951.md) | Jul 12, 2024 |
| Linux | linux Debian 14 | 6.9.7-1 | [DEBIAN-CVE-2024-40951](https://patchblox.com/security/data/fix/linux/debian-cve-2024-40951.md) | Jul 12, 2024 |

---

Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.