debugfs: Fix lockdown check for mmap_prepare
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 651fdda8406d42a5004c5c79f269540a85d6a1ab · fixed in e7f6a6b5741d16fdac7adaecbe0fa52ae756f208; From 651fdda8406d42a5004c5c79f269540a85d6a1ab · fixed in f81808de37338aac8e167f99bfae647b1b835c70
- Linux Linux
6.19
- KernelLinux
From 6.19.0 · fixed in 7.2.4