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

mm: use memalloc_nofs_save() in page_cache_ra_order()

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 13 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.18% 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 13 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.

17 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 13 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.8.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.11-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-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
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-36882 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: mm: use memalloc_nofs_save() in page_cache_ra_order()
80 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
In the Linux kernel, the following vulnerability has been resolved: mm: use memalloc_nofs_save() in page_cache_ra_order() See commit f2c817bed58d ("mm: use memalloc_nofs_save in readahead path"), ensure that page_cache_ra_order() do not attempt to reclaim file-backed pages too, or it leads to a deadlock, found issue when test ext4 large folio. INFO: task DataXceiver for:7494 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:DataXceiver for state:D stack:0 pid:7494 ppid:1 flags:0x00000200 Call trace: __switch_to+0x14c/0x240 __schedule+0x82c/0xdd0 schedule+0x58/0xf0 io_schedule+0x24/0xa0 __folio_lock+0x130/0x300 migrate_pages_batch+0x378/0x918 migrate_pages+0x350/0x700 compact_zone+0x63c/0xb38 compact_zone_order+0xc0/0x118 try_to_compact_pages+0xb0/0x280 __alloc_pages_direct_compact+0x98/0x248 __alloc_pages+0x510/0x1110 alloc_pages+0x9c/0x130 folio_alloc+0x20/0x78 filemap_alloc_folio+0x8c/0x1b0 page_cache_ra_order+0x174/0x308 ondemand_readahead+0x1c8/0x2b8 page_cache_async_ra+0x68/0xb8 filemap_readahead.isra.0+0x64/0xa8 filemap_get_pages+0x3fc/0x5b0 filemap_splice_read+0xf4/0x280 ext4_file_splice_read+0x2c/0x48 [ext4] vfs_splice_read.part.0+0xa8/0x118 splice_direct_to_actor+0xbc/0x288 do_splice_direct+0x9c/0x108 do_sendfile+0x328/0x468 __arm64_sys_sendfile64+0x8c/0x148 invoke_syscall+0x4c/0x118 el0_svc_common.constprop.0+0xc8/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x4c/0x1f8 el0t_64_sync_handler+0xc0/0xc8 el0t_64_sync+0x188/0x190
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-36234

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 13 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: mm: use memalloc_nofs_save() in page_cache_ra_order() See commit f2c817bed58d ("mm: use memalloc_nofs_save in readahead path"), ensure that page_cache_ra_order() do not attempt to reclaim file-backed pages too, or it leads to a deadlock, found issue when test ext4 large folio. INFO: task DataXceiver for:7494 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:DataXceiver for state:D stack:0 pid:7494 ppid:1 flags:0x00000200 Call trace: __switch_to+0x14c/0x240 __schedule+0x82c/0xdd0 schedule+0x58/0xf0 io_schedule+0x24/0xa0 __folio_lock+0x130/0x300 migrate_pages_batch+0x378/0x918 migrate_pages+0x350/0x700 compact_zone+0x63c/0xb38 compact_zone_order+0xc0/0x118 try_to_compact_pages+0xb0/0x280 __alloc_pages_direct_compact+0x98/0x248 __alloc_pages+0x510/0x1110 alloc_pages+0x9c/0x130 folio_alloc+0x20/0x78 filemap_alloc_folio+0x8c/0x1b0 page_cache_ra_order+0x174/0x308 ondemand_readahead+0x1c8/0x2b8 page_cache_async_ra+0x68/0xb8 filemap_readahead.isra.0+0x64/0xa8 filemap_get_pages+0x3fc/0x5b0 filemap_splice_read+0xf4/0x280 ext4_file_splice_read+0x2c/0x48 [ext4] vfs_splice_read.part.0+0xa8/0x118 splice_direct_to_actor+0xbc/0x288 do_splice_direct+0x9c/0x108 do_sendfile+0x328/0x468 __arm64_sys_sendfile64+0x8c/0x148 invoke_syscall+0x4c/0x118 el0_svc_common.constprop.0+0xc8/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x4c/0x1f8 el0t_64_sync_handler+0xc0/0xc8 el0t_64_sync+0x188/0x190

