nilfs2: prevent kernel bug at submit_bh_wbc()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1f5abe7e7dbcd83e73212c6cb135a6106cea6a0b · < 0c8aa4cfda4e4adb15d5b6536d155eca9c9cd44c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: prevent kernel bug at submit_bh_wbc()
Fix a bug where nilfs_get_block() returns a successful status when searching and inserting the specified block both fail inconsistently. If this inconsistent behavior is not due to a previously fixed bug, then an unexpected race is occurring, so return a temporary error -EAGAIN instead.
This prevents callers such as __block_write_begin_int() from requesting a read into a buffer that is not mapped, which would cause the BUG_ON check for the BH_Mapped flag in submit_bh_wbc() to fail.
From the CVE record · Linux
The Linux kernel’s nilfs2 code can report success when searching for and inserting a block both fail inconsistently. A caller may then request a read into an unmapped buffer, triggering a kernel BUG in submit_bh_wbc(). The input does not specify how an attacker could trigger this condition or whether access or user interaction is required.
Engineers running Linux systems that use nilfs2 should check their kernel versions against the vendor advisory; affected versions are not specified.