ocfs2: remove unreasonable unlock in ocfs2_read_blocks
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ cf76c78595ca87548ca5e45c862ac9e0949c4687 · < 84543da867c967edffd5065fa910ebf56aaae49d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: remove unreasonable unlock in ocfs2_read_blocks
Patch series "Misc fixes for ocfs2_read_blocks", v5.
This series contains 2 fixes for ocfs2_read_blocks(). The first patch fix the issue reported by syzbot, which detects bad unlock balance in ocfs2_read_blocks(). The second patch fixes an issue reported by Heming Zhao when reviewing above fix.
This patch (of 2):
There was a lock release before exiting, so remove the unreasonable unlock.
From the CVE record · Linux
The Linux kernel’s ocfs2_read_blocks() has an unreasonable unlock after a lock was already released, causing a bad unlock balance. The input does not specify what an attacker could do or whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with ocfs2 should check their versions against the vendor advisory; affected versions are not specified.