Joseph Qi

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to a NULL pointer dereference in the `ocfs2 abort trigger()` function. This occurs because `bdev->bd super` has been removed and the usage was changed from `bdev->bd super` to `b assoc map->host->i sb` in commit 8887b94d9322. Since `ocfs2` hasn't set `bh->b assoc map`, it triggers a NULL pointer dereference when calling into `ocfs2 abort trigger()`. The problem was previously pointed out in history, see commit 74e364ad1b13, but was reintroduced due to a mistake in reviewing commit 8887b94d9322. The fix involves initializing all types of `ocfs2` triggers when filling the super block and then getting the specific `ocfs2` trigger from `ocfs2 caching info` when accessing the journal. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** A NULL pointer dereference vulnerability has been resolved in the Linux kernel. The issue occurs in the ocfs2 journal dirty() function due to the removal of bdev->bd super and the change in usage from bdev->bd super to b assoc map->host->i sb, which introduces a NULL pointer dereference since b assoc map is still not initialized. This can be easily reproduced by running xfstests generic/186, which simulates no more credits. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** A vulnerability in the Linux kernel has been resolved, which was related to data corruption after conversion from inline format in the ocfs2 file system. The issue occurred because the code attempted to zero out pages beyond the file size, but these pages were ignored by the writeback code, resulting in data loss when the file was grown. The problem was fixed by not doing the pointless zeroing during conversion from inline format, similar to the standard write path. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.