nilfs2: fix missing cleanup on rollforward recovery error
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b · < 9d8c3a585d564d776ee60d4aabec59b404be7403| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix missing cleanup on rollforward recovery error
In an error injection test of a routine for mount-time recovery, KASAN found a use-after-free bug.
It turned out that if data recovery was performed using partial logs created by dsync writes, but an error occurred before starting the log writer to create a recovered checkpoint, the inodes whose data had been recovered were left in the ns_dirty_files list of the nilfs object and were not freed.
Fix this issue by cleaning up inodes that have read the recovery data if the recovery routine fails midway before the log writer starts.
From the CVE record · Linux
The Linux kernel's nilfs2 mount-time recovery routine has a use-after-free bug. It occurs when recovery uses partial logs created by dsync writes and fails before the log writer starts; the input does not establish how an attacker could trigger it or whether authentication or user interaction is required.
Engineers running Linux systems that use nilfs2 should check their kernel versions; affected versions were not provided.