jfs: xattr: fix buffer overflow for invalid xattr
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 4598233d9748fe4db4e13b9f473588aa25e87d69| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
jfs: xattr: fix buffer overflow for invalid xattr
When an xattr size is not what is expected, it is printed out to the kernel log in hex format as a form of debugging. But when that xattr size is bigger than the expected size, printing it out can cause an access off the end of the buffer.
Fix this all up by properly restricting the size of the debug hex dump in the kernel log.
From the CVE record · Linux
The Linux kernel's jfs xattr debugging code can read past a buffer when it prints an invalid xattr whose size exceeds the expected size to the kernel log. The input does not specify how an attacker could trigger this condition or whether authentication or user interaction is required.
Engineers running the Linux kernel should check their versions for this jfs xattr issue; affected versions were not provided.