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

bpf: Fix re-attachment branch in bpf_tracing_prog_attach

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
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.23% 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.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
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.6.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.76-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.15-1Debian Security Tracker ↗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-26591 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: bpf: Fix re-attachment branch in bpf_tracing_prog_attach
112 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
bpf: Fix re-attachment branch in bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: ? __die+0x20/0x70 ? page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ? asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10 bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30 do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.
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-23853

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix re-attachment branch in bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: <TASK> ? __die+0x20/0x70 ? page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ? asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10 bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30 do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix re-attachment branch in bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: <TASK> ? __die+0x20/0x70 ? page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ? asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10 bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30 do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

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

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix re-attachment branch in bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: <TASK> ? __die+0x20/0x70 ? page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ? asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10 bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30 do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

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

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → NULL Pointer Dereference → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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

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

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

Official authority intelligence

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

BSI · German · WID-SEC-2024-0473Linux Kernel: Mehrere Schwachstellen

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240228Security Bulletin 28 Feb 2024

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

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

rg/CVERecord?id=CVE-2024-1151 Référence CVE CVE-2024-12797 https://www.cve.org/CVERecord?id=CVE-2024-12797 Référence CVE CVE-2024-2004 https://www.cve.org/CVERecord?id=CVE-2024-2004 Référence CVE CVE-2024-22195 https://www.cve.org/CVERecord?id=CVE-2024-22195 Référence CVE CVE-2024-2379 https://www.cve.org/CVERecord?id=CVE-2024-2379 Référence CVE CVE-2024-2398 https://www.cve.org/CVERecord?id=CVE-2024-2398 Référence CVE CVE-2024-2466 https://www.cve.org/CVERecord?id=CVE-2024-2466 Référence CVE CVE-2024-24790 https://www.cve.org/CVERecord?id=CVE-2024-24790 Référence CVE CVE-2024-2511 https://www.cve.org/CVERecord?id=CVE-2024-2511 Référence CVE CVE-2024-26591 https://www.cve.org/CVERecord?id=CVE-2024-26591 Référence CVE CVE-2024-26602 https://www.cve.org/CVERecord?id=CVE-2024-26602 Référence CVE CVE-2024-26603 https://www.cve.org/CVERecord?id=CVE-2024-26603 Référence CVE CVE-2024-26611 https://www.cve.org/CVERecord?id=CVE-2024-26611 Référence CVE CVE-2024-26646 https://www.cve.org/CVERecord?id=CVE-2024-26646 Référence CVE CVE-2024-26782 https://www.cve.org/CVERecord?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=CV

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

ecord?id=CVE-2023-52451 Référence CVE CVE-2023-52464 https://www.cve.org/CVERecord?id=CVE-2023-52464 Référence CVE CVE-2023-52600 https://www.cve.org/CVERecord?id=CVE-2023-52600 Référence CVE CVE-2023-52603 https://www.cve.org/CVERecord?id=CVE-2023-52603 Référence CVE CVE-2023-6915 https://www.cve.org/CVERecord?id=CVE-2023-6915 Référence CVE CVE-2024-0639 https://www.cve.org/CVERecord?id=CVE-2024-0639 Référence CVE CVE-2024-23851 https://www.cve.org/CVERecord?id=CVE-2024-23851 Référence CVE CVE-2024-26581 https://www.cve.org/CVERecord?id=CVE-2024-26581 Référence CVE CVE-2024-26589 https://www.cve.org/CVERecord?id=CVE-2024-26589 Référence CVE CVE-2024-26591 https://www.cve.org/CVERecord?id=CVE-2024-26591 Gestion détaillée du document le 26 avril 2024 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

