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

pinmux: Use sequential access to access desc->pinmux data

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.17% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • 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: No default targetRemediation target: Normal maintenance

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 20 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.

23 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 20 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.12.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-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-azure-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-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-nvidia-tegraAffected, 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.11Affected, 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-raspi-realtimeAffected, 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-realtimeAffected, 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-47141 · CSAF 2.0 · revision 66 · interimSUSE Product Security TeamCVE-2024-47141
341 known affected

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

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: pinmux: Use sequential access to access desc->pinmux data When two client of the same gpio call pinctrl_select_state() for the same functionality, we are seeing NULL pointer issue while accessing desc->mux_owner. Let's say two processes A, B executing in pin_request() for the same pin and process A updates the desc->mux_usecount but not yet updated the desc->mux_owner while process B see the desc->mux_usecount which got updated by A path and further executes strcmp and while accessing desc->mux_owner it crashes with NULL pointer. Serialize the access to mux related setting with a mutex lock. cpu0 (process A) cpu1(process B) pinctrl_select_state() { pinctrl_select_state() { pin_request() { pin_request() { ... .... } else { desc->mux_usecount++; desc->mux_usecount && strcmp(desc->mux_owner, owner)) { if (desc->mux_usecount > 1) return 0; desc->mux_owner = owner; } }
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-42874

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 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: pinmux: Use sequential access to access desc->pinmux data When two client of the same gpio call pinctrl_select_state() for the same functionality, we are seeing NULL pointer issue while accessing desc->mux_owner. Let's say two processes A, B executing in pin_request() for the same pin and process A updates the desc->mux_usecount but not yet updated the desc->mux_owner while process B see the desc->mux_usecount which got updated by A path and further executes strcmp and while accessing desc->mux_owner it crashes with NULL pointer. Serialize the access to mux related setting with a mutex lock. cpu0 (process A) cpu1(process B) pinctrl_select_state() { pinctrl_select_state() { pin_request() { pin_request() { ... .... } else { desc->mux_usecount++; desc->mux_usecount && strcmp(desc->mux_owner, owner)) { if (desc->mux_usecount > 1) return 0; desc->mux_owner = owner; } }

What

In the Linux kernel, the following vulnerability has been resolved: pinmux: Use sequential access to access desc->pinmux data When two client of the same gpio call pinctrl_select_state() for the same functionality, we are seeing NULL pointer issue while accessing desc->mux_owner. Let's say two processes A, B executing in pin_request() for the same pin and process A updates the desc->mux_usecount but not yet updated the desc->mux_owner while process B see the desc->mux_usecount which got updated by A path and further executes strcmp and while accessing desc->mux_owner it crashes with NULL pointer. Serialize the access to mux related setting with a mutex lock. cpu0 (process A) cpu1(process B) pinctrl_select_state() { pinctrl_select_state() { pin_request() { pin_request() { ... .... } else { desc->mux_usecount++; desc->mux_usecount && strcmp(desc->mux_owner, owner)) { if (desc->mux_usecount > 1) return 0; desc->mux_owner = owner; } }

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: pinmux: Use sequential access to access desc->pinmux data When two client of the same gpio call pinctrl_select_state() for the same functionality, we are seeing NULL pointer issue while accessing desc->mux_owner. Let's say two processes A, B executing in pin_request() for the same pin and process A updates the desc->mux_usecount but not yet updated the desc->mux_owner while process B see the desc->mux_usecount which got updated by A path and further executes strcmp and while accessing desc->mux_owner it crashes with NULL pointer. Serialize the access to mux related setting with a mutex lock. cpu0 (process A) cpu1(process B) pinctrl_select_state() { pinctrl_select_state() { pin_request() { pin_request() { ... .... } else { desc->mux_usecount++; desc->mux_usecount && strcmp(desc->mux_owner, owner)) { if (desc->mux_usecount > 1) return 0; desc->mux_owner = owner; } }

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

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
local access → Improper Locking → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
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-667 ↗

CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial of serviceCWE-667
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-0047Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen und weitere nicht spezifizierte Angriffe zu starten.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250115Security Bulletin 15 Jan 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 15 Jan 2025, published on 15 January 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2024-46836 Référence CVE CVE-2024-46842 https://www.cve.org/CVERecord?id=CVE-2024-46842 Référence CVE CVE-2024-46843 https://www.cve.org/CVERecord?id=CVE-2024-46843 Référence CVE CVE-2024-46848 https://www.cve.org/CVERecord?id=CVE-2024-46848 Référence CVE CVE-2024-46857 https://www.cve.org/CVERecord?id=CVE-2024-46857 Référence CVE CVE-2024-46860 https://www.cve.org/CVERecord?id=CVE-2024-46860 Référence CVE CVE-2024-46861 https://www.cve.org/CVERecord?id=CVE-2024-46861 Référence CVE CVE-2024-46870 https://www.cve.org/CVERecord?id=CVE-2024-46870 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2024-47658 https://www.cve.org/CVERecord?id=CVE-2024-47658 Référence CVE CVE-2024-47661 https://www.cve.org/CVERecord?id=CVE-2024-47661 Référence CVE CVE-2024-47662 https://www.cve.org/CVERecord?id=CVE-2024-47662 Référence CVE CVE-2024-47664 https://www.cve.org/CVERecord?id=CVE-2024-47664 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47683 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2024-46836 Référence CVE CVE-2024-46842 https://www.cve.org/CVERecord?id=CVE-2024-46842 Référence CVE CVE-2024-46843 https://www.cve.org/CVERecord?id=CVE-2024-46843 Référence CVE CVE-2024-46848 https://www.cve.org/CVERecord?id=CVE-2024-46848 Référence CVE CVE-2024-46857 https://www.cve.org/CVERecord?id=CVE-2024-46857 Référence CVE CVE-2024-46860 https://www.cve.org/CVERecord?id=CVE-2024-46860 Référence CVE CVE-2024-46861 https://www.cve.org/CVERecord?id=CVE-2024-46861 Référence CVE CVE-2024-46870 https://www.cve.org/CVERecord?id=CVE-2024-46870 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2024-47658 https://www.cve.org/CVERecord?id=CVE-2024-47658 Référence CVE CVE-2024-47661 https://www.cve.org/CVERecord?id=CVE-2024-47661 Référence CVE CVE-2024-47662 https://www.cve.org/CVERecord?id=CVE-2024-47662 Référence CVE CVE-2024-47664 https://www.cve.org/CVERecord?id=CVE-2024-47664 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47683 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2024-43900 Référence CVE CVE-2024-44938 https://www.cve.org/CVERecord?id=CVE-2024-44938 Référence CVE CVE-2024-44955 https://www.cve.org/CVERecord?id=CVE-2024-44955 Référence CVE CVE-2024-45828 https://www.cve.org/CVERecord?id=CVE-2024-45828 Référence CVE CVE-2024-46784 https://www.cve.org/CVERecord?id=CVE-2024-46784 Référence CVE CVE-2024-46809 https://www.cve.org/CVERecord?id=CVE-2024-46809 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=CVE-2024-46826 Référence CVE CVE-2024-46841 https://www.cve.org/CVERecord?id=CVE-2024-46841 Référence CVE CVE-2024-46871 https://www.cve.org/CVERecord?id=CVE-2024-46871 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-47143 https://www.cve.org/CVERecord?id=CVE-2024-47143 Référence CVE CVE-2024-47408 https://www.cve.org/CVERecord?id=CVE-2024-47408 Référence CVE CVE-2024-47670 https://www.cve.org/CVERecord?id=CVE-2024-47670 Référence CVE CVE-2024-47671 https://www.cve.org/CVERecord?id=CVE-2024-47671 Référence CVE CVE-2024-47672 https://www.cve.org/CVERecord?id=CVE-2024-47672 Référence CVE CVE-2024-47673 https://www.cve.org/CVERecord?id=CVE-2024-47673 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47679 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-43900 Référence CVE CVE-2024-44938 https://www.cve.org/CVERecord?id=CVE-2024-44938 Référence CVE CVE-2024-44955 https://www.cve.org/CVERecord?id=CVE-2024-44955 Référence CVE CVE-2024-45828 https://www.cve.org/CVERecord?id=CVE-2024-45828 Référence CVE CVE-2024-46784 https://www.cve.org/CVERecord?id=CVE-2024-46784 Référence CVE CVE-2024-46809 https://www.cve.org/CVERecord?id=CVE-2024-46809 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=CVE-2024-46826 Référence CVE CVE-2024-46841 https://www.cve.org/CVERecord?id=CVE-2024-46841 Référence CVE CVE-2024-46871 https://www.cve.org/CVERecord?id=CVE-2024-46871 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-47143 https://www.cve.org/CVERecord?id=CVE-2024-47143 Référence CVE CVE-2024-47408 https://www.cve.org/CVERecord?id=CVE-2024-47408 Référence CVE CVE-2024-47707 https://www.cve.org/CVERecord?id=CVE-2024-47707 Référence CVE CVE-2024-47711 https://www.cve.org/CVERecord?id=CVE-2024-47711 Référence CVE CVE-2024-47726 https://www.cve.org/CVERecord?id=CVE-2024-47726 Référence CVE CVE-2024-47730 https://www.cve.org/CVERecord?id=CVE-2024-47730 Référence CVE CVE-2024-47794 https://www.cve.org/CVERecord?id=CVE-2024-47794 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=

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

