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

device-dax: correct pgoff align in dax_set_mapping()

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 19 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.27% 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 19 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 19 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.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.115-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-1Debian Security Tracker ↗Source updated 6 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
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-45239

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 19 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: device-dax: correct pgoff align in dax_set_mapping() pgoff should be aligned using ALIGN_DOWN() instead of ALIGN(). Otherwise, vmf->address not aligned to fault_size will be aligned to the next alignment, that can result in memory failure getting the wrong address. It's a subtle situation that only can be observed in page_mapped_in_vma() after the page is page fault handled by dev_dax_huge_fault. Generally, there is little chance to perform page_mapped_in_vma in dev-dax's page unless in specific error injection to the dax device to trigger an MCE - memory-failure. In that case, page_mapped_in_vma() will be triggered to determine which task is accessing the failure address and kill that task in the end. We used self-developed dax device (which is 2M aligned mapping) , to perform error injection to random address. It turned out that error injected to non-2M-aligned address was causing endless MCE until panic. Because page_mapped_in_vma() kept resulting wrong address and the task accessing the failure address was never killed properly: [ 3783.719419] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.049006] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.049190] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.448042] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.448186] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.792026] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.792179] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.162502] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.162633] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.461116] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.461247] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.764730] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.764859] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.042128] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.042259] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.464293] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.464423] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.818090] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.818217] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3787.085297] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3787.085424] Memory failure: 0x200c9742: recovery action for dax page: Recovered It took us several weeks to pinpoint this problem,  but we eventually used bpftrace to trace the page fault and mce address and successfully identified the issue. Joao added: ; Likely we never reproduce in production because we always pin : device-dax regions in the region align they provide (Qemu does : similarly with prealloc in hugetlb/file backed memory). I think this : bug requires that we touch *unpinned* device-dax regions unaligned to : the device-dax selected alignment (page size i.e. 4K/2M/1G)

What