What

In the Linux kernel, the following vulnerability has been resolved: mm: use memalloc_nofs_save() in page_cache_ra_order() See commit f2c817bed58d ("mm: use memalloc_nofs_save in readahead path"), ensure that page_cache_ra_order() do not attempt to reclaim file-backed pages too, or it leads to a deadlock, found issue when test ext4 large folio. INFO: task DataXceiver for:7494 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:DataXceiver for state:D stack:0 pid:7494 ppid:1 flags:0x00000200 Call trace: __switch_to+0x14c/0x240 __schedule+0x82c/0xdd0 schedule+0x58/0xf0 io_schedule+0x24/0xa0 __folio_lock+0x130/0x300 migrate_pages_batch+0x378/0x918 migrate_pages+0x350/0x700 compact_zone+0x63c/0xb38 compact_zone_order+0xc0/0x118 try_to_compact_pages+0xb0/0x280 __alloc_pages_direct_compact+0x98/0x248 __alloc_pages+0x510/0x1110 alloc_pages+0x9c/0x130 folio_alloc+0x20/0x78 filemap_alloc_folio+0x8c/0x1b0 page_cache_ra_order+0x174/0x308 ondemand_readahead+0x1c8/0x2b8 page_cache_async_ra+0x68/0xb8 filemap_readahead.isra.0+0x64/0xa8 filemap_get_pages+0x3fc/0x5b0 filemap_splice_read+0xf4/0x280 ext4_file_splice_read+0x2c/0x48 [ext4] vfs_splice_read.part.0+0xa8/0x118 splice_direct_to_actor+0xbc/0x288 do_splice_direct+0x9c/0x108 do_sendfile+0x328/0x468 __arm64_sys_sendfile64+0x8c/0x148 invoke_syscall+0x4c/0x118 el0_svc_common.constprop.0+0xc8/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x4c/0x1f8 el0t_64_sync_handler+0xc0/0xc8 el0t_64_sync+0x188/0x190

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 cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: mm: use memalloc_nofs_save() in page_cache_ra_order() See commit f2c817bed58d ("mm: use memalloc_nofs_save in readahead path"), ensure that page_cache_ra_order() do not attempt to reclaim file-backed pages too, or it leads to a deadlock, found issue when test ext4 large folio. INFO: task DataXceiver for:7494 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:DataXceiver for state:D stack:0 pid:7494 ppid:1 flags:0x00000200 Call trace: __switch_to+0x14c/0x240 __schedule+0x82c/0xdd0 schedule+0x58/0xf0 io_schedule+0x24/0xa0 __folio_lock+0x130/0x300 migrate_pages_batch+0x378/0x918 migrate_pages+0x350/0x700 compact_zone+0x63c/0xb38 compact_zone_order+0xc0/0x118 try_to_compact_pages+0xb0/0x280 __alloc_pages_direct_compact+0x98/0x248 __alloc_pages+0x510/0x1110 alloc_pages+0x9c/0x130 folio_alloc+0x20/0x78 filemap_alloc_folio+0x8c/0x1b0 page_cache_ra_order+0x174/0x308 ondemand_readahead+0x1c8/0x2b8 page_cache_async_ra+0x68/0xb8 filemap_readahead.isra.0+0x64/0xa8 filemap_get_pages+0x3fc/0x5b0 filemap_splice_read+0xf4/0x280 ext4_file_splice_read+0x2c/0x48 [ext4] vfs_splice_read.part.0+0xa8/0x118 splice_direct_to_actor+0xbc/0x288 do_splice_direct+0x9c/0x108 do_sendfile+0x328/0x468 __arm64_sys_sendfile64+0x8c/0x148 invoke_syscall+0x4c/0x118 el0_svc_common.constprop.0+0xc8/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x4c/0x1f8 el0t_64_sync_handler+0xc0/0xc8 el0t_64_sync+0x188/0x190

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 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 → Improper Locking → 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-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.
CWE-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-1293IBM DataPower Gateway: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um seine Privilegien zu erhöhen, Informationen auszuspähen, einen Denial-of-Service auszulösen oder weitere unspezifizierte Auswirkungen zu erzielen.

