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

net: veth: clear GRO when clearing XDP even when down

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.22% 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.7.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.82-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.9-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.9-1Debian Security Tracker ↗Source updated 6 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-26803 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: net: veth: clear GRO when clearing XDP even when down
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
In the Linux kernel, the following vulnerability has been resolved: net: veth: clear GRO when clearing XDP even when down The Linux kernel CVE team has assigned CVE-2024-26803 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024040404-CVE-2024-26803-9985@gregkh/T
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-24065

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: net: veth: clear GRO when clearing XDP even when down veth sets NETIF_F_GRO automatically when XDP is enabled, because both features use the same NAPI machinery. The logic to clear NETIF_F_GRO sits in veth_disable_xdp() which is called both on ndo_stop and when XDP is turned off. To avoid the flag from being cleared when the device is brought down, the clearing is skipped when IFF_UP is not set. Bringing the device down should indeed not modify its features. Unfortunately, this means that clearing is also skipped when XDP is disabled _while_ the device is down. And there's nothing on the open path to bring the device features back into sync. IOW if user enables XDP, disables it and then brings the device up we'll end up with a stray GRO flag set but no NAPI instances. We don't depend on the GRO flag on the datapath, so the datapath won't crash. We will crash (or hang), however, next time features are sync'ed (either by user via ethtool or peer changing its config). The GRO flag will go away, and veth will try to disable the NAPIs. But the open path never created them since XDP was off, the GRO flag was a stray. If NAPI was initialized before we'll hang in napi_disable(). If it never was we'll crash trying to stop uninitialized hrtimer. Move the GRO flag updates to the XDP enable / disable paths, instead of mixing them with the ndo_open / ndo_close paths.

What

In the Linux kernel, the following vulnerability has been resolved: net: veth: clear GRO when clearing XDP even when down veth sets NETIF_F_GRO automatically when XDP is enabled, because both features use the same NAPI machinery. The logic to clear NETIF_F_GRO sits in veth_disable_xdp() which is called both on ndo_stop and when XDP is turned off. To avoid the flag from being cleared when the device is brought down, the clearing is skipped when IFF_UP is not set. Bringing the device down should indeed not modify its features. Unfortunately, this means that clearing is also skipped when XDP is disabled _while_ the device is down. And there's nothing on the open path to bring the device features back into sync. IOW if user enables XDP, disables it and then brings the device up we'll end up with a stray GRO flag set but no NAPI instances. We don't depend on the GRO flag on the datapath, so the datapath won't crash. We will crash (or hang), however, next time features are sync'ed (either by user via ethtool or peer changing its config). The GRO flag will go away, and veth will try to disable the NAPIs. But the open path never created them since XDP was off, the GRO flag was a stray. If NAPI was initialized before we'll hang in napi_disable(). If it never was we'll crash trying to stop uninitialized hrtimer. Move the GRO flag updates to the XDP enable / disable paths, instead of mixing them with the ndo_open / ndo_close paths.

Why

The product does not properly clean up and remove temporary or supporting resources after they have been used.

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: net: veth: clear GRO when clearing XDP even when down veth sets NETIF_F_GRO automatically when XDP is enabled, because both features use the same NAPI machinery. The logic to clear NETIF_F_GRO sits in veth_disable_xdp() which is called both on ndo_stop and when XDP is turned off. To avoid the flag from being cleared when the device is brought down, the clearing is skipped when IFF_UP is not set. Bringing the device down should indeed not modify its features. Unfortunately, this means that clearing is also skipped when XDP is disabled _while_ the device is down. And there's nothing on the open path to bring the device features back into sync. IOW if user enables XDP, disables it and then brings the device up we'll end up with a stray GRO flag set but no NAPI instances. We don't depend on the GRO flag on the datapath, so the datapath won't crash. We will crash (or hang), however, next time features are sync'ed (either by user via ethtool or peer changing its config). The GRO flag will go away, and veth will try to disable the NAPIs. But the open path never created them since XDP was off, the GRO flag was a stray. If NAPI was initialized before we'll hang in napi_disable(). If it never was we'll crash trying to stop uninitialized hrtimer. Move the GRO flag updates to the XDP enable / disable paths, instead of mixing them with the ndo_open / ndo_close paths.

Why

The product does not properly clean up and remove temporary or supporting resources after they have been used.

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 → Incomplete Cleanup → 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-459 ↗

CWE-459: Incomplete Cleanup. The product does not properly clean up and remove temporary or supporting resources after they have been used.

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-459
A