In the Linux kernel, the following vulnerability has been resolved: device-dax: correct pgoff align in dax_set_mapping() pgoff should be aligned using ALIGN_DOWN() instead of ALIGN(). Otherwise, vmf->address not aligned to fault_size will be aligned to the next alignment, that can result in memory failure getting the wrong address. It's a subtle situation that only can be observed in page_mapped_in_vma() after the page is page fault handled by dev_dax_huge_fault. Generally, there is little chance to perform page_mapped_in_vma in dev-dax's page unless in specific error injection to the dax device to trigger an MCE - memory-failure. In that case, page_mapped_in_vma() will be triggered to determine which task is accessing the failure address and kill that task in the end. We used self-developed dax device (which is 2M aligned mapping) , to perform error injection to random address. It turned out that error injected to non-2M-aligned address was causing endless MCE until panic. Because page_mapped_in_vma() kept resulting wrong address and the task accessing the failure address was never killed properly: [ 3783.719419] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.049006] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.049190] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.448042] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.448186] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.792026] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.792179] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.162502] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.162633] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.461116] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.461247] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.764730] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.764859] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.042128] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.042259] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.464293] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.464423] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.818090] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.818217] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3787.085297] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3787.085424] Memory failure: 0x200c9742: recovery action for dax page: Recovered It took us several weeks to pinpoint this problem,  but we eventually used bpftrace to trace the page fault and mce address and successfully identified the issue. Joao added: ; Likely we never reproduce in production because we always pin : device-dax regions in the region align they provide (Qemu does : similarly with prealloc in hugetlb/file backed memory). I think this : bug requires that we touch *unpinned* device-dax regions unaligned to : the device-dax selected alignment (page size i.e. 4K/2M/1G)

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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: device-dax: correct pgoff align in dax_set_mapping() pgoff should be aligned using ALIGN_DOWN() instead of ALIGN(). Otherwise, vmf->address not aligned to fault_size will be aligned to the next alignment, that can result in memory failure getting the wrong address. It's a subtle situation that only can be observed in page_mapped_in_vma() after the page is page fault handled by dev_dax_huge_fault. Generally, there is little chance to perform page_mapped_in_vma in dev-dax's page unless in specific error injection to the dax device to trigger an MCE - memory-failure. In that case, page_mapped_in_vma() will be triggered to determine which task is accessing the failure address and kill that task in the end. We used self-developed dax device (which is 2M aligned mapping) , to perform error injection to random address. It turned out that error injected to non-2M-aligned address was causing endless MCE until panic. Because page_mapped_in_vma() kept resulting wrong address and the task accessing the failure address was never killed properly: [ 3783.719419] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.049006] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.049190] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.448042] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.448186] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.792026] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.792179] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.162502] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.162633] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.461116] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.461247] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.764730] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.764859] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.042128] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.042259] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.464293] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.464423] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.818090] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.818217] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3787.085297] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3787.085424] Memory failure: 0x200c9742: recovery action for dax page: Recovered It took us several weeks to pinpoint this problem,  but we eventually used bpftrace to trace the page fault and mce address and successfully identified the issue. Joao added: ; Likely we never reproduce in production because we always pin : device-dax regions in the region align they provide (Qemu does : similarly with prealloc in hugetlb/file backed memory). I think this : bug requires that we touch *unpinned* device-dax regions unaligned to : the device-dax selected alignment (page size i.e. 4K/2M/1G)

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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 → vulnerable operation → 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.
CWE not yet assigned
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.
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-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2024-49951 Référence CVE CVE-2024-49953 https://www.cve.org/CVERecord?id=CVE-2024-49953 Référence CVE CVE-2024-49976 https://www.cve.org/CVERecord?id=CVE-2024-49976 Référence CVE CVE-2024-49977 https://www.cve.org/CVERecord?id=CVE-2024-49977 Référence CVE CVE-2024-49999 https://www.cve.org/CVERecord?id=CVE-2024-49999 Référence CVE CVE-2024-50000 https://www.cve.org/CVERecord?id=CVE-2024-50000 Référence CVE CVE-2024-50019 https://www.cve.org/CVERecord?id=CVE-2024-50019 Référence CVE CVE-2024-50020 https://www.cve.org/CVERecord?id=CVE-2024-50020 Référence CVE CVE-2024-50021 https://www.cve.org/CVERecord?id=CVE-2024-50021 Référence CVE CVE-2024-50022 https://www.cve.org/CVERecord?id=CVE-2024-50022 Référence CVE CVE-2024-50023 https://www.cve.org/CVERecord?id=CVE-2024-50023 Référence CVE CVE-2024-50027 https://www.cve.org/CVERecord?id=CVE-2024-50027 Référence CVE CVE-2024-50029 https://www.cve.org/CVERecord?id=CVE-2024-50029 Référence CVE CVE-2024-50041 https://www.cve.org/CVERecord?id=CVE-2024-50041 Référence CVE CVE-2024-50042 https://www.cve.org/CVERecord?id=CVE-2024-50042 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50064 https://www.cve.org/CVERecord?id=CVE-2024-50064 Référence CVE CVE-2024-50074 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50012 Référence CVE CVE-2024-50013 https://www.cve.org/CVERecord?id=CVE-2024-50013 Référence CVE CVE-2024-50014 https://www.cve.org/CVERecord?id=CVE-2024-50014 Référence CVE CVE-2024-50015 https://www.cve.org/CVERecord?id=CVE-2024-50015 Référence CVE CVE-2024-50016 https://www.cve.org/CVERecord?id=CVE-2024-50016 Référence CVE CVE-2024-50017 https://www.cve.org/CVERecord?id=CVE-2024-50017 Référence CVE CVE-2024-50019 https://www.cve.org/CVERecord?id=CVE-2024-50019 Référence CVE CVE-2024-50020 https://www.cve.org/CVERecord?id=CVE-2024-50020 Référence CVE CVE-2024-50021 https://www.cve.org/CVERecord?id=CVE-2024-50021 Référence CVE CVE-2024-50022 https://www.cve.org/CVERecord?id=CVE-2024-50022 Référence CVE CVE-2024-50023 https://www.cve.org/CVERecord?id=CVE-2024-50023 Référence CVE CVE-2024-50024 https://www.cve.org/CVERecord?id=CVE-2024-50024 Référence CVE CVE-2024-50025 https://www.cve.org/CVERecord?id=CVE-2024-50025 Référence CVE CVE-2024-50026 https://www.cve.org/CVERecord?id=CVE-2024-50026 Référence CVE CVE-2024-50027 https://www.cve.org/CVERecord?id=CVE-2024-50027 Référence CVE CVE-2024-50028 https://www.cve.org/CVERecord?id=CVE-2024-50028 Référence CVE CVE-2024-50029 https://www.cve.org/CVERecord?id=CVE-2024-50029 Référence CVE CVE-2024-50030 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-49972 Référence CVE CVE-2024-49974 https://www.cve.org/CVERecord?id=CVE-2024-49974 Référence CVE CVE-2024-49996 https://www.cve.org/CVERecord?id=CVE-2024-49996 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-50009 https://www.cve.org/CVERecord?id=CVE-2024-50009 Référence CVE CVE-2024-50010 https://www.cve.org/CVERecord?id=CVE-2024-50010 Référence CVE CVE-2024-50019 https://www.cve.org/CVERecord?id=CVE-2024-50019 Référence CVE CVE-2024-50020 https://www.cve.org/CVERecord?id=CVE-2024-50020 Référence CVE CVE-2024-50021 https://www.cve.org/CVERecord?id=CVE-2024-50021 Référence CVE CVE-2024-50022 https://www.cve.org/CVERecord?id=CVE-2024-50022 Référence CVE CVE-2024-50023 https://www.cve.org/CVERecord?id=CVE-2024-50023 Référence CVE CVE-2024-50024 https://www.cve.org/CVERecord?id=CVE-2024-50024 Référence CVE CVE-2024-50025 https://www.cve.org/CVERecord?id=CVE-2024-50025 Référence CVE CVE-2024-50026 https://www.cve.org/CVERecord?id=CVE-2024-50026 Référence CVE CVE-2024-50027 https://www.cve.org/CVERecord?id=CVE-2024-50027 Référence CVE CVE-2024-50028 https://www.cve.org/CVERecord?id=CVE-2024-50028 Référence CVE CVE-2024-50029 https://www.cve.org/CVERecord?id=CVE-2024-50029 Référence CVE CVE-2024-50030 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50012 Référence CVE CVE-2024-50013 https://www.cve.org/CVERecord?id=CVE-2024-50013 Référence CVE CVE-2024-50014 https://www.cve.org/CVERecord?id=CVE-2024-50014 Référence CVE CVE-2024-50015 https://www.cve.org/CVERecord?id=CVE-2024-50015 Référence CVE CVE-2024-50016 https://www.cve.org/CVERecord?id=CVE-2024-50016 Référence CVE CVE-2024-50017 https://www.cve.org/CVERecord?id=CVE-2024-50017 Référence CVE CVE-2024-50019 https://www.cve.org/CVERecord?id=CVE-2024-50019 Référence CVE CVE-2024-50020 https://www.cve.org/CVERecord?id=CVE-2024-50020 Référence CVE CVE-2024-50021 https://www.cve.org/CVERecord?id=CVE-2024-50021 Référence CVE CVE-2024-50022 https://www.cve.org/CVERecord?id=CVE-2024-50022 Référence CVE CVE-2024-50023 https://www.cve.org/CVERecord?id=CVE-2024-50023 Référence CVE CVE-2024-50024 https://www.cve.org/CVERecord?id=CVE-2024-50024 Référence CVE CVE-2024-50025 https://www.cve.org/CVERecord?id=CVE-2024-50025 Référence CVE CVE-2024-50026 https://www.cve.org/CVERecord?id=CVE-2024-50026 Référence CVE CVE-2024-50027 https://www.cve.org/CVERecord?id=CVE-2024-50027 Référence CVE CVE-2024-50028 https://www.cve.org/CVERecord?id=CVE-2024-50028 Référence CVE CVE-2024-50029 https://www.cve.org/CVERecord?id=CVE-2024-50029 Référence CVE CVE-2024-50030 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-50012 Référence CVE CVE-2024-50013 https://www.cve.org/CVERecord?id=CVE-2024-50013 Référence CVE CVE-2024-50014 https://www.cve.org/CVERecord?id=CVE-2024-50014 Référence CVE CVE-2024-50015 https://www.cve.org/CVERecord?id=CVE-2024-50015 Référence CVE CVE-2024-50016 https://www.cve.org/CVERecord?id=CVE-2024-50016 Référence CVE CVE-2024-50017 https://www.cve.org/CVERecord?id=CVE-2024-50017 Référence CVE CVE-2024-50019 https://www.cve.org/CVERecord?id=CVE-2024-50019 Référence CVE CVE-2024-50020 https://www.cve.org/CVERecord?id=CVE-2024-50020 Référence CVE CVE-2024-50021 https://www.cve.org/CVERecord?id=CVE-2024-50021 Référence CVE CVE-2024-50022 https://www.cve.org/CVERecord?id=CVE-2024-50022 Référence CVE CVE-2024-50023 https://www.cve.org/CVERecord?id=CVE-2024-50023 Référence CVE CVE-2024-50024 https://www.cve.org/CVERecord?id=CVE-2024-50024 Référence CVE CVE-2024-50025 https://www.cve.org/CVERecord?id=CVE-2024-50025 Référence CVE CVE-2024-50026 https://www.cve.org/CVERecord?id=CVE-2024-50026 Référence CVE CVE-2024-50027 https://www.cve.org/CVERecord?id=CVE-2024-50027 Référence CVE CVE-2024-50028 https://www.cve.org/CVERecord?id=CVE-2024-50028 Référence CVE CVE-2024-50029 https://www.cve.org/CVERecord?id=CVE-2024-50029 Référence CVE CVE-2024-50030 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-50012 Référence CVE CVE-2024-50013 https://www.cve.org/CVERecord?id=CVE-2024-50013 Référence CVE CVE-2024-50014 https://www.cve.org/CVERecord?id=CVE-2024-50014 Référence CVE CVE-2024-50015 https://www.cve.org/CVERecord?id=CVE-2024-50015 Référence CVE CVE-2024-50016 https://www.cve.org/CVERecord?id=CVE-2024-50016 Référence CVE CVE-2024-50017 https://www.cve.org/CVERecord?id=CVE-2024-50017 Référence CVE CVE-2024-50019 https://www.cve.org/CVERecord?id=CVE-2024-50019 Référence CVE CVE-2024-50020 https://www.cve.org/CVERecord?id=CVE-2024-50020 Référence CVE CVE-2024-50021 https://www.cve.org/CVERecord?id=CVE-2024-50021 Référence CVE CVE-2024-50022 https://www.cve.org/CVERecord?id=CVE-2024-50022 Référence CVE CVE-2024-50023 https://www.cve.org/CVERecord?id=CVE-2024-50023 Référence CVE CVE-2024-50024 https://www.cve.org/CVERecord?id=CVE-2024-50024 Référence CVE CVE-2024-50025 https://www.cve.org/CVERecord?id=CVE-2024-50025 Référence CVE CVE-2024-50026 https://www.cve.org/CVERecord?id=CVE-2024-50026 Référence CVE CVE-2024-50027 https://www.cve.org/CVERecord?id=CVE-2024-50027 Référence CVE CVE-2024-50028 https://www.cve.org/CVERecord?id=CVE-2024-50028 Référence CVE CVE-2024-50029 https://www.cve.org/CVERecord?id=CVE-2024-50029 Référence CVE CVE-2024-50030 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50003 Référence CVE CVE-2024-50006 https://www.cve.org/CVERecord?id=CVE-2024-50006 Référence CVE CVE-2024-50007 https://www.cve.org/CVERecord?id=CVE-2024-50007 Référence CVE CVE-2024-50008 https://www.cve.org/CVERecord?id=CVE-2024-50008 Référence CVE CVE-2024-50010 https://www.cve.org/CVERecord?id=CVE-2024-50010 Référence CVE CVE-2024-50012 https://www.cve.org/CVERecord?id=CVE-2024-50012 Référence CVE CVE-2024-50013 https://www.cve.org/CVERecord?id=CVE-2024-50013 Référence CVE CVE-2024-50015 https://www.cve.org/CVERecord?id=CVE-2024-50015 Référence CVE CVE-2024-50019 https://www.cve.org/CVERecord?id=CVE-2024-50019 Référence CVE CVE-2024-50022 https://www.cve.org/CVERecord?id=CVE-2024-50022 Référence CVE CVE-2024-50024 https://www.cve.org/CVERecord?id=CVE-2024-50024 Référence CVE CVE-2024-50026 https://www.cve.org/CVERecord?id=CVE-2024-50026 Référence CVE CVE-2024-50031 https://www.cve.org/CVERecord?id=CVE-2024-50031 Référence CVE CVE-2024-50033 https://www.cve.org/CVERecord?id=CVE-2024-50033 Référence CVE CVE-2024-50035 https://www.cve.org/CVERecord?id=CVE-2024-50035 Référence CVE CVE-2024-50036 https://www.cve.org/CVERecord?id=CVE-2024-50036 Référence CVE CVE-2024-50038 https://www.cve.org/CVERecord?id=CVE-2024-50038 Référence CVE CVE-2024-50039 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-50009 Référence CVE CVE-2024-50012 https://www.cve.org/CVERecord?id=CVE-2024-50012 Référence CVE CVE-2024-50013 https://www.cve.org/CVERecord?id=CVE-2024-50013 Référence CVE CVE-2024-50014 https://www.cve.org/CVERecord?id=CVE-2024-50014 Référence CVE CVE-2024-50015 https://www.cve.org/CVERecord?id=CVE-2024-50015 Référence CVE CVE-2024-50017 https://www.cve.org/CVERecord?id=CVE-2024-50017 Référence CVE CVE-2024-50019 https://www.cve.org/CVERecord?id=CVE-2024-50019 Référence CVE CVE-2024-50020 https://www.cve.org/CVERecord?id=CVE-2024-50020 Référence CVE CVE-2024-50021 https://www.cve.org/CVERecord?id=CVE-2024-50021 Référence CVE CVE-2024-50022 https://www.cve.org/CVERecord?id=CVE-2024-50022 Référence CVE CVE-2024-50023 https://www.cve.org/CVERecord?id=CVE-2024-50023 Référence CVE CVE-2024-50024 https://www.cve.org/CVERecord?id=CVE-2024-50024 Référence CVE CVE-2024-50025 https://www.cve.org/CVERecord?id=CVE-2024-50025 Référence CVE CVE-2024-50026 https://www.cve.org/CVERecord?id=CVE-2024-50026 Référence CVE CVE-2024-50027 https://www.cve.org/CVERecord?id=CVE-2024-50027 Référence CVE CVE-2024-50028 https://www.cve.org/CVERecord?id=CVE-2024-50028 Référence CVE CVE-2024-50031 https://www.cve.org/CVERecord?id=CVE-2024-50031 Référence CVE CVE-2024-50033 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-50007 Référence CVE CVE-2024-50008 https://www.cve.org/CVERecord?id=CVE-2024-50008 Référence CVE CVE-2024-50013 https://www.cve.org/CVERecord?id=CVE-2024-50013 Référence CVE CVE-2024-50014 https://www.cve.org/CVERecord?id=CVE-2024-50014 Référence CVE CVE-2024-50015 https://www.cve.org/CVERecord?id=CVE-2024-50015 Référence CVE CVE-2024-50017 https://www.cve.org/CVERecord?id=CVE-2024-50017 Référence CVE CVE-2024-50019 https://www.cve.org/CVERecord?id=CVE-2024-50019 Référence CVE CVE-2024-50020 https://www.cve.org/CVERecord?id=CVE-2024-50020 Référence CVE CVE-2024-50021 https://www.cve.org/CVERecord?id=CVE-2024-50021 Référence CVE CVE-2024-50022 https://www.cve.org/CVERecord?id=CVE-2024-50022 Référence CVE CVE-2024-50023 https://www.cve.org/CVERecord?id=CVE-2024-50023 Référence CVE CVE-2024-50024 https://www.cve.org/CVERecord?id=CVE-2024-50024 Référence CVE CVE-2024-50025 https://www.cve.org/CVERecord?id=CVE-2024-50025 Référence CVE CVE-2024-50027 https://www.cve.org/CVERecord?id=CVE-2024-50027 Référence CVE CVE-2024-50028 https://www.cve.org/CVERecord?id=CVE-2024-50028 Référence CVE CVE-2024-50031 https://www.cve.org/CVERecord?id=CVE-2024-50031 Référence CVE CVE-2024-50033 https://www.cve.org/CVERecord?id=CVE-2024-50033 Référence CVE CVE-2024-50035 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-011259Linux の 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
Linux: b9b5777f09be84d0de472ded2253d2f5101427f2 < 9c4198dfdca818c5ce19c764d90eabd156bbc6da, b9b5777f09be84d0de472ded2253d2f5101427f2 < b822007e8db341d6f175c645ed79866db501ad86, b9b5777f09be84d0de472ded2253d2f5101427f2 < e877427d218159ac29c9326100920d24330c9ee6, b9b5777f09be84d0de472ded2253d2f5101427f2 < 7fcbd9785d4c17ea533c42f20a9083a83f301fa6, 5.17
Fixed
Linux: < 5.17, 6.1.113 ≤ 6.1.*, 6.6.57 ≤ 6.6.*, 6.11.4 ≤ 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
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 21 Oct 2024 · Last source change 11 May 2026, 20:43 UTC · CWE not yet assigned

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-45239
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

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-45239↗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-50022 · cve.blacktree.nl