CVE-2026-99052

Not scored yetLast modified Oct 30, 2026

Description

In the Linux kernel, the following vulnerability has been resolved:

selinux: preserve NATIVE_LABELS on already-initialized sb in set_mnt_opts

When an NFSv4 filesystem exported with security_label is mounted a second time, sget_fc() returns the existing superblock and nfs_get_root() calls security_sb_set_mnt_opts() again on it. Since the superblock is already SB_INITIALIZED, selinux_set_mnt_opts() takes an early exit without setting SECURITY_LSM_NATIVE_LABELS in *set_kern_flags. nfs_get_root() then sees kflags without SECURITY_LSM_NATIVE_LABELS set and clears NFS_CAP_SECURITY_LABEL on the shared nfs_server, silently disabling per-file labeling for both the new and the original mount.

Commit 3815a245b501 ("security/selinux: fix SECURITY_LSM_NATIVE_LABELS on reused superblock") fixed the same problem in selinux_sb_clone_mnt_opts(). The reused-superblock path for a plain second mount now goes through sb_set_mnt_opts rather than sb_clone_mnt_opts, so it needs the same treatment: on both SE_SBINITIALIZED early exits, set SECURITY_LSM_NATIVE_LABELS in *set_kern_flags when the superblock was already using SECURITY_FS_USE_NATVE.

Metrics

No CVSS score has been published yet.

Affected software

Source: the vendor's advisory (CNA). NVD analysis pending.

VendorProductVersions
LinuxLinux>= eb9ae686507bc5a5ca78e6b3fbe629cd5cc67864, < 22987d24a159ed7df3cdc9090ca5d61e58df0cac; >= eb9ae686507bc5a5ca78e6b3fbe629cd5cc67864, < 2f0f1f5a3b89c1ed67e39be49d29ee7f5c96e039; >= eb9ae686507bc5a5ca78e6b3fbe629cd5cc67864, < dc579e43b13cb65e55eabaae4f1a950e43567fb1; >= eb9ae686507bc5a5ca78e6b3fbe629cd5cc67864, < a545def625860d4ccedc14fe45e884a62a041cef; >= eb9ae686507bc5a5ca78e6b3fbe629cd5cc67864, < a6da93c625b3557dd23ff6db45d2d1bafeae1565; >= eb9ae686507bc5a5ca78e6b3fbe629cd5cc67864, < 5509d498e1b9edafebd5a60ba3cb9ecfda23dc2b; >= eb9ae686507bc5a5ca78e6b3fbe629cd5cc67864, < c997832414f1d846de0a1fa38d7d4f62ba2ea917; >= eb9ae686507bc5a5ca78e6b3fbe629cd5cc67864, < 28b7260548af3d35773477993ad4e4de41578dd7
LinuxLinux3.11

References

Timeline

Published
Oct 23, 2026
Last modified
Oct 30, 2026
NVD status
Received

Related CVEs from 2026

CVE-2026-990537.8In the Linux kernel, the following vulnerability has been resolved: tipc: hold a reference to nodes found by link name tipc_node_find_by_nCVE-2026-990547.8In the Linux kernel, the following vulnerability has been resolved: tipc: destroy topsrv workqueues before closing connections tipc_topsrvCVE-2026-99055In the Linux kernel, the following vulnerability has been resolved: tcp: reject net_iov in zerocopy receive mapping hints After copying a CVE-2026-990567.8In the Linux kernel, the following vulnerability has been resolved: strparser: make sure __strp_recv isn't running before tearing down the CVE-2026-99057In the Linux kernel, the following vulnerability has been resolved: xen/netfront: don't leak the skb when xennet_fill_frags() fails When aCVE-2026-99058In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix NULL current_pwq deref in chained work check current_wqCVE-2026-990597.7In the Linux kernel, the following vulnerability has been resolved: wireguard: noise: reject response consumption after intermediate initiaCVE-2026-99068.3Out of bounds write in GPU in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to poCVE-2026-99060In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7603: initialize global station WCID mt7603 uses a driveCVE-2026-99061In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: fix P2P device removal race in brcmf_detach() When theCVE-2026-99062In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: account only unread bytes in read_skb() After a partial CVE-2026-99063In the Linux kernel, the following vulnerability has been resolved: dm ioctl: don't let data_start run past the buffer struct dm_ioctl has