Official authority intelligence

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

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

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, seine Privilegien eskalieren oder einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240410Security Bulletin 10 Apr 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 10 Apr 2024, published on 10 April 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-26714 Référence CVE CVE-2024-26717 https://www.cve.org/CVERecord?id=CVE-2024-26717 Référence CVE CVE-2024-26721 https://www.cve.org/CVERecord?id=CVE-2024-26721 Référence CVE CVE-2024-26725 https://www.cve.org/CVERecord?id=CVE-2024-26725 Référence CVE CVE-2024-26734 https://www.cve.org/CVERecord?id=CVE-2024-26734 Référence CVE CVE-2024-26742 https://www.cve.org/CVERecord?id=CVE-2024-26742 Référence CVE CVE-2024-26746 https://www.cve.org/CVERecord?id=CVE-2024-26746 Référence CVE CVE-2024-26760 https://www.cve.org/CVERecord?id=CVE-2024-26760 Référence CVE CVE-2024-26761 https://www.cve.org/CVERecord?id=CVE-2024-26761 Référence CVE CVE-2024-26803 https://www.cve.org/CVERecord?id=CVE-2024-26803 Référence CVE CVE-2024-26815 https://www.cve.org/CVERecord?id=CVE-2024-26815 Référence CVE CVE-2024-26818 https://www.cve.org/CVERecord?id=CVE-2024-26818 Référence CVE CVE-2024-26831 https://www.cve.org/CVERecord?id=CVE-2024-26831 Référence CVE CVE-2024-26837 https://www.cve.org/CVERecord?id=CVE-2024-26837 Référence CVE CVE-2024-26838 https://www.cve.org/CVERecord?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=

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

