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

btrfs: fix race setting file private on concurrent lseek using same fd

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 57 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 severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 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: As exposure requiresRemediation target: Within 365 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 57 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.11.2-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).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.11.2-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.2-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.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-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
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-47741 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: btrfs: fix race setting file private on concurrent lseek using same fd
42 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 btrfs filesystem component of the Linux kernel. This vulnerability arises from a race condition when multiple threads within the same program attempt to use the lseek(2) system call concurrently on the same file. An attacker could exploit this to cause a memory leak or a use-after-free error. A use-after-free error can lead to system instability, crashes, or potentially allow for arbitrary code execution.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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-42658

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 57 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: btrfs: fix race setting file private on concurrent lseek using same fd When doing concurrent lseek(2) system calls against the same file descriptor, using multiple threads belonging to the same process, we have a short time window where a race happens and can result in a memory leak. The race happens like this: 1) A program opens a file descriptor for a file and then spawns two threads (with the pthreads library for example), lets call them task A and task B; 2) Task A calls lseek with SEEK_DATA or SEEK_HOLE and ends up at file.c:find_desired_extent() while holding a read lock on the inode; 3) At the start of find_desired_extent(), it extracts the file's private_data pointer into a local variable named 'private', which has a value of NULL; 4) Task B also calls lseek with SEEK_DATA or SEEK_HOLE, locks the inode in shared mode and enters file.c:find_desired_extent(), where it also extracts file->private_data into its local variable 'private', which has a NULL value; 5) Because it saw a NULL file private, task A allocates a private structure and assigns to the file structure; 6) Task B also saw a NULL file private so it also allocates its own file private and then assigns it to the same file structure, since both tasks are using the same file descriptor. At this point we leak the private structure allocated by task A. Besides the memory leak, there's also the detail that both tasks end up using the same cached state record in the private structure (struct btrfs_file_private::llseek_cached_state), which can result in a use-after-free problem since one task can free it while the other is still using it (only one task took a reference count on it). Also, sharing the cached state is not a good idea since it could result in incorrect results in the future - right now it should not be a problem because it end ups being used only in extent-io-tree.c:count_range_bits() where we do range validation before using the cached state. Fix this by protecting the private assignment and check of a file while holding the inode's spinlock and keep track of the task that allocated the private, so that it's used only by that task in order to prevent user-after-free issues with the cached state record as well as potentially using it incorrectly in the future.

What

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix race setting file private on concurrent lseek using same fd When doing concurrent lseek(2) system calls against the same file descriptor, using multiple threads belonging to the same process, we have a short time window where a race happens and can result in a memory leak. The race happens like this: 1) A program opens a file descriptor for a file and then spawns two threads (with the pthreads library for example), lets call them task A and task B; 2) Task A calls lseek with SEEK_DATA or SEEK_HOLE and ends up at file.c:find_desired_extent() while holding a read lock on the inode; 3) At the start of find_desired_extent(), it extracts the file's private_data pointer into a local variable named 'private', which has a value of NULL; 4) Task B also calls lseek with SEEK_DATA or SEEK_HOLE, locks the inode in shared mode and enters file.c:find_desired_extent(), where it also extracts file->private_data into its local variable 'private', which has a NULL value; 5) Because it saw a NULL file private, task A allocates a private structure and assigns to the file structure; 6) Task B also saw a NULL file private so it also allocates its own file private and then assigns it to the same file structure, since both tasks are using the same file descriptor. At this point we leak the private structure allocated by task A. Besides the memory leak, there's also the detail that both tasks end up using the same cached state record in the private structure (struct btrfs_file_private::llseek_cached_state), which can result in a use-after-free problem since one task can free it while the other is still using it (only one task took a reference count on it). Also, sharing the cached state is not a good idea since it could result in incorrect results in the future - right now it should not be a problem because it end ups being used only in extent-io-tree.c:count_range_bits() where we do range validation before using the cached state. Fix this by protecting the private assignment and check of a file while holding the inode's spinlock and keep track of the task that allocated the private, so that it's used only by that task in order to prevent user-after-free issues with the cached state record as well as potentially using it incorrectly in the future.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How

An attacker operating through local access may attempt exploitation with low privileges. 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: btrfs: fix race setting file private on concurrent lseek using same fd When doing concurrent lseek(2) system calls against the same file descriptor, using multiple threads belonging to the same process, we have a short time window where a race happens and can result in a memory leak. The race happens like this: 1) A program opens a file descriptor for a file and then spawns two threads (with the pthreads library for example), lets call them task A and task B; 2) Task A calls lseek with SEEK_DATA or SEEK_HOLE and ends up at file.c:find_desired_extent() while holding a read lock on the inode; 3) At the start of find_desired_extent(), it extracts the file's private_data pointer into a local variable named 'private', which has a value of NULL; 4) Task B also calls lseek with SEEK_DATA or SEEK_HOLE, locks the inode in shared mode and enters file.c:find_desired_extent(), where it also extracts file->private_data into its local variable 'private', which has a NULL value; 5) Because it saw a NULL file private, task A allocates a private structure and assigns to the file structure; 6) Task B also saw a NULL file private so it also allocates its own file private and then assigns it to the same file structure, since both tasks are using the same file descriptor. At this point we leak the private structure allocated by task A. Besides the memory leak, there's also the detail that both tasks end up using the same cached state record in the private structure (struct btrfs_file_private::llseek_cached_state), which can result in a use-after-free problem since one task can free it while the other is still using it (only one task took a reference count on it). Also, sharing the cached state is not a good idea since it could result in incorrect results in the future - right now it should not be a problem because it end ups being used only in extent-io-tree.c:count_range_bits() where we do range validation before using the cached state. Fix this by protecting the private assignment and check of a file while holding the inode's spinlock and keep track of the task that allocated the private, so that it's used only by that task in order to prevent user-after-free issues with the cached state record as well as potentially using it incorrectly in the future.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How