ecord?id=CVE-2023-52612 Référence CVE CVE-2023-6610 https://www.cve.org/CVERecord?id=CVE-2023-6610 Référence CVE CVE-2024-0607 https://www.cve.org/CVERecord?id=CVE-2024-0607 Référence CVE CVE-2024-22705 https://www.cve.org/CVERecord?id=CVE-2024-22705 Référence CVE CVE-2024-23850 https://www.cve.org/CVERecord?id=CVE-2024-23850 Référence CVE CVE-2024-23851 https://www.cve.org/CVERecord?id=CVE-2024-23851 Référence CVE CVE-2024-24860 https://www.cve.org/CVERecord?id=CVE-2024-24860 Référence CVE CVE-2024-26586 https://www.cve.org/CVERecord?id=CVE-2024-26586 Référence CVE CVE-2024-26589 https://www.cve.org/CVERecord?id=CVE-2024-26589 Référence CVE CVE-2024-26591 https://www.cve.org/CVERecord?id=CVE-2024-26591 Référence CVE CVE-2024-26597 https://www.cve.org/CVERecord?id=CVE-2024-26597 Référence CVE CVE-2024-26598 https://www.cve.org/CVERecord?id=CVE-2024-26598 Référence CVE CVE-2024-26631 https://www.cve.org/CVERecord?id=CVE-2024-26631 Référence CVE CVE-2024-26633 https://www.cve.org/CVERecord?id=CVE-2024-26633 Gestion détaillée du document le 19 avril 2024 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de l

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

cord?id=CVE-2024-0775 Référence CVE CVE-2024-1086 https://www.cve.org/CVERecord?id=CVE-2024-1086 Référence CVE CVE-2024-22705 https://www.cve.org/CVERecord?id=CVE-2024-22705 Référence CVE CVE-2024-23850 https://www.cve.org/CVERecord?id=CVE-2024-23850 Référence CVE CVE-2024-23851 https://www.cve.org/CVERecord?id=CVE-2024-23851 Référence CVE CVE-2024-24855 https://www.cve.org/CVERecord?id=CVE-2024-24855 Référence CVE CVE-2024-24860 https://www.cve.org/CVERecord?id=CVE-2024-24860 Référence CVE CVE-2024-26586 https://www.cve.org/CVERecord?id=CVE-2024-26586 Référence CVE CVE-2024-26589 https://www.cve.org/CVERecord?id=CVE-2024-26589 Référence CVE CVE-2024-26591 https://www.cve.org/CVERecord?id=CVE-2024-26591 Référence CVE CVE-2024-26597 https://www.cve.org/CVERecord?id=CVE-2024-26597 Référence CVE CVE-2024-26598 https://www.cve.org/CVERecord?id=CVE-2024-26598 Référence CVE CVE-2024-26631 https://www.cve.org/CVERecord?id=CVE-2024-26631 Référence CVE CVE-2024-26633 https://www.cve.org/CVERecord?id=CVE-2024-26633 Gestion détaillée du document le 12 avril 2024 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de l

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

Record?id=CVE-2024-0340 Référence CVE CVE-2024-0607 https://www.cve.org/CVERecord?id=CVE-2024-0607 Référence CVE CVE-2024-1151 https://www.cve.org/CVERecord?id=CVE-2024-1151 Référence CVE CVE-2024-23849 https://www.cve.org/CVERecord?id=CVE-2024-23849 Référence CVE CVE-2024-23850 https://www.cve.org/CVERecord?id=CVE-2024-23850 Référence CVE CVE-2024-23851 https://www.cve.org/CVERecord?id=CVE-2024-23851 Référence CVE CVE-2024-26585 https://www.cve.org/CVERecord?id=CVE-2024-26585 Référence CVE CVE-2024-26586 https://www.cve.org/CVERecord?id=CVE-2024-26586 Référence CVE CVE-2024-26589 https://www.cve.org/CVERecord?id=CVE-2024-26589 Référence CVE CVE-2024-26591 https://www.cve.org/CVERecord?id=CVE-2024-26591 Référence CVE CVE-2024-26593 https://www.cve.org/CVERecord?id=CVE-2024-26593 Référence CVE CVE-2024-26595 https://www.cve.org/CVERecord?id=CVE-2024-26595 Référence CVE CVE-2024-26598 https://www.cve.org/CVERecord?id=CVE-2024-26598 Référence CVE CVE-2024-26600 https://www.cve.org/CVERecord?id=CVE-2024-26600 Référence CVE CVE-2024-26602 https://www.cve.org/CVERecord?id=CVE-2024-26602 Référence CVE CVE-2024-26603 https://www.cve.org/CVERecord?id=CVE-2024-26603 Référence CVE CVE-2024-26607 https://www.cve.org/CVERecord?id=CVE-2024-26607 Référence CVE CVE-2024-26622 https://www.cve.org/CVERecord?id=

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

