{"id":"CVE-2026-99052","published":"2026-10-23T13:17:28.747","lastModified":"2026-10-23T13:17:28.747","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nselinux: preserve NATIVE_LABELS on already-initialized sb in set_mnt_opts\n\nWhen an NFSv4 filesystem exported with security_label is mounted a\nsecond time, sget_fc() returns the existing superblock and\nnfs_get_root() calls security_sb_set_mnt_opts() again on it. Since the\nsuperblock is already SB_INITIALIZED, selinux_set_mnt_opts() takes an\nearly exit without setting SECURITY_LSM_NATIVE_LABELS in\n*set_kern_flags. nfs_get_root() then sees kflags without\nSECURITY_LSM_NATIVE_LABELS set and clears NFS_CAP_SECURITY_LABEL on\nthe shared nfs_server, silently disabling per-file labeling for both\nthe new and the original mount.\n\nCommit 3815a245b501 (\"security/selinux: fix SECURITY_LSM_NATIVE_LABELS\non reused superblock\") fixed the same problem in\nselinux_sb_clone_mnt_opts().  The reused-superblock path for a plain\nsecond mount now goes through sb_set_mnt_opts rather than\nsb_clone_mnt_opts, so it needs the same treatment: on both\nSE_SBINITIALIZED early exits, set SECURITY_LSM_NATIVE_LABELS in\n*set_kern_flags when the superblock was already using\nSECURITY_FS_USE_NATVE.","cvssScore":null,"cvssSeverity":null,"cvssVector":null,"cwes":[],"vendors":[],"products":[],"references":[{"url":"https://git.kernel.org/stable/c/28b7260548af3d35773477993ad4e4de41578dd7","tags":[]},{"url":"https://git.kernel.org/stable/c/5509d498e1b9edafebd5a60ba3cb9ecfda23dc2b","tags":[]},{"url":"https://git.kernel.org/stable/c/a545def625860d4ccedc14fe45e884a62a041cef","tags":[]},{"url":"https://git.kernel.org/stable/c/a6da93c625b3557dd23ff6db45d2d1bafeae1565","tags":[]},{"url":"https://git.kernel.org/stable/c/c997832414f1d846de0a1fa38d7d4f62ba2ea917","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":null}