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

net: hns3: fix kernel crash when 1588 is received on HIP08 devices

Linux · Linux

7.5HighCVSS 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 11 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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.69% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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: Within 30 daysRemediation target: Within 180 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 11 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.

15 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 11 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.7.12-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.85-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.12-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.12-1Debian Security Tracker ↗Source updated 7 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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-24143

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 11 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: net: hns3: fix kernel crash when 1588 is received on HIP08 devices The HIP08 devices does not register the ptp devices, so the hdev->ptp is NULL, but the hardware can receive 1588 messages, and set the HNS3_RXD_TS_VLD_B bit, so, if match this case, the access of hdev->ptp->flags will cause a kernel crash: [ 5888.946472] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000018 [ 5888.946475] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000018 ... [ 5889.266118] pc : hclge_ptp_get_rx_hwts+0x40/0x170 [hclge] [ 5889.272612] lr : hclge_ptp_get_rx_hwts+0x34/0x170 [hclge] [ 5889.279101] sp : ffff800012c3bc50 [ 5889.283516] x29: ffff800012c3bc50 x28: ffff2040002be040 [ 5889.289927] x27: ffff800009116484 x26: 0000000080007500 [ 5889.296333] x25: 0000000000000000 x24: ffff204001c6f000 [ 5889.302738] x23: ffff204144f53c00 x22: 0000000000000000 [ 5889.309134] x21: 0000000000000000 x20: ffff204004220080 [ 5889.315520] x19: ffff204144f53c00 x18: 0000000000000000 [ 5889.321897] x17: 0000000000000000 x16: 0000000000000000 [ 5889.328263] x15: 0000004000140ec8 x14: 0000000000000000 [ 5889.334617] x13: 0000000000000000 x12: 00000000010011df [ 5889.340965] x11: bbfeff4d22000000 x10: 0000000000000000 [ 5889.347303] x9 : ffff800009402124 x8 : 0200f78811dfbb4d [ 5889.353637] x7 : 2200000000191b01 x6 : ffff208002a7d480 [ 5889.359959] x5 : 0000000000000000 x4 : 0000000000000000 [ 5889.366271] x3 : 0000000000000000 x2 : 0000000000000000 [ 5889.372567] x1 : 0000000000000000 x0 : ffff20400095c080 [ 5889.378857] Call trace: [ 5889.382285] hclge_ptp_get_rx_hwts+0x40/0x170 [hclge] [ 5889.388304] hns3_handle_bdinfo+0x324/0x410 [hns3] [ 5889.394055] hns3_handle_rx_bd+0x60/0x150 [hns3] [ 5889.399624] hns3_clean_rx_ring+0x84/0x170 [hns3] [ 5889.405270] hns3_nic_common_poll+0xa8/0x220 [hns3] [ 5889.411084] napi_poll+0xcc/0x264 [ 5889.415329] net_rx_action+0xd4/0x21c [ 5889.419911] __do_softirq+0x130/0x358 [ 5889.424484] irq_exit+0x134/0x154 [ 5889.428700] __handle_domain_irq+0x88/0xf0 [ 5889.433684] gic_handle_irq+0x78/0x2c0 [ 5889.438319] el1_irq+0xb8/0x140 [ 5889.442354] arch_cpu_idle+0x18/0x40 [ 5889.446816] default_idle_call+0x5c/0x1c0 [ 5889.451714] cpuidle_idle_call+0x174/0x1b0 [ 5889.456692] do_idle+0xc8/0x160 [ 5889.460717] cpu_startup_entry+0x30/0xfc [ 5889.465523] secondary_start_kernel+0x158/0x1ec [ 5889.470936] Code: 97ffab78 f9411c14 91408294 f9457284 (f9400c80) [ 5889.477950] SMP: stopping secondary CPUs [ 5890.514626] SMP: failed to stop secondary CPUs 0-69,71-95 [ 5890.522951] Starting crashdump kernel...

