nilfs2: fix failure to detect DAT corruption in btree and direct mappings
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c3a7abf06ce719a51139e62a034590be99abbc2c · < f69e81396aea66304d214f175aa371f1b5578862| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix failure to detect DAT corruption in btree and direct mappings
Patch series "nilfs2: fix kernel bug at submit_bh_wbc()".
This resolves a kernel BUG reported by syzbot. Since there are two flaws involved, I've made each one a separate patch.
The first patch alone resolves the syzbot-reported bug, but I think both fixes should be sent to stable, so I've tagged them as such.
This patch (of 2):
Syzbot has reported a kernel bug in submit_bh_wbc() when writing file data to a nilfs2 file system whose metadata is corrupted.
There are two flaws involved in this issue.
From the CVE record · Linux
The Linux kernel’s nilfs2 block mapping can mishandle corrupted DAT metadata during a file write. If an attacker can trigger a write to an affected filesystem with that corruption, the inconsistency can cause a kernel BUG. The input does not establish whether network access, authentication, or user interaction is required.
Engineers running Linux systems that use nilfs2 should check their kernel against the vendor advisory; affected versions were not provided.