fs/adfs: validate nzones in adfs_validate_bblk()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f6f14a0d71b0773a1d4147d1a3c33d537cd213ab · < a3fd5dc1c7b0aae947a67dc2e2c037d57557a4de| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fs/adfs: validate nzones in adfs_validate_bblk()
Reject ADFS disc records with a zero zone count during boot block validation, before the disc record is used.
When nzones is 0, adfs_read_map() passes it to kmalloc_array(0, ...) which returns ZERO_SIZE_PTR, and adfs_map_layout() then writes to dm[-1], causing an out-of-bounds write before the allocated buffer.
adfs_validate_dr0() already rejects nzones != 1 for old-format images. Add the equivalent check to adfs_validate_bblk() for new-format images so that a crafted image with nzones == 0 is rejected at probe time.
Found by syzkaller.
From the CVE record · Linux
The Linux kernel’s ADFS boot block validation does not reject new-format disc records with a zero zone count. When a crafted image is probed, this can cause an out-of-bounds write; the input does not specify network access, authentication requirements, or user interaction.
Engineers running Linux kernels with ADFS support should check their versions; affected versions were not provided.