What

In the Linux kernel, the following vulnerability has been resolved: net: hns3: fix kernel crash when 1588 is received on HIP08 devices The HIP08 devices does not register the ptp devices, so the hdev->ptp is NULL, but the hardware can receive 1588 messages, and set the HNS3_RXD_TS_VLD_B bit, so, if match this case, the access of hdev->ptp->flags will cause a kernel crash: [ 5888.946472] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000018 [ 5888.946475] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000018 ... [ 5889.266118] pc : hclge_ptp_get_rx_hwts+0x40/0x170 [hclge] [ 5889.272612] lr : hclge_ptp_get_rx_hwts+0x34/0x170 [hclge] [ 5889.279101] sp : ffff800012c3bc50 [ 5889.283516] x29: ffff800012c3bc50 x28: ffff2040002be040 [ 5889.289927] x27: ffff800009116484 x26: 0000000080007500 [ 5889.296333] x25: 0000000000000000 x24: ffff204001c6f000 [ 5889.302738] x23: ffff204144f53c00 x22: 0000000000000000 [ 5889.309134] x21: 0000000000000000 x20: ffff204004220080 [ 5889.315520] x19: ffff204144f53c00 x18: 0000000000000000 [ 5889.321897] x17: 0000000000000000 x16: 0000000000000000 [ 5889.328263] x15: 0000004000140ec8 x14: 0000000000000000 [ 5889.334617] x13: 0000000000000000 x12: 00000000010011df [ 5889.340965] x11: bbfeff4d22000000 x10: 0000000000000000 [ 5889.347303] x9 : ffff800009402124 x8 : 0200f78811dfbb4d [ 5889.353637] x7 : 2200000000191b01 x6 : ffff208002a7d480 [ 5889.359959] x5 : 0000000000000000 x4 : 0000000000000000 [ 5889.366271] x3 : 0000000000000000 x2 : 0000000000000000 [ 5889.372567] x1 : 0000000000000000 x0 : ffff20400095c080 [ 5889.378857] Call trace: [ 5889.382285] hclge_ptp_get_rx_hwts+0x40/0x170 [hclge] [ 5889.388304] hns3_handle_bdinfo+0x324/0x410 [hns3] [ 5889.394055] hns3_handle_rx_bd+0x60/0x150 [hns3] [ 5889.399624] hns3_clean_rx_ring+0x84/0x170 [hns3] [ 5889.405270] hns3_nic_common_poll+0xa8/0x220 [hns3] [ 5889.411084] napi_poll+0xcc/0x264 [ 5889.415329] net_rx_action+0xd4/0x21c [ 5889.419911] __do_softirq+0x130/0x358 [ 5889.424484] irq_exit+0x134/0x154 [ 5889.428700] __handle_domain_irq+0x88/0xf0 [ 5889.433684] gic_handle_irq+0x78/0x2c0 [ 5889.438319] el1_irq+0xb8/0x140 [ 5889.442354] arch_cpu_idle+0x18/0x40 [ 5889.446816] default_idle_call+0x5c/0x1c0 [ 5889.451714] cpuidle_idle_call+0x174/0x1b0 [ 5889.456692] do_idle+0xc8/0x160 [ 5889.460717] cpu_startup_entry+0x30/0xfc [ 5889.465523] secondary_start_kernel+0x158/0x1ec [ 5889.470936] Code: 97ffab78 f9411c14 91408294 f9457284 (f9400c80) [ 5889.477950] SMP: stopping secondary CPUs [ 5890.514626] SMP: failed to stop secondary CPUs 0-69,71-95 [ 5890.522951] Starting crashdump kernel...

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: net: hns3: fix kernel crash when 1588 is received on HIP08 devices The HIP08 devices does not register the ptp devices, so the hdev->ptp is NULL, but the hardware can receive 1588 messages, and set the HNS3_RXD_TS_VLD_B bit, so, if match this case, the access of hdev->ptp->flags will cause a kernel crash: [ 5888.946472] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000018 [ 5888.946475] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000018 ... [ 5889.266118] pc : hclge_ptp_get_rx_hwts+0x40/0x170 [hclge] [ 5889.272612] lr : hclge_ptp_get_rx_hwts+0x34/0x170 [hclge] [ 5889.279101] sp : ffff800012c3bc50 [ 5889.283516] x29: ffff800012c3bc50 x28: ffff2040002be040 [ 5889.289927] x27: ffff800009116484 x26: 0000000080007500 [ 5889.296333] x25: 0000000000000000 x24: ffff204001c6f000 [ 5889.302738] x23: ffff204144f53c00 x22: 0000000000000000 [ 5889.309134] x21: 0000000000000000 x20: ffff204004220080 [ 5889.315520] x19: ffff204144f53c00 x18: 0000000000000000 [ 5889.321897] x17: 0000000000000000 x16: 0000000000000000 [ 5889.328263] x15: 0000004000140ec8 x14: 0000000000000000 [ 5889.334617] x13: 0000000000000000 x12: 00000000010011df [ 5889.340965] x11: bbfeff4d22000000 x10: 0000000000000000 [ 5889.347303] x9 : ffff800009402124 x8 : 0200f78811dfbb4d [ 5889.353637] x7 : 2200000000191b01 x6 : ffff208002a7d480 [ 5889.359959] x5 : 0000000000000000 x4 : 0000000000000000 [ 5889.366271] x3 : 0000000000000000 x2 : 0000000000000000 [ 5889.372567] x1 : 0000000000000000 x0 : ffff20400095c080 [ 5889.378857] Call trace: [ 5889.382285] hclge_ptp_get_rx_hwts+0x40/0x170 [hclge] [ 5889.388304] hns3_handle_bdinfo+0x324/0x410 [hns3] [ 5889.394055] hns3_handle_rx_bd+0x60/0x150 [hns3] [ 5889.399624] hns3_clean_rx_ring+0x84/0x170 [hns3] [ 5889.405270] hns3_nic_common_poll+0xa8/0x220 [hns3] [ 5889.411084] napi_poll+0xcc/0x264 [ 5889.415329] net_rx_action+0xd4/0x21c [ 5889.419911] __do_softirq+0x130/0x358 [ 5889.424484] irq_exit+0x134/0x154 [ 5889.428700] __handle_domain_irq+0x88/0xf0 [ 5889.433684] gic_handle_irq+0x78/0x2c0 [ 5889.438319] el1_irq+0xb8/0x140 [ 5889.442354] arch_cpu_idle+0x18/0x40 [ 5889.446816] default_idle_call+0x5c/0x1c0 [ 5889.451714] cpuidle_idle_call+0x174/0x1b0 [ 5889.456692] do_idle+0xc8/0x160 [ 5889.460717] cpu_startup_entry+0x30/0xfc [ 5889.465523] secondary_start_kernel+0x158/0x1ec [ 5889.470936] Code: 97ffab78 f9411c14 91408294 f9457284 (f9400c80) [ 5889.477950] SMP: stopping secondary CPUs [ 5890.514626] SMP: failed to stop secondary CPUs 0-69,71-95 [ 5890.522951] Starting crashdump kernel...

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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
a network path → NULL Pointer Dereference → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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:N/AC:L/PR:N/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.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial 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-0920Linux 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-20240424Security Bulletin 24 Apr 2024

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

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

