BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-46695High confidence

selinux,smack: don't bypass permissions check in inode_setsecctx hook

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 15 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.53% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 15 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

19 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 15 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.115-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-46695 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: selinux,smack: don't bypass permissions check in inode_setsecctx hook
64 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel. A highly privileged user on a Network File System (NFS) client can bypass intended security restrictions and modify security labels on files located on an NFS filesystem. This issue occurs even when root squashing, a security feature designed to limit root user privileges, is enabled on the NFS export. This unauthorized modification of security labels could lead to a bypass of security policies.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-41956

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 15 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

During installation, installed file permissions are set to allow anyone to modify those files.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

During installation, installed file permissions are set to allow anyone to modify those files.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Incorrect Default Permissions → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-276 ↗

CWE-276: Incorrect Default Permissions. During installation, installed file permissions are set to allow anyone to modify those files.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-276
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-2133Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen unspezifischen Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240918Security Bulletin 18 Sep 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 18 Sep 2024, published on 18 September 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-43880 Référence CVE CVE-2024-43889 https://www.cve.org/CVERecord?id=CVE-2024-43889 Référence CVE CVE-2024-43892 https://www.cve.org/CVERecord?id=CVE-2024-43892 Référence CVE CVE-2024-44935 https://www.cve.org/CVERecord?id=CVE-2024-44935 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45663 https://www.cve.org/CVERecord?id=CVE-2024-45663 Référence CVE CVE-2024-46679 https://www.cve.org/CVERecord?id=CVE-2024-46679 Référence CVE CVE-2024-46695 https://www.cve.org/CVERecord?id=CVE-2024-46695 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=CVE-2024-46826 Référence CVE CVE-2024-46858 https://www.cve.org/CVERecord?id=CVE-2024-46858 Référence CVE CVE-2024-47118 https://www.cve.org/CVERecord?id=CVE-2024-47118 Référence CVE CVE-2024-47535 https://www.cve.org/CVERecord?id=CVE-2024-47535 Référence CVE CVE-2024-47561 https://www.cve.org/CVERecord?id=CVE-2024-47561 Référence CVE CVE-2024-47668 https://www.cve.org/CVERecord?id=CVE-2024-47668 Référence CVE CVE-2024-49350 https://www.cve.org/CVERecord?id=CVE-2024-49350 Référence CVE CVE-2024-49949 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0255Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2023-28439 Référence CVE CVE-2023-33201 https://www.cve.org/CVERecord?id=CVE-2023-33201 Référence CVE CVE-2023-36478 https://www.cve.org/CVERecord?id=CVE-2023-36478 Référence CVE CVE-2023-36479 https://www.cve.org/CVERecord?id=CVE-2023-36479 Référence CVE CVE-2023-40167 https://www.cve.org/CVERecord?id=CVE-2023-40167 Référence CVE CVE-2023-41900 https://www.cve.org/CVERecord?id=CVE-2023-41900 Référence CVE CVE-2023-5072 https://www.cve.org/CVERecord?id=CVE-2023-5072 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-3661 https://www.cve.org/CVERecord?id=CVE-2024-3661 Référence CVE CVE-2024-46695 https://www.cve.org/CVERecord?id=CVE-2024-46695 Référence CVE CVE-2024-49949 https://www.cve.org/CVERecord?id=CVE-2024-49949 Référence CVE CVE-2024-50082 https://www.cve.org/CVERecord?id=CVE-2024-50082 Référence CVE CVE-2024-50099 https://www.cve.org/CVERecord?id=CVE-2024-50099 Référence CVE CVE-2024-50110 https://www.cve.org/CVERecord?id=CVE-2024-50110 Référence CVE CVE-2024-50142 https://www.cve.org/CVERecord?id=CVE-2024-50142 Référence CVE CVE-2024-50192 https://www.cve.org/CVERecord?id=CVE-2024-50192 Référence CVE CVE-2024-50256 https://www.cve.org/CVERecord?id=CVE-2024-50256 Référence CVE CVE-2024-50264 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0184Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2024-41080 Référence CVE CVE-2024-42252 https://www.cve.org/CVERecord?id=CVE-2024-42252 Référence CVE CVE-2024-42315 https://www.cve.org/CVERecord?id=CVE-2024-42315 Référence CVE CVE-2024-42319 https://www.cve.org/CVERecord?id=CVE-2024-42319 Référence CVE CVE-2024-43098 https://www.cve.org/CVERecord?id=CVE-2024-43098 Référence CVE CVE-2024-44931 https://www.cve.org/CVERecord?id=CVE-2024-44931 Référence CVE CVE-2024-44940 https://www.cve.org/CVERecord?id=CVE-2024-44940 Référence CVE CVE-2024-44950 https://www.cve.org/CVERecord?id=CVE-2024-44950 Référence CVE CVE-2024-45828 https://www.cve.org/CVERecord?id=CVE-2024-45828 Référence CVE CVE-2024-46695 https://www.cve.org/CVERecord?id=CVE-2024-46695 Référence CVE CVE-2024-46809 https://www.cve.org/CVERecord?id=CVE-2024-46809 Référence CVE CVE-2024-46841 https://www.cve.org/CVERecord?id=CVE-2024-46841 Référence CVE CVE-2024-46849 https://www.cve.org/CVERecord?id=CVE-2024-46849 Référence CVE CVE-2024-46853 https://www.cve.org/CVERecord?id=CVE-2024-46853 Référence CVE CVE-2024-46854 https://www.cve.org/CVERecord?id=CVE-2024-46854 Référence CVE CVE-2024-46858 https://www.cve.org/CVERecord?id=CVE-2024-46858 Référence CVE CVE-2024-46865 https://www.cve.org/CVERecord?id=CVE-2024-46865 Référence CVE CVE-2024-46896 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0153Multiples vulnérabilités dans le noyau Linux de Red Hat

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données, un contournement de la politique de sécurité et un déni de service.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0069Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-38667 Référence CVE CVE-2024-39463 https://www.cve.org/CVERecord?id=CVE-2024-39463 Référence CVE CVE-2024-41016 https://www.cve.org/CVERecord?id=CVE-2024-41016 Référence CVE CVE-2024-42079 https://www.cve.org/CVERecord?id=CVE-2024-42079 Référence CVE CVE-2024-42156 https://www.cve.org/CVERecord?id=CVE-2024-42156 Référence CVE CVE-2024-42158 https://www.cve.org/CVERecord?id=CVE-2024-42158 Référence CVE CVE-2024-44931 https://www.cve.org/CVERecord?id=CVE-2024-44931 Référence CVE CVE-2024-44940 https://www.cve.org/CVERecord?id=CVE-2024-44940 Référence CVE CVE-2024-44942 https://www.cve.org/CVERecord?id=CVE-2024-44942 Référence CVE CVE-2024-46695 https://www.cve.org/CVERecord?id=CVE-2024-46695 Référence CVE CVE-2024-46849 https://www.cve.org/CVERecord?id=CVE-2024-46849 Référence CVE CVE-2024-46852 https://www.cve.org/CVERecord?id=CVE-2024-46852 Référence CVE CVE-2024-46853 https://www.cve.org/CVERecord?id=CVE-2024-46853 Référence CVE CVE-2024-46854 https://www.cve.org/CVERecord?id=CVE-2024-46854 Référence CVE CVE-2024-46855 https://www.cve.org/CVERecord?id=CVE-2024-46855 Référence CVE CVE-2024-46858 https://www.cve.org/CVERecord?id=CVE-2024-46858 Référence CVE CVE-2024-46859 https://www.cve.org/CVERecord?id=CVE-2024-46859 Référence CVE CVE-2024-46865 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0022Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-46683 Référence CVE CVE-2024-46685 https://www.cve.org/CVERecord?id=CVE-2024-46685 Référence CVE CVE-2024-46686 https://www.cve.org/CVERecord?id=CVE-2024-46686 Référence CVE CVE-2024-46687 https://www.cve.org/CVERecord?id=CVE-2024-46687 Référence CVE CVE-2024-46689 https://www.cve.org/CVERecord?id=CVE-2024-46689 Référence CVE CVE-2024-46691 https://www.cve.org/CVERecord?id=CVE-2024-46691 Référence CVE CVE-2024-46692 https://www.cve.org/CVERecord?id=CVE-2024-46692 Référence CVE CVE-2024-46693 https://www.cve.org/CVERecord?id=CVE-2024-46693 Référence CVE CVE-2024-46694 https://www.cve.org/CVERecord?id=CVE-2024-46694 Référence CVE CVE-2024-46695 https://www.cve.org/CVERecord?id=CVE-2024-46695 Référence CVE CVE-2024-46697 https://www.cve.org/CVERecord?id=CVE-2024-46697 Référence CVE CVE-2024-46698 https://www.cve.org/CVERecord?id=CVE-2024-46698 Référence CVE CVE-2024-46701 https://www.cve.org/CVERecord?id=CVE-2024-46701 Référence CVE CVE-2024-46702 https://www.cve.org/CVERecord?id=CVE-2024-46702 Référence CVE CVE-2024-46703 https://www.cve.org/CVERecord?id=CVE-2024-46703 Référence CVE CVE-2024-46705 https://www.cve.org/CVERecord?id=CVE-2024-46705 Référence CVE CVE-2024-46706 https://www.cve.org/CVERecord?id=CVE-2024-46706 Référence CVE CVE-2024-46707 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1108Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-42079 Référence CVE CVE-2024-42156 https://www.cve.org/CVERecord?id=CVE-2024-42156 Référence CVE CVE-2024-42158 https://www.cve.org/CVERecord?id=CVE-2024-42158 Référence CVE CVE-2024-42240 https://www.cve.org/CVERecord?id=CVE-2024-42240 Référence CVE CVE-2024-43892 https://www.cve.org/CVERecord?id=CVE-2024-43892 Référence CVE CVE-2024-43904 https://www.cve.org/CVERecord?id=CVE-2024-43904 Référence CVE CVE-2024-44931 https://www.cve.org/CVERecord?id=CVE-2024-44931 Référence CVE CVE-2024-44940 https://www.cve.org/CVERecord?id=CVE-2024-44940 Référence CVE CVE-2024-44942 https://www.cve.org/CVERecord?id=CVE-2024-44942 Référence CVE CVE-2024-46695 https://www.cve.org/CVERecord?id=CVE-2024-46695 Référence CVE CVE-2024-46724 https://www.cve.org/CVERecord?id=CVE-2024-46724 Référence CVE CVE-2024-46849 https://www.cve.org/CVERecord?id=CVE-2024-46849 Référence CVE CVE-2024-46852 https://www.cve.org/CVERecord?id=CVE-2024-46852 Référence CVE CVE-2024-46853 https://www.cve.org/CVERecord?id=CVE-2024-46853 Référence CVE CVE-2024-46854 https://www.cve.org/CVERecord?id=CVE-2024-46854 Référence CVE CVE-2024-46855 https://www.cve.org/CVERecord?id=CVE-2024-46855 Référence CVE CVE-2024-46858 https://www.cve.org/CVERecord?id=CVE-2024-46858 Référence CVE CVE-2024-46859 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0002Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2024-46674 Référence CVE CVE-2024-46675 https://www.cve.org/CVERecord?id=CVE-2024-46675 Référence CVE CVE-2024-46676 https://www.cve.org/CVERecord?id=CVE-2024-46676 Référence CVE CVE-2024-46677 https://www.cve.org/CVERecord?id=CVE-2024-46677 Référence CVE CVE-2024-46679 https://www.cve.org/CVERecord?id=CVE-2024-46679 Référence CVE CVE-2024-46685 https://www.cve.org/CVERecord?id=CVE-2024-46685 Référence CVE CVE-2024-46686 https://www.cve.org/CVERecord?id=CVE-2024-46686 Référence CVE CVE-2024-46689 https://www.cve.org/CVERecord?id=CVE-2024-46689 Référence CVE CVE-2024-46694 https://www.cve.org/CVERecord?id=CVE-2024-46694 Référence CVE CVE-2024-46695 https://www.cve.org/CVERecord?id=CVE-2024-46695 Référence CVE CVE-2024-46702 https://www.cve.org/CVERecord?id=CVE-2024-46702 Référence CVE CVE-2024-46707 https://www.cve.org/CVERecord?id=CVE-2024-46707 Référence CVE CVE-2024-46710 https://www.cve.org/CVERecord?id=CVE-2024-46710 Référence CVE CVE-2024-46711 https://www.cve.org/CVERecord?id=CVE-2024-46711 Référence CVE CVE-2024-46713 https://www.cve.org/CVERecord?id=CVE-2024-46713 Référence CVE CVE-2024-46714 https://www.cve.org/CVERecord?id=CVE-2024-46714 Référence CVE CVE-2024-46715 https://www.cve.org/CVERecord?id=CVE-2024-46715 Référence CVE CVE-2024-46716 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1101Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-42079 Référence CVE CVE-2024-42156 https://www.cve.org/CVERecord?id=CVE-2024-42156 Référence CVE CVE-2024-42158 https://www.cve.org/CVERecord?id=CVE-2024-42158 Référence CVE CVE-2024-42240 https://www.cve.org/CVERecord?id=CVE-2024-42240 Référence CVE CVE-2024-43882 https://www.cve.org/CVERecord?id=CVE-2024-43882 Référence CVE CVE-2024-43892 https://www.cve.org/CVERecord?id=CVE-2024-43892 Référence CVE CVE-2024-44931 https://www.cve.org/CVERecord?id=CVE-2024-44931 Référence CVE CVE-2024-44940 https://www.cve.org/CVERecord?id=CVE-2024-44940 Référence CVE CVE-2024-44942 https://www.cve.org/CVERecord?id=CVE-2024-44942 Référence CVE CVE-2024-46695 https://www.cve.org/CVERecord?id=CVE-2024-46695 Référence CVE CVE-2024-46724 https://www.cve.org/CVERecord?id=CVE-2024-46724 Référence CVE CVE-2024-46849 https://www.cve.org/CVERecord?id=CVE-2024-46849 Référence CVE CVE-2024-46852 https://www.cve.org/CVERecord?id=CVE-2024-46852 Référence CVE CVE-2024-46853 https://www.cve.org/CVERecord?id=CVE-2024-46853 Référence CVE CVE-2024-46854 https://www.cve.org/CVERecord?id=CVE-2024-46854 Référence CVE CVE-2024-46855 https://www.cve.org/CVERecord?id=CVE-2024-46855 Référence CVE CVE-2024-46858 https://www.cve.org/CVERecord?id=CVE-2024-46858 Référence CVE CVE-2024-46859 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1080Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-46683 Référence CVE CVE-2024-46685 https://www.cve.org/CVERecord?id=CVE-2024-46685 Référence CVE CVE-2024-46686 https://www.cve.org/CVERecord?id=CVE-2024-46686 Référence CVE CVE-2024-46687 https://www.cve.org/CVERecord?id=CVE-2024-46687 Référence CVE CVE-2024-46689 https://www.cve.org/CVERecord?id=CVE-2024-46689 Référence CVE CVE-2024-46691 https://www.cve.org/CVERecord?id=CVE-2024-46691 Référence CVE CVE-2024-46692 https://www.cve.org/CVERecord?id=CVE-2024-46692 Référence CVE CVE-2024-46693 https://www.cve.org/CVERecord?id=CVE-2024-46693 Référence CVE CVE-2024-46694 https://www.cve.org/CVERecord?id=CVE-2024-46694 Référence CVE CVE-2024-46695 https://www.cve.org/CVERecord?id=CVE-2024-46695 Référence CVE CVE-2024-46697 https://www.cve.org/CVERecord?id=CVE-2024-46697 Référence CVE CVE-2024-46698 https://www.cve.org/CVERecord?id=CVE-2024-46698 Référence CVE CVE-2024-46701 https://www.cve.org/CVERecord?id=CVE-2024-46701 Référence CVE CVE-2024-46702 https://www.cve.org/CVERecord?id=CVE-2024-46702 Référence CVE CVE-2024-46703 https://www.cve.org/CVERecord?id=CVE-2024-46703 Référence CVE CVE-2024-46705 https://www.cve.org/CVERecord?id=CVE-2024-46705 Référence CVE CVE-2024-46706 https://www.cve.org/CVERecord?id=CVE-2024-46706 Référence CVE CVE-2024-46707 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1078Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2024-26830 Référence CVE CVE-2024-27062 https://www.cve.org/CVERecord?id=CVE-2024-27062 Référence CVE CVE-2024-38564 https://www.cve.org/CVERecord?id=CVE-2024-38564 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41064 https://www.cve.org/CVERecord?id=CVE-2024-41064 Référence CVE CVE-2024-42124 https://www.cve.org/CVERecord?id=CVE-2024-42124 Référence CVE CVE-2024-43854 https://www.cve.org/CVERecord?id=CVE-2024-43854 Référence CVE CVE-2024-44994 https://www.cve.org/CVERecord?id=CVE-2024-44994 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-46695 https://www.cve.org/CVERecord?id=CVE-2024-46695 Référence CVE CVE-2024-47675 https://www.cve.org/CVERecord?id=CVE-2024-47675 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49949 https://www.cve.org/CVERecord?id=CVE-2024-49949 Référence CVE CVE-2024-50082 https://www.cve.org/CVERecord?id=CVE-2024-50082 Référence CVE CVE-2024-50099 https://www.cve.org/CVERecord?id=CVE-2024-50099 Référence CVE CVE-2024-50110 https://www.cve.org/CVERecord?id=CVE-2024-50110 Référence CVE CVE-2024-50142 https://www.cve.org/CVERecord?id=CVE-2024-50142 Référence CVE CVE-2024-50192 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0870Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-46679 Référence CVE CVE-2024-46685 https://www.cve.org/CVERecord?id=CVE-2024-46685 Référence CVE CVE-2024-46686 https://www.cve.org/CVERecord?id=CVE-2024-46686 Référence CVE CVE-2024-46687 https://www.cve.org/CVERecord?id=CVE-2024-46687 Référence CVE CVE-2024-46689 https://www.cve.org/CVERecord?id=CVE-2024-46689 Référence CVE CVE-2024-46691 https://www.cve.org/CVERecord?id=CVE-2024-46691 Référence CVE CVE-2024-46692 https://www.cve.org/CVERecord?id=CVE-2024-46692 Référence CVE CVE-2024-46693 https://www.cve.org/CVERecord?id=CVE-2024-46693 Référence CVE CVE-2024-46694 https://www.cve.org/CVERecord?id=CVE-2024-46694 Référence CVE CVE-2024-46695 https://www.cve.org/CVERecord?id=CVE-2024-46695 Référence CVE CVE-2024-46702 https://www.cve.org/CVERecord?id=CVE-2024-46702 Référence CVE CVE-2024-46706 https://www.cve.org/CVERecord?id=CVE-2024-46706 Référence CVE CVE-2024-46707 https://www.cve.org/CVERecord?id=CVE-2024-46707 Référence CVE CVE-2024-46709 https://www.cve.org/CVERecord?id=CVE-2024-46709 Référence CVE CVE-2024-46710 https://www.cve.org/CVERecord?id=CVE-2024-46710 Référence CVE CVE-2024-46711 https://www.cve.org/CVERecord?id=CVE-2024-46711 Référence CVE CVE-2024-46714 https://www.cve.org/CVERecord?id=CVE-2024-46714 Référence CVE CVE-2024-46715 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-008616Linux の Linux Kernel における不適切なデフォルトパーミッションに関する脆弱性

Linux の Linux Kernel には、不適切なデフォルトパーミッションに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 13 Sept 2024 · Last source change 5 Aug 2026, 11:37 UTC · CWE-276 · Incorrect Default Permissions

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-41956
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-46695 · cve.blacktree.nl