nilfs2: fix kernel bug due to missing clearing of buffer delay flag
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8c26c4e2694a163d525976e804d81cd955bbb40c · < 743c78d455e784097011ea958b27396001181567| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix kernel bug due to missing clearing of buffer delay flag
Syzbot reported that after nilfs2 reads a corrupted file system image and degrades to read-only, the BUG_ON check for the buffer delay flag in submit_bh_wbc() may fail, causing a kernel bug.
This is because the buffer delay flag is not cleared when clearing the buffer state flags to discard a page/folio or a buffer head. So, fix this.
This became necessary when the use of nilfs2's own page clear routine was expanded. This state inconsistency does not occur if the buffer is written normally by log writing.
From the CVE record · Linux
The Linux kernel's nilfs2 filesystem can retain a buffer delay flag when discarding a page or buffer head. If nilfs2 reads a corrupted filesystem image and becomes read-only, this inconsistent state can trigger a kernel bug. The input does not specify whether authentication or user interaction is required.
Engineers running Linux kernels with nilfs2 should check their systems; affected versions are not specified.