Answer in brief
CVE-2024-46695 records a Unknown severity vulnerability in selinux,smack: don't bypass permissions check in inode_setsecctx hook. 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.
Answer in brief
CVE-2024-46695 records a Unknown severity vulnerability in selinux,smack: don't bypass permissions check in inode_setsecctx hook. 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 | 3.11 | Not reported |
| Linux/Linuxgeneric | >=18032ca062e621e15683cb61c066ef3dc5414a7b <2dbc4b7bac60b02cc6e70d05bf6a7dfd551f9dda || >=18032ca062e621e15683cb61c066ef3dc5414a7b <fe0cd53791119f6287b6532af8ce41576d664930 || >=18032ca062e621e15683cb61c066ef3dc5414a7b <eebec98791d0137e455cc006411bb92a54250924 || >=18032ca062e621e15683cb61c066ef3dc5414a7b <459584258d47ec3cc6245a82e8a49c9d08eb8b57 || >=18032ca062e621e15683cb61c066ef3dc5414a7b <f71ec019257ba4f7ab198bd948c5902a207bad96 || >=18032ca062e621e15683cb61c066ef3dc5414a7b <76a0e79bc84f466999fa501fce5bf7a07641b8a7 | 2dbc4b7bac60b02cc6e70d05bf6a7dfd551f9dda, fe0cd53791119f6287b6532af8ce41576d664930, eebec98791d0137e455cc006411bb92a54250924, 459584258d47ec3cc6245a82e8a49c9d08eb8b57, f71ec019257ba4f7ab198bd948c5902a207bad96, 76a0e79bc84f466999fa501fce5bf7a07641b8a7 |
Published upstream
Sep 13, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: selinux,smack: don't bypass permissions check in inode_setsecctx hook Marek Gresko reports that the root user on an NFS client is able to change the security labels on files on an NFS filesystem that is exported with root squashing enabled. The end of the kerneldoc comment for __vfs_setxattr_noperm() states: * This function requires the caller to lock the inode's i_mutex before it * is executed. It also assumes that the caller will make the appropriate * permission checks. nfsd_setattr() does do permissions checking via fh_verify() and nfsd_permission(), but those don't do all the same permissions checks that are done by security_inode_setxattr() and its related LSM hooks do. Since nfsd_setattr() is the only consumer of security_inode_setsecctx(), simplest solution appears to be to replace the call to __vfs_setxattr_noperm() with a call to __vfs_setxattr_locked(). This fixes the above issue and has the added benefit of causing nfsd to recall conflicting delegations on a file when a client tries to change its security label.
Quoted source text, attributed separately from HOL analysis.
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 | 3.11 | Not reported |
| Linux/Linuxgeneric | >=18032ca062e621e15683cb61c066ef3dc5414a7b <2dbc4b7bac60b02cc6e70d05bf6a7dfd551f9dda || >=18032ca062e621e15683cb61c066ef3dc5414a7b <fe0cd53791119f6287b6532af8ce41576d664930 || >=18032ca062e621e15683cb61c066ef3dc5414a7b <eebec98791d0137e455cc006411bb92a54250924 || >=18032ca062e621e15683cb61c066ef3dc5414a7b <459584258d47ec3cc6245a82e8a49c9d08eb8b57 || >=18032ca062e621e15683cb61c066ef3dc5414a7b <f71ec019257ba4f7ab198bd948c5902a207bad96 || >=18032ca062e621e15683cb61c066ef3dc5414a7b <76a0e79bc84f466999fa501fce5bf7a07641b8a7 | 2dbc4b7bac60b02cc6e70d05bf6a7dfd551f9dda, fe0cd53791119f6287b6532af8ce41576d664930, eebec98791d0137e455cc006411bb92a54250924, 459584258d47ec3cc6245a82e8a49c9d08eb8b57, f71ec019257ba4f7ab198bd948c5902a207bad96, 76a0e79bc84f466999fa501fce5bf7a07641b8a7 |
Published upstream
Sep 13, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: selinux,smack: don't bypass permissions check in inode_setsecctx hook Marek Gresko reports that the root user on an NFS client is able to change the security labels on files on an NFS filesystem that is exported with root squashing enabled. The end of the kerneldoc comment for __vfs_setxattr_noperm() states: * This function requires the caller to lock the inode's i_mutex before it * is executed. It also assumes that the caller will make the appropriate * permission checks. nfsd_setattr() does do permissions checking via fh_verify() and nfsd_permission(), but those don't do all the same permissions checks that are done by security_inode_setxattr() and its related LSM hooks do. Since nfsd_setattr() is the only consumer of security_inode_setsecctx(), simplest solution appears to be to replace the call to __vfs_setxattr_noperm() with a call to __vfs_setxattr_locked(). This fixes the above issue and has the added benefit of causing nfsd to recall conflicting delegations on a file when a client tries to change its security label.
Quoted source text, attributed separately from HOL analysis.