Official advisory ↗
BSI · German · WID-SEC-2024-1259Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifischen Angriff

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240605Security Bulletin 05 Jun 2024

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

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

d?id=CVE-2024-35983 Référence CVE CVE-2024-35991 https://www.cve.org/CVERecord?id=CVE-2024-35991 Référence CVE CVE-2024-36002 https://www.cve.org/CVERecord?id=CVE-2024-36002 Référence CVE CVE-2024-36010 https://www.cve.org/CVERecord?id=CVE-2024-36010 Référence CVE CVE-2024-36011 https://www.cve.org/CVERecord?id=CVE-2024-36011 Référence CVE CVE-2024-36012 https://www.cve.org/CVERecord?id=CVE-2024-36012 Référence CVE CVE-2024-36021 https://www.cve.org/CVERecord?id=CVE-2024-36021 Référence CVE CVE-2024-36028 https://www.cve.org/CVERecord?id=CVE-2024-36028 Référence CVE CVE-2024-36477 https://www.cve.org/CVERecord?id=CVE-2024-36477 Référence CVE CVE-2024-36882 https://www.cve.org/CVERecord?id=CVE-2024-36882 Référence CVE CVE-2024-36884 https://www.cve.org/CVERecord?id=CVE-2024-36884 Référence CVE CVE-2024-36891 https://www.cve.org/CVERecord?id=CVE-2024-36891 Référence CVE CVE-2024-36906 https://www.cve.org/CVERecord?id=CVE-2024-36906 Référence CVE CVE-2024-36918 https://www.cve.org/CVERecord?id=CVE-2024-36918 Référence CVE CVE-2024-36920 https://www.cve.org/CVERecord?id=CVE-2024-36920 Référence CVE CVE-2024-36926 https://www.cve.org/CVERecord?id=CVE-2024-36926 Référence CVE CVE-2024-36930 https://www.cve.org/CVERecord?id=CVE-2024-36930 Référence CVE CVE-2024-36932 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2024-26782 Référence CVE CVE-2024-26803 https://www.cve.org/CVERecord?id=CVE-2024-26803 Référence CVE CVE-2024-3372 https://www.cve.org/CVERecord?id=CVE-2024-3372 Référence CVE CVE-2024-34064 https://www.cve.org/CVERecord?id=CVE-2024-34064 Référence CVE CVE-2024-34069 https://www.cve.org/CVERecord?id=CVE-2024-34069 Référence CVE CVE-2024-35195 https://www.cve.org/CVERecord?id=CVE-2024-35195 Référence CVE CVE-2024-35995 https://www.cve.org/CVERecord?id=CVE-2024-35995 Référence CVE CVE-2024-36015 https://www.cve.org/CVERecord?id=CVE-2024-36015 Référence CVE CVE-2024-36881 https://www.cve.org/CVERecord?id=CVE-2024-36881 Référence CVE CVE-2024-36882 https://www.cve.org/CVERecord?id=CVE-2024-36882 Référence CVE CVE-2024-36974 https://www.cve.org/CVERecord?id=CVE-2024-36974 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2024-49766 https://www.cve.org/CVERecord?id=CVE-2024-49766 Référence CVE CVE-2024-49767 https://www.cve.org/CVERecord?id=CVE-2024-49767 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-56201 https://www.cve.org/CVERecord?id=CVE-2024-56201 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-

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

