jfs: fix GPF in diFree
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 62aff86fdf18657d9eca7878654415f94f16d027 · < 8018936950360f1c503bb385e158cfc5e4945d18| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
jfs: fix GPF in diFree
Avoid passing inode with JFS_SBI(inode->i_sb)->ipimap == NULL to diFree()[1]. GFP will appear:
struct inode *ipimap = JFS_SBI(ip->i_sb)->ipimap; struct inomap *imap = JFS_IP(ipimap)->i_imap;
JFS_IP() will return invalid pointer when ipimap == NULL
Call Trace: diFree+0x13d/0x2dc0 fs/jfs/jfs_imap.c:853 [1] jfs_evict_inode+0x2c9/0x370 fs/jfs/inode.c:154 evict+0x2ed/0x750 fs/inode.c:578 iput_final fs/inode.c:1654 [inline] iput.part.0+0x3fe/0x820 fs/inode.c:1680 iput+0x58/0x70 fs/inode.c:1670
From the CVE record · Linux
The Linux kernel’s JFS code can pass an inode to diFree when its ipimap pointer is NULL, causing an invalid pointer access and a general protection fault. The input does not specify how an attacker could trigger this condition or whether access or user interaction is required.
Engineers running Linux kernels with JFS should check whether their kernel includes the fix; affected versions are not specified.