Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-46695: selinux,smack: don't bypass permissions check in inode_setsecctx hook

Noroxi assessment

Priority: Monitor (action score 17/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.53% (FIRST EPSS).
  • Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2dbc4b7bac60b02cc6e70d05bf6a7dfd551f9dda, 459584258d47ec3cc6245a82e8a49c9d08eb8b57, 76a0e79bc84f466999fa501fce5bf7a07641b8a7; Azure Linux 3.0 ARM 6.6.51.1-5; Azure Linux 3.0 x64 6.6.51.1-5.
  • Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 4.4.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 2dbc4b7bac60b02cc6e70d05bf6a7dfd551f9dda, 459584258d47ec3cc6245a82e8a49c9d08eb8b57, 76a0e79bc84f466999fa501fce5bf7a07641b8a7; Azure Linux 3.0 ARM 6.6.51.1-5; Azure Linux 3.0 x64 6.6.51.1-5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.4 · v3.1—No exploit Fix available
Published
Sep 13, 2024
Updated
Aug 5, 2026
EPSS
0.5% · 45th percentile

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
17 / 40 · 4.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
4.4
CNA · Linux
9.8
5.4 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-46695

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 6.6.49
  • linux linux kernel6.7 and later · before 6.10.8
  • linux linux kernel6.11

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.11affected
    • 18032ca062e621e15683cb61c066ef3dc5414a7b and later · before 2dbc4b7bac60b02cc6e70d05bf6a7dfd551f9ddaaffected · git
    • 18032ca062e621e15683cb61c066ef3dc5414a7b and later · before fe0cd53791119f6287b6532af8ce41576d664930affected · git
    • 18032ca062e621e15683cb61c066ef3dc5414a7b and later · before eebec98791d0137e455cc006411bb92a54250924affected · git
    • 18032ca062e621e15683cb61c066ef3dc5414a7b and later · before 459584258d47ec3cc6245a82e8a49c9d08eb8b57affected · git
    • 18032ca062e621e15683cb61c066ef3dc5414a7b and later · before f71ec019257ba4f7ab198bd948c5902a207bad96affected · git
    • 18032ca062e621e15683cb61c066ef3dc5414a7b and later · before 76a0e79bc84f466999fa501fce5bf7a07641b8a7affected · git
    • before 3.11not affected · semver
    • 5.10.227 and later · up to and including 5.10.*not affected · semver
    • 5.15.168 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-46693Sep 13, 2024 · soc: qcom: pmic_glink: Fix race during initialization
    18Monitor
  • ← EarlierCVE-2024-46694Sep 13, 2024 · drm/amd/display: avoid using null object of framebuffer
    22Monitor
  • Later →CVE-2024-46696Sep 13, 2024 · nfsd: fix potential UAF in nfsd4_cb_getattr_release
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2dbc4b7bac60b02cc6e70d05bf6a7dfd551f9ddaVendor (CNA)
Linux Linux459584258d47ec3cc6245a82e8a49c9d08eb8b57Vendor (CNA)
Linux Linux76a0e79bc84f466999fa501fce5bf7a07641b8a7Vendor (CNA)
Linux Linuxeebec98791d0137e455cc006411bb92a54250924Vendor (CNA)
Linux Linuxf71ec019257ba4f7ab198bd948c5902a207bad96Vendor (CNA)
Linux Linuxfe0cd53791119f6287b6532af8ce41576d664930Vendor (CNA)
Azure Linux 3.0 ARM6.6.51.1-5 · kernelMicrosoft (MSRC)
Azure Linux 3.0 x646.6.51.1-5 · kernelMicrosoft (MSRC)
almalinux:bpftool7.4.0-503.16.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-503.16.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-503.16.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-503.16.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-503.16.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-503.16.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-503.16.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-503.16.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-503.16.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-503.16.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-503.16.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-503.16.1.el9_5 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.115-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.4.0-503.16.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-503.16.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-503.16.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-503.16.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-503.16.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-503.16.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-503.16.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-503.16.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-503.16.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+17

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records