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

arm64: hibernate: Fix level3 translation fault in swsusp_save()

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 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 severityHighOperational priority:Medium, 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.24% 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 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.9-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.90-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.9-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.9-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-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-intelAffected, 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-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
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-24251

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 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: arm64: hibernate: Fix level3 translation fault in swsusp_save() On arm64 machines, swsusp_save() faults if it attempts to access MEMBLOCK_NOMAP memory ranges. This can be reproduced in QEMU using UEFI when booting with rodata=off debug_pagealloc=off and CONFIG_KFENCE=n: Unable to handle kernel paging request at virtual address ffffff8000000000 Mem abort info: ESR = 0x0000000096000007 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x07: level 3 translation fault Data abort info: ISV = 0, ISS = 0x00000007, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 swapper pgtable: 4k pages, 39-bit VAs, pgdp=00000000eeb0b000 [ffffff8000000000] pgd=180000217fff9803, p4d=180000217fff9803, pud=180000217fff9803, pmd=180000217fff8803, pte=0000000000000000 Internal error: Oops: 0000000096000007 [#1] SMP Internal error: Oops: 0000000096000007 [#1] SMP Modules linked in: xt_multiport ipt_REJECT nf_reject_ipv4 xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter bpfilter rfkill at803x snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg dwmac_generic stmmac_platform snd_hda_codec stmmac joydev pcs_xpcs snd_hda_core phylink ppdev lp parport ramoops reed_solomon ip_tables x_tables nls_iso8859_1 vfat multipath linear amdgpu amdxcp drm_exec gpu_sched drm_buddy hid_generic usbhid hid radeon video drm_suballoc_helper drm_ttm_helper ttm i2c_algo_bit drm_display_helper cec drm_kms_helper drm CPU: 0 PID: 3663 Comm: systemd-sleep Not tainted 6.6.2+ #76 Source Version: 4e22ed63a0a48e7a7cff9b98b7806d8d4add7dc0 Hardware name: Greatwall GW-XXXXXX-XXX/GW-XXXXXX-XXX, BIOS KunLun BIOS V4.0 01/19/2021 pstate: 600003c5 (nZCv DAIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : swsusp_save+0x280/0x538 lr : swsusp_save+0x280/0x538 sp : ffffffa034a3fa40 x29: ffffffa034a3fa40 x28: ffffff8000001000 x27: 0000000000000000 x26: ffffff8001400000 x25: ffffffc08113e248 x24: 0000000000000000 x23: 0000000000080000 x22: ffffffc08113e280 x21: 00000000000c69f2 x20: ffffff8000000000 x19: ffffffc081ae2500 x18: 0000000000000000 x17: 6666662074736420 x16: 3030303030303030 x15: 3038666666666666 x14: 0000000000000b69 x13: ffffff9f89088530 x12: 00000000ffffffea x11: 00000000ffff7fff x10: 00000000ffff7fff x9 : ffffffc08193f0d0 x8 : 00000000000bffe8 x7 : c0000000ffff7fff x6 : 0000000000000001 x5 : ffffffa0fff09dc8 x4 : 0000000000000000 x3 : 0000000000000027 x2 : 0000000000000000 x1 : 0000000000000000 x0 : 000000000000004e Call trace: swsusp_save+0x280/0x538 swsusp_arch_suspend+0x148/0x190 hibernation_snapshot+0x240/0x39c hibernate+0xc4/0x378 state_store+0xf0/0x10c kobj_attr_store+0x14/0x24 The reason is swsusp_save() -> copy_data_pages() -> page_is_saveable() -> kernel_page_present() assuming that a page is always present when can_set_direct_map() is false (all of rodata_full, debug_pagealloc_enabled() and arm64_kfence_can_set_direct_map() false), irrespective of the MEMBLOCK_NOMAP ranges. Such MEMBLOCK_NOMAP regions should not be saved during hibernation. This problem was introduced by changes to the pfn_valid() logic in commit a7d9f306ba70 ("arm64: drop pfn_valid_within() and simplify pfn_valid()"). Similar to other architectures, drop the !can_set_direct_map() check in kernel_page_present() so that page_is_savable() skips such pages. [catalin.marinas@arm.com: rework commit message]

What

In the Linux kernel, the following vulnerability has been resolved: arm64: hibernate: Fix level3 translation fault in swsusp_save() On arm64 machines, swsusp_save() faults if it attempts to access MEMBLOCK_NOMAP memory ranges. This can be reproduced in QEMU using UEFI when booting with rodata=off debug_pagealloc=off and CONFIG_KFENCE=n: Unable to handle kernel paging request at virtual address ffffff8000000000 Mem abort info: ESR = 0x0000000096000007 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x07: level 3 translation fault Data abort info: ISV = 0, ISS = 0x00000007, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 swapper pgtable: 4k pages, 39-bit VAs, pgdp=00000000eeb0b000 [ffffff8000000000] pgd=180000217fff9803, p4d=180000217fff9803, pud=180000217fff9803, pmd=180000217fff8803, pte=0000000000000000 Internal error: Oops: 0000000096000007 [#1] SMP Internal error: Oops: 0000000096000007 [#1] SMP Modules linked in: xt_multiport ipt_REJECT nf_reject_ipv4 xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter bpfilter rfkill at803x snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg dwmac_generic stmmac_platform snd_hda_codec stmmac joydev pcs_xpcs snd_hda_core phylink ppdev lp parport ramoops reed_solomon ip_tables x_tables nls_iso8859_1 vfat multipath linear amdgpu amdxcp drm_exec gpu_sched drm_buddy hid_generic usbhid hid radeon video drm_suballoc_helper drm_ttm_helper ttm i2c_algo_bit drm_display_helper cec drm_kms_helper drm CPU: 0 PID: 3663 Comm: systemd-sleep Not tainted 6.6.2+ #76 Source Version: 4e22ed63a0a48e7a7cff9b98b7806d8d4add7dc0 Hardware name: Greatwall GW-XXXXXX-XXX/GW-XXXXXX-XXX, BIOS KunLun BIOS V4.0 01/19/2021 pstate: 600003c5 (nZCv DAIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : swsusp_save+0x280/0x538 lr : swsusp_save+0x280/0x538 sp : ffffffa034a3fa40 x29: ffffffa034a3fa40 x28: ffffff8000001000 x27: 0000000000000000 x26: ffffff8001400000 x25: ffffffc08113e248 x24: 0000000000000000 x23: 0000000000080000 x22: ffffffc08113e280 x21: 00000000000c69f2 x20: ffffff8000000000 x19: ffffffc081ae2500 x18: 0000000000000000 x17: 6666662074736420 x16: 3030303030303030 x15: 3038666666666666 x14: 0000000000000b69 x13: ffffff9f89088530 x12: 00000000ffffffea x11: 00000000ffff7fff x10: 00000000ffff7fff x9 : ffffffc08193f0d0 x8 : 00000000000bffe8 x7 : c0000000ffff7fff x6 : 0000000000000001 x5 : ffffffa0fff09dc8 x4 : 0000000000000000 x3 : 0000000000000027 x2 : 0000000000000000 x1 : 0000000000000000 x0 : 000000000000004e Call trace: swsusp_save+0x280/0x538 swsusp_arch_suspend+0x148/0x190 hibernation_snapshot+0x240/0x39c hibernate+0xc4/0x378 state_store+0xf0/0x10c kobj_attr_store+0x14/0x24 The reason is swsusp_save() -> copy_data_pages() -> page_is_saveable() -> kernel_page_present() assuming that a page is always present when can_set_direct_map() is false (all of rodata_full, debug_pagealloc_enabled() and arm64_kfence_can_set_direct_map() false), irrespective of the MEMBLOCK_NOMAP ranges. Such MEMBLOCK_NOMAP regions should not be saved during hibernation. This problem was introduced by changes to the pfn_valid() logic in commit a7d9f306ba70 ("arm64: drop pfn_valid_within() and simplify pfn_valid()"). Similar to other architectures, drop the !can_set_direct_map() check in kernel_page_present() so that page_is_savable() skips such pages. [catalin.marinas@arm.com: rework commit message]

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: arm64: hibernate: Fix level3 translation fault in swsusp_save() On arm64 machines, swsusp_save() faults if it attempts to access MEMBLOCK_NOMAP memory ranges. This can be reproduced in QEMU using UEFI when booting with rodata=off debug_pagealloc=off and CONFIG_KFENCE=n: Unable to handle kernel paging request at virtual address ffffff8000000000 Mem abort info: ESR = 0x0000000096000007 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x07: level 3 translation fault Data abort info: ISV = 0, ISS = 0x00000007, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 swapper pgtable: 4k pages, 39-bit VAs, pgdp=00000000eeb0b000 [ffffff8000000000] pgd=180000217fff9803, p4d=180000217fff9803, pud=180000217fff9803, pmd=180000217fff8803, pte=0000000000000000 Internal error: Oops: 0000000096000007 [#1] SMP Internal error: Oops: 0000000096000007 [#1] SMP Modules linked in: xt_multiport ipt_REJECT nf_reject_ipv4 xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter bpfilter rfkill at803x snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg dwmac_generic stmmac_platform snd_hda_codec stmmac joydev pcs_xpcs snd_hda_core phylink ppdev lp parport ramoops reed_solomon ip_tables x_tables nls_iso8859_1 vfat multipath linear amdgpu amdxcp drm_exec gpu_sched drm_buddy hid_generic usbhid hid radeon video drm_suballoc_helper drm_ttm_helper ttm i2c_algo_bit drm_display_helper cec drm_kms_helper drm CPU: 0 PID: 3663 Comm: systemd-sleep Not tainted 6.6.2+ #76 Source Version: 4e22ed63a0a48e7a7cff9b98b7806d8d4add7dc0 Hardware name: Greatwall GW-XXXXXX-XXX/GW-XXXXXX-XXX, BIOS KunLun BIOS V4.0 01/19/2021 pstate: 600003c5 (nZCv DAIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : swsusp_save+0x280/0x538 lr : swsusp_save+0x280/0x538 sp : ffffffa034a3fa40 x29: ffffffa034a3fa40 x28: ffffff8000001000 x27: 0000000000000000 x26: ffffff8001400000 x25: ffffffc08113e248 x24: 0000000000000000 x23: 0000000000080000 x22: ffffffc08113e280 x21: 00000000000c69f2 x20: ffffff8000000000 x19: ffffffc081ae2500 x18: 0000000000000000 x17: 6666662074736420 x16: 3030303030303030 x15: 3038666666666666 x14: 0000000000000b69 x13: ffffff9f89088530 x12: 00000000ffffffea x11: 00000000ffff7fff x10: 00000000ffff7fff x9 : ffffffc08193f0d0 x8 : 00000000000bffe8 x7 : c0000000ffff7fff x6 : 0000000000000001 x5 : ffffffa0fff09dc8 x4 : 0000000000000000 x3 : 0000000000000027 x2 : 0000000000000000 x1 : 0000000000000000 x0 : 000000000000004e Call trace: swsusp_save+0x280/0x538 swsusp_arch_suspend+0x148/0x190 hibernation_snapshot+0x240/0x39c hibernate+0xc4/0x378 state_store+0xf0/0x10c kobj_attr_store+0x14/0x24 The reason is swsusp_save() -> copy_data_pages() -> page_is_saveable() -> kernel_page_present() assuming that a page is always present when can_set_direct_map() is false (all of rodata_full, debug_pagealloc_enabled() and arm64_kfence_can_set_direct_map() false), irrespective of the MEMBLOCK_NOMAP ranges. Such MEMBLOCK_NOMAP regions should not be saved during hibernation. This problem was introduced by changes to the pfn_valid() logic in commit a7d9f306ba70 ("arm64: drop pfn_valid_within() and simplify pfn_valid()"). Similar to other architectures, drop the !can_set_direct_map() check in kernel_page_present() so that page_is_savable() skips such pages. [catalin.marinas@arm.com: rework commit message]

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: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.
A

Official authority intelligence

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

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

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240508Security Bulletin 08 May 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 08 May 2024, published on 8 May 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-26838 Référence CVE CVE-2024-26892 https://www.cve.org/CVERecord?id=CVE-2024-26892 Référence CVE CVE-2024-26899 https://www.cve.org/CVERecord?id=CVE-2024-26899 Référence CVE CVE-2024-26918 https://www.cve.org/CVERecord?id=CVE-2024-26918 Référence CVE CVE-2024-26933 https://www.cve.org/CVERecord?id=CVE-2024-26933 Référence CVE CVE-2024-26953 https://www.cve.org/CVERecord?id=CVE-2024-26953 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26975 https://www.cve.org/CVERecord?id=CVE-2024-26975 Référence CVE CVE-2024-26987 https://www.cve.org/CVERecord?id=CVE-2024-26987 Référence CVE CVE-2024-26989 https://www.cve.org/CVERecord?id=CVE-2024-26989 Référence CVE CVE-2024-26990 https://www.cve.org/CVERecord?id=CVE-2024-26990 Référence CVE CVE-2024-26992 https://www.cve.org/CVERecord?id=CVE-2024-26992 Référence CVE CVE-2024-27003 https://www.cve.org/CVERecord?id=CVE-2024-27003 Référence CVE CVE-2024-27012 https://www.cve.org/CVERecord?id=CVE-2024-27012 Référence CVE CVE-2024-27014 https://www.cve.org/CVERecord?id=CVE-2024-27014 Référence CVE CVE-2024-27015 https://www.cve.org/CVERecord?id=CVE-2024-27015 Référence CVE CVE-2024-27017 https://www.cve.org/CVERecord?id=CVE-2024-27017 Référence CVE CVE-2024-27023 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26970 Référence CVE CVE-2024-26973 https://www.cve.org/CVERecord?id=CVE-2024-26973 Référence CVE CVE-2024-26974 https://www.cve.org/CVERecord?id=CVE-2024-26974 Référence CVE CVE-2024-26976 https://www.cve.org/CVERecord?id=CVE-2024-26976 Référence CVE CVE-2024-26977 https://www.cve.org/CVERecord?id=CVE-2024-26977 Référence CVE CVE-2024-26980 https://www.cve.org/CVERecord?id=CVE-2024-26980 Référence CVE CVE-2024-26981 https://www.cve.org/CVERecord?id=CVE-2024-26981 Référence CVE CVE-2024-26984 https://www.cve.org/CVERecord?id=CVE-2024-26984 Référence CVE CVE-2024-26988 https://www.cve.org/CVERecord?id=CVE-2024-26988 Référence CVE CVE-2024-26989 https://www.cve.org/CVERecord?id=CVE-2024-26989 Référence CVE CVE-2024-26993 https://www.cve.org/CVERecord?id=CVE-2024-26993 Référence CVE CVE-2024-26994 https://www.cve.org/CVERecord?id=CVE-2024-26994 Référence CVE CVE-2024-26996 https://www.cve.org/CVERecord?id=CVE-2024-26996 Référence CVE CVE-2024-26999 https://www.cve.org/CVERecord?id=CVE-2024-26999 Référence CVE CVE-2024-27000 https://www.cve.org/CVERecord?id=CVE-2024-27000 Référence CVE CVE-2024-27001 https://www.cve.org/CVERecord?id=CVE-2024-27001 Référence CVE CVE-2024-27004 https://www.cve.org/CVERecord?id=CVE-2024-27004 Référence CVE CVE-2024-27008 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26973 Référence CVE CVE-2024-26976 https://www.cve.org/CVERecord?id=CVE-2024-26976 Référence CVE CVE-2024-26978 https://www.cve.org/CVERecord?id=CVE-2024-26978 Référence CVE CVE-2024-26981 https://www.cve.org/CVERecord?id=CVE-2024-26981 Référence CVE CVE-2024-26982 https://www.cve.org/CVERecord?id=CVE-2024-26982 Référence CVE CVE-2024-26983 https://www.cve.org/CVERecord?id=CVE-2024-26983 Référence CVE CVE-2024-26984 https://www.cve.org/CVERecord?id=CVE-2024-26984 Référence CVE CVE-2024-26986 https://www.cve.org/CVERecord?id=CVE-2024-26986 Référence CVE CVE-2024-26988 https://www.cve.org/CVERecord?id=CVE-2024-26988 Référence CVE CVE-2024-26989 https://www.cve.org/CVERecord?id=CVE-2024-26989 Référence CVE CVE-2024-26990 https://www.cve.org/CVERecord?id=CVE-2024-26990 Référence CVE CVE-2024-26991 https://www.cve.org/CVERecord?id=CVE-2024-26991 Référence CVE CVE-2024-26992 https://www.cve.org/CVERecord?id=CVE-2024-26992 Référence CVE CVE-2024-26993 https://www.cve.org/CVERecord?id=CVE-2024-26993 Référence CVE CVE-2024-26994 https://www.cve.org/CVERecord?id=CVE-2024-26994 Référence CVE CVE-2024-26995 https://www.cve.org/CVERecord?id=CVE-2024-26995 Référence CVE CVE-2024-26996 https://www.cve.org/CVERecord?id=CVE-2024-26996 Référence CVE CVE-2024-26997 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26980 Référence CVE CVE-2024-26981 https://www.cve.org/CVERecord?id=CVE-2024-26981 Référence CVE CVE-2024-26982 https://www.cve.org/CVERecord?id=CVE-2024-26982 Référence CVE CVE-2024-26983 https://www.cve.org/CVERecord?id=CVE-2024-26983 Référence CVE CVE-2024-26984 https://www.cve.org/CVERecord?id=CVE-2024-26984 Référence CVE CVE-2024-26985 https://www.cve.org/CVERecord?id=CVE-2024-26985 Référence CVE CVE-2024-26986 https://www.cve.org/CVERecord?id=CVE-2024-26986 Référence CVE CVE-2024-26987 https://www.cve.org/CVERecord?id=CVE-2024-26987 Référence CVE CVE-2024-26988 https://www.cve.org/CVERecord?id=CVE-2024-26988 Référence CVE CVE-2024-26989 https://www.cve.org/CVERecord?id=CVE-2024-26989 Référence CVE CVE-2024-26990 https://www.cve.org/CVERecord?id=CVE-2024-26990 Référence CVE CVE-2024-26991 https://www.cve.org/CVERecord?id=CVE-2024-26991 Référence CVE CVE-2024-26992 https://www.cve.org/CVERecord?id=CVE-2024-26992 Référence CVE CVE-2024-26993 https://www.cve.org/CVERecord?id=CVE-2024-26993 Référence CVE CVE-2024-26994 https://www.cve.org/CVERecord?id=CVE-2024-26994 Référence CVE CVE-2024-26995 https://www.cve.org/CVERecord?id=CVE-2024-26995 Référence CVE CVE-2024-26996 https://www.cve.org/CVERecord?id=CVE-2024-26996 Référence CVE CVE-2024-26997 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26980 Référence CVE CVE-2024-26981 https://www.cve.org/CVERecord?id=CVE-2024-26981 Référence CVE CVE-2024-26982 https://www.cve.org/CVERecord?id=CVE-2024-26982 Référence CVE CVE-2024-26983 https://www.cve.org/CVERecord?id=CVE-2024-26983 Référence CVE CVE-2024-26984 https://www.cve.org/CVERecord?id=CVE-2024-26984 Référence CVE CVE-2024-26985 https://www.cve.org/CVERecord?id=CVE-2024-26985 Référence CVE CVE-2024-26986 https://www.cve.org/CVERecord?id=CVE-2024-26986 Référence CVE CVE-2024-26987 https://www.cve.org/CVERecord?id=CVE-2024-26987 Référence CVE CVE-2024-26988 https://www.cve.org/CVERecord?id=CVE-2024-26988 Référence CVE CVE-2024-26989 https://www.cve.org/CVERecord?id=CVE-2024-26989 Référence CVE CVE-2024-26990 https://www.cve.org/CVERecord?id=CVE-2024-26990 Référence CVE CVE-2024-26991 https://www.cve.org/CVERecord?id=CVE-2024-26991 Référence CVE CVE-2024-26992 https://www.cve.org/CVERecord?id=CVE-2024-26992 Référence CVE CVE-2024-26993 https://www.cve.org/CVERecord?id=CVE-2024-26993 Référence CVE CVE-2024-26994 https://www.cve.org/CVERecord?id=CVE-2024-26994 Référence CVE CVE-2024-26995 https://www.cve.org/CVERecord?id=CVE-2024-26995 Référence CVE CVE-2024-26996 https://www.cve.org/CVERecord?id=CVE-2024-26996 Référence CVE CVE-2024-26997 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26980 Référence CVE CVE-2024-26981 https://www.cve.org/CVERecord?id=CVE-2024-26981 Référence CVE CVE-2024-26982 https://www.cve.org/CVERecord?id=CVE-2024-26982 Référence CVE CVE-2024-26983 https://www.cve.org/CVERecord?id=CVE-2024-26983 Référence CVE CVE-2024-26984 https://www.cve.org/CVERecord?id=CVE-2024-26984 Référence CVE CVE-2024-26985 https://www.cve.org/CVERecord?id=CVE-2024-26985 Référence CVE CVE-2024-26986 https://www.cve.org/CVERecord?id=CVE-2024-26986 Référence CVE CVE-2024-26987 https://www.cve.org/CVERecord?id=CVE-2024-26987 Référence CVE CVE-2024-26988 https://www.cve.org/CVERecord?id=CVE-2024-26988 Référence CVE CVE-2024-26989 https://www.cve.org/CVERecord?id=CVE-2024-26989 Référence CVE CVE-2024-26990 https://www.cve.org/CVERecord?id=CVE-2024-26990 Référence CVE CVE-2024-26991 https://www.cve.org/CVERecord?id=CVE-2024-26991 Référence CVE CVE-2024-26992 https://www.cve.org/CVERecord?id=CVE-2024-26992 Référence CVE CVE-2024-26993 https://www.cve.org/CVERecord?id=CVE-2024-26993 Référence CVE CVE-2024-26994 https://www.cve.org/CVERecord?id=CVE-2024-26994 Référence CVE CVE-2024-26995 https://www.cve.org/CVERecord?id=CVE-2024-26995 Référence CVE CVE-2024-26996 https://www.cve.org/CVERecord?id=CVE-2024-26996 Référence CVE CVE-2024-26997 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26977 Référence CVE CVE-2024-26978 https://www.cve.org/CVERecord?id=CVE-2024-26978 Référence CVE CVE-2024-26979 https://www.cve.org/CVERecord?id=CVE-2024-26979 Référence CVE CVE-2024-26981 https://www.cve.org/CVERecord?id=CVE-2024-26981 Référence CVE CVE-2024-26982 https://www.cve.org/CVERecord?id=CVE-2024-26982 Référence CVE CVE-2024-26983 https://www.cve.org/CVERecord?id=CVE-2024-26983 Référence CVE CVE-2024-26984 https://www.cve.org/CVERecord?id=CVE-2024-26984 Référence CVE CVE-2024-26986 https://www.cve.org/CVERecord?id=CVE-2024-26986 Référence CVE CVE-2024-26988 https://www.cve.org/CVERecord?id=CVE-2024-26988 Référence CVE CVE-2024-26989 https://www.cve.org/CVERecord?id=CVE-2024-26989 Référence CVE CVE-2024-26990 https://www.cve.org/CVERecord?id=CVE-2024-26990 Référence CVE CVE-2024-26991 https://www.cve.org/CVERecord?id=CVE-2024-26991 Référence CVE CVE-2024-26992 https://www.cve.org/CVERecord?id=CVE-2024-26992 Référence CVE CVE-2024-26993 https://www.cve.org/CVERecord?id=CVE-2024-26993 Référence CVE CVE-2024-26994 https://www.cve.org/CVERecord?id=CVE-2024-26994 Référence CVE CVE-2024-26995 https://www.cve.org/CVERecord?id=CVE-2024-26995 Référence CVE CVE-2024-26996 https://www.cve.org/CVERecord?id=CVE-2024-26996 Référence CVE CVE-2024-26997 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26943 Référence CVE CVE-2024-26957 https://www.cve.org/CVERecord?id=CVE-2024-26957 Référence CVE CVE-2024-26958 https://www.cve.org/CVERecord?id=CVE-2024-26958 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26974 https://www.cve.org/CVERecord?id=CVE-2024-26974 Référence CVE CVE-2024-26977 https://www.cve.org/CVERecord?id=CVE-2024-26977 Référence CVE CVE-2024-26979 https://www.cve.org/CVERecord?id=CVE-2024-26979 Référence CVE CVE-2024-26984 https://www.cve.org/CVERecord?id=CVE-2024-26984 Référence CVE CVE-2024-26988 https://www.cve.org/CVERecord?id=CVE-2024-26988 Référence CVE CVE-2024-26989 https://www.cve.org/CVERecord?id=CVE-2024-26989 Référence CVE CVE-2024-26994 https://www.cve.org/CVERecord?id=CVE-2024-26994 Référence CVE CVE-2024-26996 https://www.cve.org/CVERecord?id=CVE-2024-26996 Référence CVE CVE-2024-26997 https://www.cve.org/CVERecord?id=CVE-2024-26997 Référence CVE CVE-2024-26999 https://www.cve.org/CVERecord?id=CVE-2024-26999 Référence CVE CVE-2024-27000 https://www.cve.org/CVERecord?id=CVE-2024-27000 Référence CVE CVE-2024-27001 https://www.cve.org/CVERecord?id=CVE-2024-27001 Référence CVE CVE-2024-27004 https://www.cve.org/CVERecord?id=CVE-2024-27004 Référence CVE CVE-2024-27008 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26976 Référence CVE CVE-2024-26978 https://www.cve.org/CVERecord?id=CVE-2024-26978 Référence CVE CVE-2024-26979 https://www.cve.org/CVERecord?id=CVE-2024-26979 Référence CVE CVE-2024-26980 https://www.cve.org/CVERecord?id=CVE-2024-26980 Référence CVE CVE-2024-26981 https://www.cve.org/CVERecord?id=CVE-2024-26981 Référence CVE CVE-2024-26983 https://www.cve.org/CVERecord?id=CVE-2024-26983 Référence CVE CVE-2024-26984 https://www.cve.org/CVERecord?id=CVE-2024-26984 Référence CVE CVE-2024-26987 https://www.cve.org/CVERecord?id=CVE-2024-26987 Référence CVE CVE-2024-26988 https://www.cve.org/CVERecord?id=CVE-2024-26988 Référence CVE CVE-2024-26989 https://www.cve.org/CVERecord?id=CVE-2024-26989 Référence CVE CVE-2024-26992 https://www.cve.org/CVERecord?id=CVE-2024-26992 Référence CVE CVE-2024-26993 https://www.cve.org/CVERecord?id=CVE-2024-26993 Référence CVE CVE-2024-26994 https://www.cve.org/CVERecord?id=CVE-2024-26994 Référence CVE CVE-2024-26996 https://www.cve.org/CVERecord?id=CVE-2024-26996 Référence CVE CVE-2024-26997 https://www.cve.org/CVERecord?id=CVE-2024-26997 Référence CVE CVE-2024-26999 https://www.cve.org/CVERecord?id=CVE-2024-26999 Référence CVE CVE-2024-27000 https://www.cve.org/CVERecord?id=CVE-2024-27000 Référence CVE CVE-2024-27001 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-015447Linux の 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: a7d9f306ba7052056edf9ccae596aeb400226af8 < 813f5213f2c612dc800054859aaa396ec8ad7069, a7d9f306ba7052056edf9ccae596aeb400226af8 < f7e71a7cf399f53ff9fc314ca3836dc913b05bd6, a7d9f306ba7052056edf9ccae596aeb400226af8 < 31f815cb436082e72d34ed2e8a182140a73ebdf4, a7d9f306ba7052056edf9ccae596aeb400226af8 < 022b19ebc31cce369c407617041a3db810db23b3, a7d9f306ba7052056edf9ccae596aeb400226af8 < 50449ca66cc5a8cbc64749cf4b9f3d3fc5f4b457, 5.14
Fixed
Linux: < 5.14, 5.15.157 ≤ 5.15.*, 6.1.88 ≤ 6.1.*, 6.6.29 ≤ 6.6.*, 6.8.8 ≤ 6.8.*, 6.9 ≤ *
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 1 May 2024 · Last source change 11 May 2026, 20:08 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-24251
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
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-26989 · cve.blacktree.nl