Answer in brief
CVE-2026-99052 records a Unknown severity vulnerability in selinux: preserve NATIVE_LABELS on already-initialized sb in set_mnt_opts. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=eb9ae686507bc5a5ca78e6b3fbe629cd5cc67864 <a545def625860d4ccedc14fe45e884a62a041cef || >=eb9ae686507bc5a5ca78e6b3fbe629cd5cc67864 <a6da93c625b3557dd23ff6db45d2d1bafeae1565 || >=eb9ae686507bc5a5ca78e6b3fbe629cd5cc67864 <5509d498e1b9edafebd5a60ba3cb9ecfda23dc2b || >=eb9ae686507bc5a5ca78e6b3fbe629cd5cc67864 <c997832414f1d846de0a1fa38d7d4f62ba2ea917 || >=eb9ae686507bc5a5ca78e6b3fbe629cd5cc67864 <28b7260548af3d35773477993ad4e4de41578dd7 | a545def625860d4ccedc14fe45e884a62a041cef, a6da93c625b3557dd23ff6db45d2d1bafeae1565, 5509d498e1b9edafebd5a60ba3cb9ecfda23dc2b, c997832414f1d846de0a1fa38d7d4f62ba2ea917, 28b7260548af3d35773477993ad4e4de41578dd7 |
| Linux/Linuxgeneric | 3.11 | Not reported |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
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.
Quoted source text, attributed separately from HOL analysis.