jfs: fix uaf in jfs_evict_inode
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 1696d6d7d4a1b373e96428d0fe1166bd7c3c795e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
jfs: fix uaf in jfs_evict_inode
When the execution of diMount(ipimap) fails, the object ipimap that has been released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs when rcu_core() calls jfs_free_node().
Therefore, when diMount(ipimap) fails, sbi->ipimap should not be initialized as ipimap.
From the CVE record · Linux
The Linux kernel's JFS code can access a freed ipimap object in diFreeSpecial() if diMount(ipimap) fails and the object is released asynchronously. This can cause a use-after-free; the input does not establish how an attacker could trigger it or whether authentication or user interaction is required.
Engineers running Linux kernels with JFS should check their installations; affected versions are not specified.