ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ cf1d6c763fbcb115263114302485ad17e7933d87 · < c726dea9d0c806d64c26fcef483b1fb9474d8c5e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry()
xattr in ocfs2 maybe 'non-indexed', which saved with additional space requested. It's better to check if the memory is out of bound before memcmp, although this possibility mainly comes from crafted poisonous images.
From the CVE record · Linux
The Linux kernel’s ocfs2_xattr_find_entry() may compare memory before checking its bounds when handling a non-indexed extended attribute. A crafted filesystem image is the main described way to reach this condition. The input does not specify the required access, authentication, or user interaction.
Engineers running Linux kernels that use ocfs2 should check their kernel versions; affected versions were not provided.