ocfs2: handle a symlink read error correctly
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1 · < 52a326f93ceb9348264fddf7bab6e345db69e08c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: handle a symlink read error correctly
Patch series "Convert ocfs2 to use folios".
Mark did a conversion of ocfs2 to use folios and sent it to me as a giant patch for review ;-)
So I've redone it as individual patches, and credited Mark for the patches where his code is substantially the same. It's not a bad way to do it; his patch had some bugs and my patches had some bugs. Hopefully all our bugs were different from each other. And hopefully Mark likes all the changes I made to his code!
This patch (of 23):
If we can't read the buffer, be sure to unlock the page before returning.
From the CVE record · Linux
The Linux kernel’s ocfs2 code can return from a symlink read error without unlocking the page when it cannot read the buffer. The input does not establish how an attacker could trigger this condition or whether it requires local access, authentication, or user interaction.
Engineers running Linux kernels with ocfs2 should check their versions against the vendor advisory; affected versions are not specified in the input.