CVE-2024-46695

MEDIUMNVD 4.44.4
EchelonGraph scoreMEDIUM confidence

Score 4.4 from GitHub Security Advisory published 2024-09-13. NVD baseline CVSS 4.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 4.4Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
4.4
EG Score
4.4(medium)
EG Risk
20(Track)
EG Risk 20/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity44% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

September 13, 2024

Last Modified

August 5, 2026

Patch Availability(17)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)5.10.234-1
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u16.1.119-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (30 versions)6.1.115-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.10.9-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.10.9-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 8× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 147 total refreshes for this CVE.

  1. 2026-09-18 19:26 UTCEPSS rescore
  2. 2026-09-18 19:26 UTCEPSS rescore
  3. 2026-09-16 14:06 UTCEPSS rescore
  4. 2026-09-16 05:12 UTCEPSS rescore
  5. 2026-09-15 03:08 UTCEPSS rescore
  6. 2026-09-15 03:08 UTCEPSS rescore
  7. 2026-09-13 16:45 UTCEPSS rescore
  8. 2026-09-12 14:59 UTCEPSS rescore
  9. 2026-09-11 14:51 UTCEPSS rescore
  10. 2026-09-11 09:35 UTCEPSS rescore
  11. 2026-09-08 21:58 UTCEPSS rescore
  12. 2026-09-07 16:00 UTCEPSS rescore
  13. 2026-09-07 08:48 UTCOSV refresh
  14. 2026-09-06 13:46 UTCEPSS rescore
  15. 2026-09-06 13:46 UTCEPSS rescore
  16. 2026-09-05 15:27 UTCEPSS rescore
  17. 2026-09-04 13:59 UTCEPSS rescore
  18. 2026-09-04 05:05 UTCEPSS rescore
  19. 2026-09-02 14:10 UTCEPSS rescore
  20. 2026-09-01 13:52 UTCEPSS rescore
  21. 2026-08-30 19:16 UTCEPSS rescore
  22. 2026-08-28 21:39 UTCEPSS rescore
  23. 2026-08-27 14:23 UTCEPSS rescore
  24. 2026-08-25 13:47 UTCEPSS rescore
  25. 2026-08-24 14:15 UTCEPSS rescore
Show 75 more
  1. 2026-08-23 00:18 UTCEPSS rescore
  2. 2026-08-21 23:47 UTCEPSS rescore
  3. 2026-08-20 22:54 UTCEPSS rescore
  4. 2026-08-20 18:31 UTCOSV refresh
  5. 2026-08-19 17:02 UTCEPSS rescore
  6. 2026-08-18 13:46 UTCEPSS rescore
  7. 2026-08-17 13:45 UTCEPSS rescore
  8. 2026-08-16 14:54 UTCEPSS rescore
  9. 2026-08-16 02:13 UTCEPSS rescore
  10. 2026-08-15 01:28 UTCEPSS rescore
  11. 2026-08-13 21:59 UTCEPSS rescore
  12. 2026-08-12 13:49 UTCEPSS rescore
  13. 2026-08-11 13:40 UTCEPSS rescore
  14. 2026-08-10 23:58 UTCEPSS rescore
  15. 2026-08-09 13:45 UTCEPSS rescore
  16. 2026-08-08 16:35 UTCEPSS rescore
  17. 2026-08-07 16:25 UTCEPSS rescore
  18. 2026-08-06 13:45 UTCEPSS rescore
  19. 2026-08-05 19:16 UTCEPSS rescore
  20. 2026-08-05 12:01 UTCEG score recompute
  21. 2026-08-05 12:01 UTCVendor advisory
  22. 2026-08-05 12:01 UTCGHSA enrichment
  23. 2026-08-04 15:08 UTCEPSS rescore
  24. 2026-08-04 11:48 UTCEG score recompute
  25. 2026-08-04 11:48 UTCVendor advisory
  26. 2026-08-04 11:48 UTCGHSA enrichment
  27. 2026-08-04 10:36 UTCEPSS rescore
  28. 2026-08-03 10:34 UTCEPSS rescore
  29. 2026-08-02 02:25 UTCEPSS rescore
  30. 2026-08-01 04:14 UTCEPSS rescore
  31. 2026-07-30 22:51 UTCOSV refresh
  32. 2026-07-30 16:26 UTCEPSS rescore
  33. 2026-07-30 01:29 UTCEPSS rescore
  34. 2026-07-28 15:34 UTCEPSS rescore
  35. 2026-07-27 14:11 UTCEPSS rescore
  36. 2026-07-26 14:53 UTCEPSS rescore
  37. 2026-07-26 14:53 UTCEPSS rescore
  38. 2026-07-25 14:16 UTCEPSS rescore
  39. 2026-07-24 14:16 UTCEPSS rescore
  40. 2026-07-23 14:17 UTCEPSS rescore
  41. 2026-07-23 02:41 UTCEG score recompute
  42. 2026-07-22 14:07 UTCEPSS rescore
  43. 2026-07-21 15:23 UTCEPSS rescore
  44. 2026-07-21 15:23 UTCEPSS rescore
  45. 2026-07-20 17:06 UTCEPSS rescore
  46. 2026-07-19 14:30 UTCEPSS rescore
  47. 2026-07-19 14:30 UTCEPSS rescore
  48. 2026-07-19 02:28 UTCEPSS rescore
  49. 2026-07-19 02:28 UTCEPSS rescore
  50. 2026-07-18 10:03 UTCEPSS rescore
  51. 2026-07-18 10:03 UTCEPSS rescore
  52. 2026-07-16 17:02 UTCEPSS rescore
  53. 2026-07-15 16:56 UTCEPSS rescore
  54. 2026-07-15 16:56 UTCEPSS rescore
  55. 2026-07-15 01:59 UTCEPSS rescore
  56. 2026-07-15 01:59 UTCEPSS rescore
  57. 2026-07-13 22:29 UTCEPSS rescore
  58. 2026-07-13 07:38 UTCOSV refresh
  59. 2026-07-13 06:12 UTCEPSS rescore
  60. 2026-07-12 05:45 UTCEPSS rescore
  61. 2026-07-12 05:45 UTCEPSS rescore
  62. 2026-07-11 08:26 UTCEPSS rescore
  63. 2026-07-09 19:09 UTCEPSS rescore
  64. 2026-07-09 19:09 UTCEPSS rescore
  65. 2026-07-08 15:14 UTCEPSS rescore
  66. 2026-07-07 13:45 UTCEPSS rescore
  67. 2026-07-06 16:26 UTCEPSS rescore
  68. 2026-07-06 02:22 UTCEPSS rescore
  69. 2026-07-06 02:22 UTCEPSS rescore
  70. 2026-07-04 06:30 UTCEPSS rescore
  71. 2026-07-01 15:05 UTCEPSS rescore
  72. 2026-06-30 23:21 UTCEPSS rescore
  73. 2026-06-30 23:21 UTCEPSS rescore
  74. 2026-06-29 14:05 UTCEPSS rescore
  75. 2026-06-28 14:07 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-46695?
CVE-2024-46695 is a medium vulnerability published on September 13, 2024. 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…
When was CVE-2024-46695 disclosed?
CVE-2024-46695 was first published in the National Vulnerability Database on September 13, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-46695 actively exploited?
CVE-2024-46695 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.2% of all scored CVEs.
What is the CVSS score of CVE-2024-46695?
CVE-2024-46695 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2024-46695?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-46695, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-46695

Explore →

Is Your Infrastructure Affected by CVE-2024-46695?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.