jfs: upper bound check of tree index in dbAllocAG
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < c8ca21a2836993d7cb816668458e05e598574e55| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
jfs: upper bound check of tree index in dbAllocAG
When computing the tree index in dbAllocAG, we never check if we are out of bounds realative to the size of the stree. This could happen in a scenario where the filesystem metadata are corrupted.
From the CVE record · Linux
The Linux kernel's JFS dbAllocAG function does not check whether a computed tree index exceeds the stree size. Corrupted filesystem metadata can trigger an out-of-bounds index. The input does not specify how an attacker could exploit this or whether authentication or user interaction is required.
Engineers running Linux kernels with JFS should check their kernel versions; affected versions are not specified.