nilfs2: handle inconsistent state in nilfs_btnode_create_block()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a60be987d45dd510aeb54389526f9957cfab106c · < be56dfc9be0604291267c07b0e27a69a6bda4899| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: handle inconsistent state in nilfs_btnode_create_block()
Syzbot reported that a buffer state inconsistency was detected in nilfs_btnode_create_block(), triggering a kernel bug.
It is not appropriate to treat this inconsistency as a bug; it can occur if the argument block address (the buffer index of the newly created block) is a virtual block number and has been reallocated due to corruption of the bitmap used to manage its allocation state.
So, modify nilfs_btnode_create_block() and its callers to treat it as a possible filesystem error, rather than triggering a kernel bug.
From the CVE record · Linux
In nilfs2, an inconsistent buffer state can trigger a kernel bug when a virtual block number is reallocated because its allocation bitmap is corrupted. The input does not establish how an attacker could cause this condition or whether authentication or user interaction is required.
Engineers running Linux kernels with nilfs2 should check their versions; affected versions are not specified.