cord?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=CVE-2024-34064 Référence CVE CVE-2024-34069 https://www.cve.org/CVERecord?id=CVE-2024-34069 Référence CVE CVE-2024-35195 https://www.cve.org/CVERecord?id=CVE-2024-35195 Référence CVE CVE-2024-35995 https://www.cve.org/CVERecord?id=CVE-2024-35995 Référence CVE CVE-2024-36015 https://www.cve.org/CVERecord?id=CVE-2024-36015 Référence CVE CVE-2024-36881 https://www.cve.org/CVERecord?id=CVE-2024-36881 Référence CVE CVE-2024-36882 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2024-26735 Référence CVE CVE-2024-26736 https://www.cve.org/CVERecord?id=CVE-2024-26736 Référence CVE CVE-2024-26748 https://www.cve.org/CVERecord?id=CVE-2024-26748 Référence CVE CVE-2024-26782 https://www.cve.org/CVERecord?id=CVE-2024-26782 Référence CVE CVE-2024-26789 https://www.cve.org/CVERecord?id=CVE-2024-26789 Référence CVE CVE-2024-26790 https://www.cve.org/CVERecord?id=CVE-2024-26790 Référence CVE CVE-2024-26792 https://www.cve.org/CVERecord?id=CVE-2024-26792 Référence CVE CVE-2024-26798 https://www.cve.org/CVERecord?id=CVE-2024-26798 Référence CVE CVE-2024-26802 https://www.cve.org/CVERecord?id=CVE-2024-26802 Référence CVE CVE-2024-26803 https://www.cve.org/CVERecord?id=CVE-2024-26803 Référence CVE CVE-2024-26818 https://www.cve.org/CVERecord?id=CVE-2024-26818 Référence CVE CVE-2024-26820 https://www.cve.org/CVERecord?id=CVE-2024-26820 Référence CVE CVE-2024-26822 https://www.cve.org/CVERecord?id=CVE-2024-26822 Référence CVE CVE-2024-26824 https://www.cve.org/CVERecord?id=CVE-2024-26824 Référence CVE CVE-2024-26825 https://www.cve.org/CVERecord?id=CVE-2024-26825 Référence CVE CVE-2024-26826 https://www.cve.org/CVERecord?id=CVE-2024-26826 Référence CVE CVE-2024-26828 https://www.cve.org/CVERecord?id=CVE-2024-26828 Référence CVE CVE-2024-26829 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-26788 Référence CVE CVE-2024-26790 https://www.cve.org/CVERecord?id=CVE-2024-26790 Référence CVE CVE-2024-26791 https://www.cve.org/CVERecord?id=CVE-2024-26791 Référence CVE CVE-2024-26792 https://www.cve.org/CVERecord?id=CVE-2024-26792 Référence CVE CVE-2024-26793 https://www.cve.org/CVERecord?id=CVE-2024-26793 Référence CVE CVE-2024-26795 https://www.cve.org/CVERecord?id=CVE-2024-26795 Référence CVE CVE-2024-26798 https://www.cve.org/CVERecord?id=CVE-2024-26798 Référence CVE CVE-2024-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 Référence CVE CVE-2024-26802 https://www.cve.org/CVERecord?id=CVE-2024-26802 Référence CVE CVE-2024-26803 https://www.cve.org/CVERecord?id=CVE-2024-26803 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26805 https://www.cve.org/CVERecord?id=CVE-2024-26805 Référence CVE CVE-2024-26809 https://www.cve.org/CVERecord?id=CVE-2024-26809 Référence CVE CVE-2024-26810 https://www.cve.org/CVERecord?id=CVE-2024-26810 Référence CVE CVE-2024-26811 https://www.cve.org/CVERecord?id=CVE-2024-26811 Référence CVE CVE-2024-26812 https://www.cve.org/CVERecord?id=CVE-2024-26812 Référence CVE CVE-2024-26813 https://www.cve.org/CVERecord?id=CVE-2024-26813 Référence CVE CVE-2024-26814 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-26735 Référence CVE CVE-2024-26736 https://www.cve.org/CVERecord?id=CVE-2024-26736 Référence CVE CVE-2024-26748 https://www.cve.org/CVERecord?id=CVE-2024-26748 Référence CVE CVE-2024-26782 https://www.cve.org/CVERecord?id=CVE-2024-26782 Référence CVE CVE-2024-26789 https://www.cve.org/CVERecord?id=CVE-2024-26789 Référence CVE CVE-2024-26790 https://www.cve.org/CVERecord?id=CVE-2024-26790 Référence CVE CVE-2024-26792 https://www.cve.org/CVERecord?id=CVE-2024-26792 Référence CVE CVE-2024-26798 https://www.cve.org/CVERecord?id=CVE-2024-26798 Référence CVE CVE-2024-26802 https://www.cve.org/CVERecord?id=CVE-2024-26802 Référence CVE CVE-2024-26803 https://www.cve.org/CVERecord?id=CVE-2024-26803 Référence CVE CVE-2024-26810 https://www.cve.org/CVERecord?id=CVE-2024-26810 Référence CVE CVE-2024-26811 https://www.cve.org/CVERecord?id=CVE-2024-26811 Référence CVE CVE-2024-26812 https://www.cve.org/CVERecord?id=CVE-2024-26812 Référence CVE CVE-2024-26813 https://www.cve.org/CVERecord?id=CVE-2024-26813 Référence CVE CVE-2024-26814 https://www.cve.org/CVERecord?id=CVE-2024-26814 Référence CVE CVE-2024-26816 https://www.cve.org/CVERecord?id=CVE-2024-26816 Référence CVE CVE-2024-26817 https://www.cve.org/CVERecord?id=CVE-2024-26817 Référence CVE CVE-2024-26818 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-26735 Référence CVE CVE-2024-26736 https://www.cve.org/CVERecord?id=CVE-2024-26736 Référence CVE CVE-2024-26748 https://www.cve.org/CVERecord?id=CVE-2024-26748 Référence CVE CVE-2024-26782 https://www.cve.org/CVERecord?id=CVE-2024-26782 Référence CVE CVE-2024-26789 https://www.cve.org/CVERecord?id=CVE-2024-26789 Référence CVE CVE-2024-26790 https://www.cve.org/CVERecord?id=CVE-2024-26790 Référence CVE CVE-2024-26792 https://www.cve.org/CVERecord?id=CVE-2024-26792 Référence CVE CVE-2024-26798 https://www.cve.org/CVERecord?id=CVE-2024-26798 Référence CVE CVE-2024-26802 https://www.cve.org/CVERecord?id=CVE-2024-26802 Référence CVE CVE-2024-26803 https://www.cve.org/CVERecord?id=CVE-2024-26803 Référence CVE CVE-2024-26809 https://www.cve.org/CVERecord?id=CVE-2024-26809 Référence CVE CVE-2024-26810 https://www.cve.org/CVERecord?id=CVE-2024-26810 Référence CVE CVE-2024-26811 https://www.cve.org/CVERecord?id=CVE-2024-26811 Référence CVE CVE-2024-26812 https://www.cve.org/CVERecord?id=CVE-2024-26812 Référence CVE CVE-2024-26813 https://www.cve.org/CVERecord?id=CVE-2024-26813 Référence CVE CVE-2024-26814 https://www.cve.org/CVERecord?id=CVE-2024-26814 Référence CVE CVE-2024-26816 https://www.cve.org/CVERecord?id=CVE-2024-26816 Référence CVE CVE-2024-26817 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-26788 Référence CVE CVE-2024-26790 https://www.cve.org/CVERecord?id=CVE-2024-26790 Référence CVE CVE-2024-26791 https://www.cve.org/CVERecord?id=CVE-2024-26791 Référence CVE CVE-2024-26792 https://www.cve.org/CVERecord?id=CVE-2024-26792 Référence CVE CVE-2024-26793 https://www.cve.org/CVERecord?id=CVE-2024-26793 Référence CVE CVE-2024-26795 https://www.cve.org/CVERecord?id=CVE-2024-26795 Référence CVE CVE-2024-26798 https://www.cve.org/CVERecord?id=CVE-2024-26798 Référence CVE CVE-2024-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 Référence CVE CVE-2024-26802 https://www.cve.org/CVERecord?id=CVE-2024-26802 Référence CVE CVE-2024-26803 https://www.cve.org/CVERecord?id=CVE-2024-26803 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26805 https://www.cve.org/CVERecord?id=CVE-2024-26805 Référence CVE CVE-2024-26809 https://www.cve.org/CVERecord?id=CVE-2024-26809 Référence CVE CVE-2024-26816 https://www.cve.org/CVERecord?id=CVE-2024-26816 Référence CVE CVE-2024-26820 https://www.cve.org/CVERecord?id=CVE-2024-26820 Référence CVE CVE-2024-26833 https://www.cve.org/CVERecord?id=CVE-2024-26833 Référence CVE CVE-2024-26835 https://www.cve.org/CVERecord?id=CVE-2024-26835 Référence CVE CVE-2024-26838 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-26788 Référence CVE CVE-2024-26790 https://www.cve.org/CVERecord?id=CVE-2024-26790 Référence CVE CVE-2024-26791 https://www.cve.org/CVERecord?id=CVE-2024-26791 Référence CVE CVE-2024-26792 https://www.cve.org/CVERecord?id=CVE-2024-26792 Référence CVE CVE-2024-26793 https://www.cve.org/CVERecord?id=CVE-2024-26793 Référence CVE CVE-2024-26795 https://www.cve.org/CVERecord?id=CVE-2024-26795 Référence CVE CVE-2024-26798 https://www.cve.org/CVERecord?id=CVE-2024-26798 Référence CVE CVE-2024-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 Référence CVE CVE-2024-26802 https://www.cve.org/CVERecord?id=CVE-2024-26802 Référence CVE CVE-2024-26803 https://www.cve.org/CVERecord?id=CVE-2024-26803 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26805 https://www.cve.org/CVERecord?id=CVE-2024-26805 Référence CVE CVE-2024-26809 https://www.cve.org/CVERecord?id=CVE-2024-26809 Référence CVE CVE-2024-26810 https://www.cve.org/CVERecord?id=CVE-2024-26810 Référence CVE CVE-2024-26812 https://www.cve.org/CVERecord?id=CVE-2024-26812 Référence CVE CVE-2024-26813 https://www.cve.org/CVERecord?id=CVE-2024-26813 Référence CVE CVE-2024-26814 https://www.cve.org/CVERecord?id=CVE-2024-26814 Référence CVE CVE-2024-26815 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26790 Référence CVE CVE-2024-26791 https://www.cve.org/CVERecord?id=CVE-2024-26791 Référence CVE CVE-2024-26792 https://www.cve.org/CVERecord?id=CVE-2024-26792 Référence CVE CVE-2024-26793 https://www.cve.org/CVERecord?id=CVE-2024-26793 Référence CVE CVE-2024-26795 https://www.cve.org/CVERecord?id=CVE-2024-26795 Référence CVE CVE-2024-26798 https://www.cve.org/CVERecord?id=CVE-2024-26798 Référence CVE CVE-2024-26800 https://www.cve.org/CVERecord?id=CVE-2024-26800 Référence CVE CVE-2024-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 Référence CVE CVE-2024-26802 https://www.cve.org/CVERecord?id=CVE-2024-26802 Référence CVE CVE-2024-26803 https://www.cve.org/CVERecord?id=CVE-2024-26803 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26805 https://www.cve.org/CVERecord?id=CVE-2024-26805 Référence CVE CVE-2024-26809 https://www.cve.org/CVERecord?id=CVE-2024-26809 Référence CVE CVE-2024-26810 https://www.cve.org/CVERecord?id=CVE-2024-26810 Référence CVE CVE-2024-26811 https://www.cve.org/CVERecord?id=CVE-2024-26811 Référence CVE CVE-2024-26812 https://www.cve.org/CVERecord?id=CVE-2024-26812 Référence CVE CVE-2024-26813 https://www.cve.org/CVERecord?id=CVE-2024-26813 Référence CVE CVE-2024-26814 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-021494Linux の 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.
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 4 Apr 2024 · Last source change 11 May 2026, 20:04 UTC · CWE-459 · Incomplete Cleanup

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-24065
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD enriched

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

Material change intelligence

What changed after publication

View recent updates ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-24065↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-26803 · cve.blacktree.nl