An attacker operating through local access may attempt exploitation with low privileges. 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
local access → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → cause the confidentiality, integrity or availability impact described by the vendor
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-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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:H/I:H/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.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
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-362
A

Official authority intelligence

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

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

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241023Security Bulletin 23 Oct 2024

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

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

d?id=CVE-2024-47731 Référence CVE CVE-2024-47732 https://www.cve.org/CVERecord?id=CVE-2024-47732 Référence CVE CVE-2024-47733 https://www.cve.org/CVERecord?id=CVE-2024-47733 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47741 https://www.cve.org/CVERecord?id=CVE-2024-47741 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47743 https://www.cve.org/CVERecord?id=CVE-2024-47743 Référence CVE CVE-2024-47744 https://www.cve.org/CVERecord?id=CVE-2024-47744 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=CVE-2024-47749 Référence CVE CVE-2024-47750 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47732 Référence CVE CVE-2024-47733 https://www.cve.org/CVERecord?id=CVE-2024-47733 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47736 https://www.cve.org/CVERecord?id=CVE-2024-47736 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47741 https://www.cve.org/CVERecord?id=CVE-2024-47741 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47743 https://www.cve.org/CVERecord?id=CVE-2024-47743 Référence CVE CVE-2024-47744 https://www.cve.org/CVERecord?id=CVE-2024-47744 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47746 https://www.cve.org/CVERecord?id=CVE-2024-47746 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47731 Référence CVE CVE-2024-47732 https://www.cve.org/CVERecord?id=CVE-2024-47732 Référence CVE CVE-2024-47733 https://www.cve.org/CVERecord?id=CVE-2024-47733 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47741 https://www.cve.org/CVERecord?id=CVE-2024-47741 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47743 https://www.cve.org/CVERecord?id=CVE-2024-47743 Référence CVE CVE-2024-47744 https://www.cve.org/CVERecord?id=CVE-2024-47744 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=CVE-2024-47749 Référence CVE CVE-2024-47750 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47732 Référence CVE CVE-2024-47733 https://www.cve.org/CVERecord?id=CVE-2024-47733 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47736 https://www.cve.org/CVERecord?id=CVE-2024-47736 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47741 https://www.cve.org/CVERecord?id=CVE-2024-47741 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47743 https://www.cve.org/CVERecord?id=CVE-2024-47743 Référence CVE CVE-2024-47744 https://www.cve.org/CVERecord?id=CVE-2024-47744 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47746 https://www.cve.org/CVERecord?id=CVE-2024-47746 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47727 Référence CVE CVE-2024-47728 https://www.cve.org/CVERecord?id=CVE-2024-47728 Référence CVE CVE-2024-47730 https://www.cve.org/CVERecord?id=CVE-2024-47730 Référence CVE CVE-2024-47731 https://www.cve.org/CVERecord?id=CVE-2024-47731 Référence CVE CVE-2024-47732 https://www.cve.org/CVERecord?id=CVE-2024-47732 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47741 https://www.cve.org/CVERecord?id=CVE-2024-47741 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47743 https://www.cve.org/CVERecord?id=CVE-2024-47743 Référence CVE CVE-2024-47744 https://www.cve.org/CVERecord?id=CVE-2024-47744 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=CVE-2024-47749 Référence CVE CVE-2024-47750 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47727 Référence CVE CVE-2024-47728 https://www.cve.org/CVERecord?id=CVE-2024-47728 Référence CVE CVE-2024-47730 https://www.cve.org/CVERecord?id=CVE-2024-47730 Référence CVE CVE-2024-47731 https://www.cve.org/CVERecord?id=CVE-2024-47731 Référence CVE CVE-2024-47732 https://www.cve.org/CVERecord?id=CVE-2024-47732 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47741 https://www.cve.org/CVERecord?id=CVE-2024-47741 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47743 https://www.cve.org/CVERecord?id=CVE-2024-47743 Référence CVE CVE-2024-47744 https://www.cve.org/CVERecord?id=CVE-2024-47744 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=CVE-2024-47749 Référence CVE CVE-2024-47750 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-011390Linux の 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: < 6.2, 6.6.54 ≤ 6.6.*, 6.10.13 ≤ 6.10.*, 6.11.2 ≤ 6.11.*, 6.12 ≤ *
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
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
04

Evidence and provenance

Published 21 Oct 2024 · Last source change 5 Aug 2026, 11:39 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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-42658
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
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-42658↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update 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-47741 · cve.blacktree.nl