jfs: fix out-of-bounds in dbNextAG() and diAlloc()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < c1ba4b8ca799ff1d99d01f37d7ccb7d5ba5533d2| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
jfs: fix out-of-bounds in dbNextAG() and diAlloc()
In dbNextAG() , there is no check for the case where bmp->db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount().
And in dbNextAG(), a check for the case where agpref is greater than bmp->db_numag should be added, so an out-of-bounds exception should be prevented.
Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.
From the CVE record · Linux
The Linux kernel's JFS code lacks bounds checks in dbNextAG() and diAlloc(). A polluted filesystem image can trigger out-of-bounds access; the input does not specify an attacker's required access or whether user interaction is needed.
Engineers running Linux kernels with JFS support should check their deployments; affected versions are not specified.