/notices/USN-7382-1 Référence CVE CVE-2023-52880 https://www.cve.org/CVERecord?id=CVE-2023-52880 Référence CVE CVE-2024-36476 https://www.cve.org/CVERecord?id=CVE-2024-36476 Référence CVE CVE-2024-38558 https://www.cve.org/CVERecord?id=CVE-2024-38558 Référence CVE CVE-2024-39282 https://www.cve.org/CVERecord?id=CVE-2024-39282 Référence CVE CVE-2024-41932 https://www.cve.org/CVERecord?id=CVE-2024-41932 Référence CVE CVE-2024-41935 https://www.cve.org/CVERecord?id=CVE-2024-41935 Référence CVE CVE-2024-43098 https://www.cve.org/CVERecord?id=CVE-2024-43098 Référence CVE CVE-2024-45828 https://www.cve.org/CVERecord?id=CVE-2024-45828 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-47143 https://www.cve.org/CVERecord?id=CVE-2024-47143 Référence CVE CVE-2024-47408 https://www.cve.org/CVERecord?id=CVE-2024-47408 Référence CVE CVE-2024-47794 https://www.cve.org/CVERecord?id=CVE-2024-47794 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48875 https://www.cve.org/CVERecord?id=CVE-2024-48875 Référence CVE CVE-2024-48876 https://www.cve.org/CVERecord?id=CVE-2024-48876 Référence CVE CVE-2024-48881 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-38599 Référence CVE CVE-2024-39282 https://www.cve.org/CVERecord?id=CVE-2024-39282 Référence CVE CVE-2024-40980 https://www.cve.org/CVERecord?id=CVE-2024-40980 Référence CVE CVE-2024-41047 https://www.cve.org/CVERecord?id=CVE-2024-41047 Référence CVE CVE-2024-43913 https://www.cve.org/CVERecord?id=CVE-2024-43913 Référence CVE CVE-2024-45019 https://www.cve.org/CVERecord?id=CVE-2024-45019 Référence CVE CVE-2024-45828 https://www.cve.org/CVERecord?id=CVE-2024-45828 Référence CVE CVE-2024-46858 https://www.cve.org/CVERecord?id=CVE-2024-46858 Référence CVE CVE-2024-46896 https://www.cve.org/CVERecord?id=CVE-2024-46896 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-47143 https://www.cve.org/CVERecord?id=CVE-2024-47143 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48881 https://www.cve.org/CVERecord?id=CVE-2024-48881 Référence CVE CVE-2024-49569 https://www.cve.org/CVERecord?id=CVE-2024-49569 Référence CVE CVE-2024-49948 https://www.cve.org/CVERecord?id=CVE-2024-49948 Référence CVE CVE-2024-49951 https://www.cve.org/CVERecord?id=CVE-2024-49951 Référence CVE CVE-2024-49978 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26810 Référence CVE CVE-2024-35863 https://www.cve.org/CVERecord?id=CVE-2024-35863 Référence CVE CVE-2024-36476 https://www.cve.org/CVERecord?id=CVE-2024-36476 Référence CVE CVE-2024-39282 https://www.cve.org/CVERecord?id=CVE-2024-39282 Référence CVE CVE-2024-43913 https://www.cve.org/CVERecord?id=CVE-2024-43913 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45828 https://www.cve.org/CVERecord?id=CVE-2024-45828 Référence CVE CVE-2024-46858 https://www.cve.org/CVERecord?id=CVE-2024-46858 Référence CVE CVE-2024-46896 https://www.cve.org/CVERecord?id=CVE-2024-46896 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-47143 https://www.cve.org/CVERecord?id=CVE-2024-47143 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48881 https://www.cve.org/CVERecord?id=CVE-2024-48881 Référence CVE CVE-2024-49569 https://www.cve.org/CVERecord?id=CVE-2024-49569 Référence CVE CVE-2024-49948 https://www.cve.org/CVERecord?id=CVE-2024-49948 Référence CVE CVE-2024-49951 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-43913 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-45828 https://www.cve.org/CVERecord?id=CVE-2024-45828 Référence CVE CVE-2024-46680 https://www.cve.org/CVERecord?id=CVE-2024-46680 Référence CVE CVE-2024-46765 https://www.cve.org/CVERecord?id=CVE-2024-46765 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-46896 https://www.cve.org/CVERecord?id=CVE-2024-46896 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-47143 https://www.cve.org/CVERecord?id=CVE-2024-47143 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47709 https://www.cve.org/CVERecord?id=CVE-2024-47709 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48881 https://www.cve.org/CVERecord?id=CVE-2024-48881 Référence CVE CVE-2024-49569 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-018111Linux の 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
Linux: < 3.10, 6.6.66 ≤ 6.6.*, 6.12.5 ≤ 6.12.*, 6.13 ≤ *
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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 11 Jan 2025 · Last source change 11 May 2026, 20:38 UTC · CWE-667 · Improper Locking

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-42874
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
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
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-42874↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
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-47141 · cve.blacktree.nl