cord?id=CVE-2024-0607 Référence CVE CVE-2024-1151 https://www.cve.org/CVERecord?id=CVE-2024-1151 Référence CVE CVE-2024-23849 https://www.cve.org/CVERecord?id=CVE-2024-23849 Référence CVE CVE-2024-23850 https://www.cve.org/CVERecord?id=CVE-2024-23850 Référence CVE CVE-2024-23851 https://www.cve.org/CVERecord?id=CVE-2024-23851 Référence CVE CVE-2024-25744 https://www.cve.org/CVERecord?id=CVE-2024-25744 Référence CVE CVE-2024-26585 https://www.cve.org/CVERecord?id=CVE-2024-26585 Référence CVE CVE-2024-26586 https://www.cve.org/CVERecord?id=CVE-2024-26586 Référence CVE CVE-2024-26589 https://www.cve.org/CVERecord?id=CVE-2024-26589 Référence CVE CVE-2024-26591 https://www.cve.org/CVERecord?id=CVE-2024-26591 Référence CVE CVE-2024-26593 https://www.cve.org/CVERecord?id=CVE-2024-26593 Référence CVE CVE-2024-26595 https://www.cve.org/CVERecord?id=CVE-2024-26595 Référence CVE CVE-2024-26598 https://www.cve.org/CVERecord?id=CVE-2024-26598 Référence CVE CVE-2024-26602 https://www.cve.org/CVERecord?id=CVE-2024-26602 Référence CVE CVE-2024-26603 https://www.cve.org/CVERecord?id=CVE-2024-26603 Référence CVE CVE-2024-26607 https://www.cve.org/CVERecord?id=CVE-2024-26607 Référence CVE CVE-2024-26622 https://www.cve.org/CVERecord?id=CVE-2024-26622 Gestion détaillée du document le 22 mars 2024 Version initiale

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

VERecord?id=CVE-2024-0607 Référence CVE CVE-2024-0646 https://www.cve.org/CVERecord?id=CVE-2024-0646 Référence CVE CVE-2024-1085 https://www.cve.org/CVERecord?id=CVE-2024-1085 Référence CVE CVE-2024-1086 https://www.cve.org/CVERecord?id=CVE-2024-1086 Référence CVE CVE-2024-23849 https://www.cve.org/CVERecord?id=CVE-2024-23849 Référence CVE CVE-2024-24860 https://www.cve.org/CVERecord?id=CVE-2024-24860 Référence CVE CVE-2024-26581 https://www.cve.org/CVERecord?id=CVE-2024-26581 Référence CVE CVE-2024-26588 https://www.cve.org/CVERecord?id=CVE-2024-26588 Référence CVE CVE-2024-26589 https://www.cve.org/CVERecord?id=CVE-2024-26589 Référence CVE CVE-2024-26591 https://www.cve.org/CVERecord?id=CVE-2024-26591 Référence CVE CVE-2024-26592 https://www.cve.org/CVERecord?id=CVE-2024-26592 Référence CVE CVE-2024-26594 https://www.cve.org/CVERecord?id=CVE-2024-26594 Référence CVE CVE-2024-26597 https://www.cve.org/CVERecord?id=CVE-2024-26597 Référence CVE CVE-2024-26598 https://www.cve.org/CVERecord?id=CVE-2024-26598 Référence CVE CVE-2024-26599 https://www.cve.org/CVERecord?id=CVE-2024-26599 Référence CVE CVE-2024-26600 https://www.cve.org/CVERecord?id=CVE-2024-26600 Référence CVE CVE-2024-26601 https://www.cve.org/CVERecord?id=CVE-2024-26601 Référence CVE CVE-2024-26624 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-002998Linux の Linux Kernel における NULL ポインタデリファレンスに関する脆弱性

Linux の Linux Kernel には、NULL ポインタデリファレンスに関する脆弱性が存在します。

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.
Patch available
Affected
Fixed
Action
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.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 22 Feb 2024 · Last source change 11 May 2026, 20:00 UTC · CWE-476 · NULL Pointer Dereference

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-23853
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-26591 · cve.blacktree.nl