d?id=CVE-2024-26858 Référence CVE CVE-2024-26860 https://www.cve.org/CVERecord?id=CVE-2024-26860 Référence CVE CVE-2024-26861 https://www.cve.org/CVERecord?id=CVE-2024-26861 Référence CVE CVE-2024-26862 https://www.cve.org/CVERecord?id=CVE-2024-26862 Référence CVE CVE-2024-26863 https://www.cve.org/CVERecord?id=CVE-2024-26863 Référence CVE CVE-2024-26866 https://www.cve.org/CVERecord?id=CVE-2024-26866 Référence CVE CVE-2024-26868 https://www.cve.org/CVERecord?id=CVE-2024-26868 Référence CVE CVE-2024-26870 https://www.cve.org/CVERecord?id=CVE-2024-26870 Référence CVE CVE-2024-26878 https://www.cve.org/CVERecord?id=CVE-2024-26878 Référence CVE CVE-2024-26881 https://www.cve.org/CVERecord?id=CVE-2024-26881 Référence CVE CVE-2024-26882 https://www.cve.org/CVERecord?id=CVE-2024-26882 Référence CVE CVE-2024-26883 https://www.cve.org/CVERecord?id=CVE-2024-26883 Référence CVE CVE-2024-26884 https://www.cve.org/CVERecord?id=CVE-2024-26884 Référence CVE CVE-2024-26885 https://www.cve.org/CVERecord?id=CVE-2024-26885 Référence CVE CVE-2024-26889 https://www.cve.org/CVERecord?id=CVE-2024-26889 Référence CVE CVE-2024-26899 https://www.cve.org/CVERecord?id=CVE-2024-26899 Référence CVE CVE-2024-26900 https://www.cve.org/CVERecord?id=CVE-2024-26900 Référence CVE CVE-2024-26901 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-26863 Référence CVE CVE-2024-26870 https://www.cve.org/CVERecord?id=CVE-2024-26870 Référence CVE CVE-2024-26872 https://www.cve.org/CVERecord?id=CVE-2024-26872 Référence CVE CVE-2024-26874 https://www.cve.org/CVERecord?id=CVE-2024-26874 Référence CVE CVE-2024-26875 https://www.cve.org/CVERecord?id=CVE-2024-26875 Référence CVE CVE-2024-26877 https://www.cve.org/CVERecord?id=CVE-2024-26877 Référence CVE CVE-2024-26878 https://www.cve.org/CVERecord?id=CVE-2024-26878 Référence CVE CVE-2024-26879 https://www.cve.org/CVERecord?id=CVE-2024-26879 Référence CVE CVE-2024-26880 https://www.cve.org/CVERecord?id=CVE-2024-26880 Référence CVE CVE-2024-26881 https://www.cve.org/CVERecord?id=CVE-2024-26881 Référence CVE CVE-2024-26882 https://www.cve.org/CVERecord?id=CVE-2024-26882 Référence CVE CVE-2024-26883 https://www.cve.org/CVERecord?id=CVE-2024-26883 Référence CVE CVE-2024-26884 https://www.cve.org/CVERecord?id=CVE-2024-26884 Référence CVE CVE-2024-26885 https://www.cve.org/CVERecord?id=CVE-2024-26885 Référence CVE CVE-2024-26886 https://www.cve.org/CVERecord?id=CVE-2024-26886 Référence CVE CVE-2024-26889 https://www.cve.org/CVERecord?id=CVE-2024-26889 Référence CVE CVE-2024-26891 https://www.cve.org/CVERecord?id=CVE-2024-26891 Référence CVE CVE-2024-26894 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26863 Référence CVE CVE-2024-26870 https://www.cve.org/CVERecord?id=CVE-2024-26870 Référence CVE CVE-2024-26872 https://www.cve.org/CVERecord?id=CVE-2024-26872 Référence CVE CVE-2024-26874 https://www.cve.org/CVERecord?id=CVE-2024-26874 Référence CVE CVE-2024-26875 https://www.cve.org/CVERecord?id=CVE-2024-26875 Référence CVE CVE-2024-26877 https://www.cve.org/CVERecord?id=CVE-2024-26877 Référence CVE CVE-2024-26878 https://www.cve.org/CVERecord?id=CVE-2024-26878 Référence CVE CVE-2024-26879 https://www.cve.org/CVERecord?id=CVE-2024-26879 Référence CVE CVE-2024-26880 https://www.cve.org/CVERecord?id=CVE-2024-26880 Référence CVE CVE-2024-26881 https://www.cve.org/CVERecord?id=CVE-2024-26881 Référence CVE CVE-2024-26882 https://www.cve.org/CVERecord?id=CVE-2024-26882 Référence CVE CVE-2024-26883 https://www.cve.org/CVERecord?id=CVE-2024-26883 Référence CVE CVE-2024-26884 https://www.cve.org/CVERecord?id=CVE-2024-26884 Référence CVE CVE-2024-26885 https://www.cve.org/CVERecord?id=CVE-2024-26885 Référence CVE CVE-2024-26889 https://www.cve.org/CVERecord?id=CVE-2024-26889 Référence CVE CVE-2024-26891 https://www.cve.org/CVERecord?id=CVE-2024-26891 Référence CVE CVE-2024-26894 https://www.cve.org/CVERecord?id=CVE-2024-26894 Référence CVE CVE-2024-26895 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26872 Référence CVE CVE-2024-26873 https://www.cve.org/CVERecord?id=CVE-2024-26873 Référence CVE CVE-2024-26874 https://www.cve.org/CVERecord?id=CVE-2024-26874 Référence CVE CVE-2024-26875 https://www.cve.org/CVERecord?id=CVE-2024-26875 Référence CVE CVE-2024-26876 https://www.cve.org/CVERecord?id=CVE-2024-26876 Référence CVE CVE-2024-26877 https://www.cve.org/CVERecord?id=CVE-2024-26877 Référence CVE CVE-2024-26878 https://www.cve.org/CVERecord?id=CVE-2024-26878 Référence CVE CVE-2024-26879 https://www.cve.org/CVERecord?id=CVE-2024-26879 Référence CVE CVE-2024-26880 https://www.cve.org/CVERecord?id=CVE-2024-26880 Référence CVE CVE-2024-26881 https://www.cve.org/CVERecord?id=CVE-2024-26881 Référence CVE CVE-2024-26882 https://www.cve.org/CVERecord?id=CVE-2024-26882 Référence CVE CVE-2024-26883 https://www.cve.org/CVERecord?id=CVE-2024-26883 Référence CVE CVE-2024-26884 https://www.cve.org/CVERecord?id=CVE-2024-26884 Référence CVE CVE-2024-26885 https://www.cve.org/CVERecord?id=CVE-2024-26885 Référence CVE CVE-2024-26886 https://www.cve.org/CVERecord?id=CVE-2024-26886 Référence CVE CVE-2024-26887 https://www.cve.org/CVERecord?id=CVE-2024-26887 Référence CVE CVE-2024-26888 https://www.cve.org/CVERecord?id=CVE-2024-26888 Référence CVE CVE-2024-26889 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-26862 Référence CVE CVE-2024-26866 https://www.cve.org/CVERecord?id=CVE-2024-26866 Référence CVE CVE-2024-26868 https://www.cve.org/CVERecord?id=CVE-2024-26868 Référence CVE CVE-2024-26870 https://www.cve.org/CVERecord?id=CVE-2024-26870 Référence CVE CVE-2024-26874 https://www.cve.org/CVERecord?id=CVE-2024-26874 Référence CVE CVE-2024-26876 https://www.cve.org/CVERecord?id=CVE-2024-26876 Référence CVE CVE-2024-26877 https://www.cve.org/CVERecord?id=CVE-2024-26877 Référence CVE CVE-2024-26878 https://www.cve.org/CVERecord?id=CVE-2024-26878 Référence CVE CVE-2024-26880 https://www.cve.org/CVERecord?id=CVE-2024-26880 Référence CVE CVE-2024-26881 https://www.cve.org/CVERecord?id=CVE-2024-26881 Référence CVE CVE-2024-26882 https://www.cve.org/CVERecord?id=CVE-2024-26882 Référence CVE CVE-2024-26883 https://www.cve.org/CVERecord?id=CVE-2024-26883 Référence CVE CVE-2024-26884 https://www.cve.org/CVERecord?id=CVE-2024-26884 Référence CVE CVE-2024-26885 https://www.cve.org/CVERecord?id=CVE-2024-26885 Référence CVE CVE-2024-26889 https://www.cve.org/CVERecord?id=CVE-2024-26889 Référence CVE CVE-2024-26894 https://www.cve.org/CVERecord?id=CVE-2024-26894 Référence CVE CVE-2024-26898 https://www.cve.org/CVERecord?id=CVE-2024-26898 Référence CVE CVE-2024-26899 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26861 Référence CVE CVE-2024-26862 https://www.cve.org/CVERecord?id=CVE-2024-26862 Référence CVE CVE-2024-26866 https://www.cve.org/CVERecord?id=CVE-2024-26866 Référence CVE CVE-2024-26872 https://www.cve.org/CVERecord?id=CVE-2024-26872 Référence CVE CVE-2024-26875 https://www.cve.org/CVERecord?id=CVE-2024-26875 Référence CVE CVE-2024-26876 https://www.cve.org/CVERecord?id=CVE-2024-26876 Référence CVE CVE-2024-26877 https://www.cve.org/CVERecord?id=CVE-2024-26877 Référence CVE CVE-2024-26878 https://www.cve.org/CVERecord?id=CVE-2024-26878 Référence CVE CVE-2024-26879 https://www.cve.org/CVERecord?id=CVE-2024-26879 Référence CVE CVE-2024-26881 https://www.cve.org/CVERecord?id=CVE-2024-26881 Référence CVE CVE-2024-26882 https://www.cve.org/CVERecord?id=CVE-2024-26882 Référence CVE CVE-2024-26883 https://www.cve.org/CVERecord?id=CVE-2024-26883 Référence CVE CVE-2024-26884 https://www.cve.org/CVERecord?id=CVE-2024-26884 Référence CVE CVE-2024-26885 https://www.cve.org/CVERecord?id=CVE-2024-26885 Référence CVE CVE-2024-26891 https://www.cve.org/CVERecord?id=CVE-2024-26891 Référence CVE CVE-2024-26893 https://www.cve.org/CVERecord?id=CVE-2024-26893 Référence CVE CVE-2024-26895 https://www.cve.org/CVERecord?id=CVE-2024-26895 Référence CVE CVE-2024-26896 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-003169Linux の 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.
Fix availability varies by product
Affected
Linux: 0bf5eb788512187b744ef7f79de835e6cbe85b9c < 23ec1cec24293f9799c725941677d4e167997265, 0bf5eb788512187b744ef7f79de835e6cbe85b9c < b3cf70472a600bcb2efe24906bc9bc6014d4c6f6, 0bf5eb788512187b744ef7f79de835e6cbe85b9c < f0b5225a7dfc1bf53c98215db8c2f0b4efd3f108, 0bf5eb788512187b744ef7f79de835e6cbe85b9c < b2bb19114c079dcfec1ea46e761f510e30505e70, 0bf5eb788512187b744ef7f79de835e6cbe85b9c < 11b998360d96f6c76f04a95f54b49f24d3c858e4, 0bf5eb788512187b744ef7f79de835e6cbe85b9c < 0fbcf2366ba9888cf02eda23e35fde7f7fcc07c3, 5.14
Fixed
Linux: < 5.14, 5.15.153 ≤ 5.15.*, 6.1.83 ≤ 6.1.*, 6.6.23 ≤ 6.6.*, 6.7.11 ≤ 6.7.*, 6.8.2 ≤ 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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 17 Apr 2024 · Last source change 5 Aug 2026, 11:28 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-24143
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-24143↗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-26881 · cve.blacktree.nl