Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

[REJECTED CVE] CVE-2024-26821 was initially identified as a vulnerability related to the mount_setattr() function in the Linux kernel, which dealt with permission checks for mounting file systems. The issue was addressed by relaxing certain permission checks to align with legacy behavior. However, this CVE has been rejected and is no longer considered a valid security vulnerability.

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

In the Linux kernel, the following vulnerability has been resolved: fs: relax mount_setattr() permission checks When we added mount_setattr() I added additional checks compared to the legacy do_reconfigure_mnt() and do_change_type() helpers used by regular mount(2). If that mount had a parent then verify that the caller and the mount namespace the mount is attached to match and if not make sure that it's an anonymous mount. The real rootfs falls into neither category. It is neither an anoymous mount because it is obviously attached to the initial mount namespace but it also obviously doesn't have a parent mount. So that means legacy mount(2) allows changing mount properties on the real rootfs but mount_setattr(2) blocks this. I never thought much about this but of course someone on this planet of earth changes properties on the real rootfs as can be seen in [1]. Since util-linux finally switched to the new mount api in 2.39 not so long ago it also relies on mount_setattr() and t...