fs/statmount: fix slab out-of-bounds write in statmount_mnt_idmap
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.347.0.117.1In the Linux kernel, the following vulnerability has been resolved:
fs/statmount: fix slab out-of-bounds write in statmount_mnt_idmap
statmount_mnt_idmap() writes one mapping with seq_printf() and then manually advances seq->count to include the NUL separator.
If seq_printf() overflows, seq_set_overflow() sets seq->count to seq->size. The manual seq->count++ changes this to seq->size + 1. seq_has_overflowed() then no longer detects the overflow. The corrupted count returns to statmount_string(), which later executes:
seq->buf[seq->count++] = '\0';
This causes a 1-byte NULL out-of-bounds write on the dynamically allocated seq buffer.
Fix this by checking for overflow immediately after seq_printf().
From the CVE record · Linux
The Linux kernel's statmount_mnt_idmap() can mishandle a seq_printf() overflow, leading to a one-byte out-of-bounds write on a dynamically allocated buffer. The input does not specify how an attacker could trigger it or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.