debugfs: Fix lockdown check for mmap_prepare
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
debugfs: Fix lockdown check for mmap_prepare
Commit 651fdda8406d ("relay: update relay to use mmap_prepare") changed the `mmap` file operation to `mmap_prepare` for relayfs, but the lockdown check in debugfs was not updated accordingly.
This prevents debugfs from being locked down when the kernel is in integrity mode if a file uses `mmap_prepare` but not `mmap`.
Since the conversion to `mmap_prepare` across the kernel is not yet complete, update the lockdown check to look for both `mmap` and `mmap_prepare` to ensure comprehensive coverage.
From the CVE record · Linux
A debugfs lockdown check does not cover files that use mmap_prepare but not mmap. When the kernel is in integrity mode, this can leave those files outside debugfs lockdown. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with debugfs should check their kernel version against the vendor advisory; affected versions are not specified.