d?id=CVE-2024-36030 Référence CVE CVE-2024-36032 https://www.cve.org/CVERecord?id=CVE-2024-36032 Référence CVE CVE-2024-36281 https://www.cve.org/CVERecord?id=CVE-2024-36281 Référence CVE CVE-2024-36288 https://www.cve.org/CVERecord?id=CVE-2024-36288 Référence CVE CVE-2024-36477 https://www.cve.org/CVERecord?id=CVE-2024-36477 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36479 https://www.cve.org/CVERecord?id=CVE-2024-36479 Référence CVE CVE-2024-36592 https://www.cve.org/CVERecord?id=CVE-2024-36592 Référence CVE CVE-2024-36880 https://www.cve.org/CVERecord?id=CVE-2024-36880 Référence CVE CVE-2024-36882 https://www.cve.org/CVERecord?id=CVE-2024-36882 Référence CVE CVE-2024-36885 https://www.cve.org/CVERecord?id=CVE-2024-36885 Référence CVE CVE-2024-36887 https://www.cve.org/CVERecord?id=CVE-2024-36887 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=CVE-2024-36889 Référence CVE CVE-2024-36890 https://www.cve.org/CVERecord?id=CVE-2024-36890 Référence CVE CVE-2024-36891 https://www.cve.org/CVERecord?id=CVE-2024-36891 Référence CVE CVE-2024-36893 https://www.cve.org/CVERecord?id=CVE-2024-36893 Référence CVE CVE-2024-36894 https://www.cve.org/CVERecord?id=CVE-2024-36894 Référence CVE CVE-2024-36895 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36029 Référence CVE CVE-2024-36030 https://www.cve.org/CVERecord?id=CVE-2024-36030 Référence CVE CVE-2024-36031 https://www.cve.org/CVERecord?id=CVE-2024-36031 Référence CVE CVE-2024-36032 https://www.cve.org/CVERecord?id=CVE-2024-36032 Référence CVE CVE-2024-36033 https://www.cve.org/CVERecord?id=CVE-2024-36033 Référence CVE CVE-2024-36270 https://www.cve.org/CVERecord?id=CVE-2024-36270 Référence CVE CVE-2024-36286 https://www.cve.org/CVERecord?id=CVE-2024-36286 Référence CVE CVE-2024-36880 https://www.cve.org/CVERecord?id=CVE-2024-36880 Référence CVE CVE-2024-36881 https://www.cve.org/CVERecord?id=CVE-2024-36881 Référence CVE CVE-2024-36882 https://www.cve.org/CVERecord?id=CVE-2024-36882 Référence CVE CVE-2024-36883 https://www.cve.org/CVERecord?id=CVE-2024-36883 Référence CVE CVE-2024-36884 https://www.cve.org/CVERecord?id=CVE-2024-36884 Référence CVE CVE-2024-36886 https://www.cve.org/CVERecord?id=CVE-2024-36886 Référence CVE CVE-2024-36887 https://www.cve.org/CVERecord?id=CVE-2024-36887 Référence CVE CVE-2024-36888 https://www.cve.org/CVERecord?id=CVE-2024-36888 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=CVE-2024-36889 Référence CVE CVE-2024-36890 https://www.cve.org/CVERecord?id=CVE-2024-36890 Référence CVE CVE-2024-36891 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36021 Référence CVE CVE-2024-36024 https://www.cve.org/CVERecord?id=CVE-2024-36024 Référence CVE CVE-2024-36025 https://www.cve.org/CVERecord?id=CVE-2024-36025 Référence CVE CVE-2024-36281 https://www.cve.org/CVERecord?id=CVE-2024-36281 Référence CVE CVE-2024-36288 https://www.cve.org/CVERecord?id=CVE-2024-36288 Référence CVE CVE-2024-36477 https://www.cve.org/CVERecord?id=CVE-2024-36477 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36479 https://www.cve.org/CVERecord?id=CVE-2024-36479 Référence CVE CVE-2024-36592 https://www.cve.org/CVERecord?id=CVE-2024-36592 Référence CVE CVE-2024-36882 https://www.cve.org/CVERecord?id=CVE-2024-36882 Référence CVE CVE-2024-36887 https://www.cve.org/CVERecord?id=CVE-2024-36887 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=CVE-2024-36889 Référence CVE CVE-2024-36890 https://www.cve.org/CVERecord?id=CVE-2024-36890 Référence CVE CVE-2024-36894 https://www.cve.org/CVERecord?id=CVE-2024-36894 Référence CVE CVE-2024-36899 https://www.cve.org/CVERecord?id=CVE-2024-36899 Référence CVE CVE-2024-36900 https://www.cve.org/CVERecord?id=CVE-2024-36900 Référence CVE CVE-2024-36901 https://www.cve.org/CVERecord?id=CVE-2024-36901 Référence CVE CVE-2024-36902 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36029 Référence CVE CVE-2024-36030 https://www.cve.org/CVERecord?id=CVE-2024-36030 Référence CVE CVE-2024-36031 https://www.cve.org/CVERecord?id=CVE-2024-36031 Référence CVE CVE-2024-36032 https://www.cve.org/CVERecord?id=CVE-2024-36032 Référence CVE CVE-2024-36033 https://www.cve.org/CVERecord?id=CVE-2024-36033 Référence CVE CVE-2024-36270 https://www.cve.org/CVERecord?id=CVE-2024-36270 Référence CVE CVE-2024-36286 https://www.cve.org/CVERecord?id=CVE-2024-36286 Référence CVE CVE-2024-36880 https://www.cve.org/CVERecord?id=CVE-2024-36880 Référence CVE CVE-2024-36881 https://www.cve.org/CVERecord?id=CVE-2024-36881 Référence CVE CVE-2024-36882 https://www.cve.org/CVERecord?id=CVE-2024-36882 Référence CVE CVE-2024-36883 https://www.cve.org/CVERecord?id=CVE-2024-36883 Référence CVE CVE-2024-36884 https://www.cve.org/CVERecord?id=CVE-2024-36884 Référence CVE CVE-2024-36886 https://www.cve.org/CVERecord?id=CVE-2024-36886 Référence CVE CVE-2024-36887 https://www.cve.org/CVERecord?id=CVE-2024-36887 Référence CVE CVE-2024-36888 https://www.cve.org/CVERecord?id=CVE-2024-36888 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=CVE-2024-36889 Référence CVE CVE-2024-36890 https://www.cve.org/CVERecord?id=CVE-2024-36890 Référence CVE CVE-2024-36891 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36005 Référence CVE CVE-2024-36008 https://www.cve.org/CVERecord?id=CVE-2024-36008 Référence CVE CVE-2024-36010 https://www.cve.org/CVERecord?id=CVE-2024-36010 Référence CVE CVE-2024-36017 https://www.cve.org/CVERecord?id=CVE-2024-36017 Référence CVE CVE-2024-36024 https://www.cve.org/CVERecord?id=CVE-2024-36024 Référence CVE CVE-2024-36281 https://www.cve.org/CVERecord?id=CVE-2024-36281 Référence CVE CVE-2024-36477 https://www.cve.org/CVERecord?id=CVE-2024-36477 Référence CVE CVE-2024-36478 https://www.cve.org/CVERecord?id=CVE-2024-36478 Référence CVE CVE-2024-36479 https://www.cve.org/CVERecord?id=CVE-2024-36479 Référence CVE CVE-2024-36882 https://www.cve.org/CVERecord?id=CVE-2024-36882 Référence CVE CVE-2024-36887 https://www.cve.org/CVERecord?id=CVE-2024-36887 Référence CVE CVE-2024-36899 https://www.cve.org/CVERecord?id=CVE-2024-36899 Référence CVE CVE-2024-36900 https://www.cve.org/CVERecord?id=CVE-2024-36900 Référence CVE CVE-2024-36903 https://www.cve.org/CVERecord?id=CVE-2024-36903 Référence CVE CVE-2024-36904 https://www.cve.org/CVERecord?id=CVE-2024-36904 Référence CVE CVE-2024-36915 https://www.cve.org/CVERecord?id=CVE-2024-36915 Référence CVE CVE-2024-36916 https://www.cve.org/CVERecord?id=CVE-2024-36916 Référence CVE CVE-2024-36917 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-016595Linux の 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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 30 May 2024 · Last source change 11 May 2026, 20:16 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-36234
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD enriched

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-36234↗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-36882 · cve.blacktree.nl