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

net: ip_tunnel: prevent perpetual headroom growth

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 12 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.25% 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.

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 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.82-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.9-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.

3 current
CVE-2024-26804 · CSAF 2.0 · revision 101 · interimSUSE Product Security TeamCVE-2024-26804
356 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Enterprise Storage 7.1
  • kernel-default-devel as component of SUSE Enterprise Storage 7.1
  • kernel-devel as component of SUSE Enterprise Storage 7.1
  • kernel-macros as component of SUSE Enterprise Storage 7.1
  • kernel-source as component of SUSE Enterprise Storage 7.1
  • reiserfs-kmp-default as component of SUSE Enterprise Storage 7.1
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: net: ip_tunnel: prevent perpetual headroom growth syzkaller triggered following kasan splat: BUG: KASAN: use-after-free in __skb_flow_dissect+0x19d1/0x7a50 net/core/flow_dissector.c:1170 Read of size 1 at addr ffff88812fb4000e by task syz-executor183/5191 [..] kasan_report+0xda/0x110 mm/kasan/report.c:588 __skb_flow_dissect+0x19d1/0x7a50 net/core/flow_dissector.c:1170 skb_flow_dissect_flow_keys include/linux/skbuff.h:1514 [inline] ___skb_get_hash net/core/flow_dissector.c:1791 [inline] __skb_get_hash+0xc7/0x540 net/core/flow_dissector.c:1856 skb_get_hash include/linux/skbuff.h:1556 [inline] ip_tunnel_xmit+0x1855/0x33c0 net/ipv4/ip_tunnel.c:748 ipip_tunnel_xmit+0x3cc/0x4e0 net/ipv4/ipip.c:308 __netdev_start_xmit include/linux/netdevice.h:4940 [inline] netdev_start_xmit include/linux/netdevice.h:4954 [inline] xmit_one net/core/dev.c:3548 [inline] dev_hard_start_xmit+0x13d/0x6d0 net/core/dev.c:3564 __dev_queue_xmit+0x7c1/0x3d60 net/core/dev.c:4349 dev_queue_xmit include/linux/netdevice.h:3134 [inline] neigh_connected_output+0x42c/0x5d0 net/core/neighbour.c:1592 ... ip_finish_output2+0x833/0x2550 net/ipv4/ip_output.c:235 ip_finish_output+0x31/0x310 net/ipv4/ip_output.c:323 .. iptunnel_xmit+0x5b4/0x9b0 net/ipv4/ip_tunnel_core.c:82 ip_tunnel_xmit+0x1dbc/0x33c0 net/ipv4/ip_tunnel.c:831 ipgre_xmit+0x4a1/0x980 net/ipv4/ip_gre.c:665 __netdev_start_xmit include/linux/netdevice.h:4940 [inline] netdev_start_xmit include/linux/netdevice.h:4954 [inline] xmit_one net/core/dev.c:3548 [inline] dev_hard_start_xmit+0x13d/0x6d0 net/core/dev.c:3564 ... The splat occurs because skb->data points past skb->head allocated area. This is because neigh layer does: __skb_pull(skb, skb_network_offset(skb)); ... but skb_network_offset() returns a negative offset and __skb_pull() arg is unsigned. IOW, we skb->data gets "adjusted" by a huge value. The negative value is returned because skb->head and skb->data distance is more than 64k and skb->network_header (u16) has wrapped around. The bug is in the ip_tunnel infrastructure, which can cause dev->needed_headroom to increment ad infinitum. The syzkaller reproducer consists of packets getting routed via a gre tunnel, and route of gre encapsulated packets pointing at another (ipip) tunnel. The ipip encapsulation finds gre0 as next output device. This results in the following pattern: 1). First packet is to be sent out via gre0. Route lookup found an output device, ipip0. 2). ip_tunnel_xmit for gre0 bumps gre0->needed_headroom based on the future output device, rt.dev->needed_headroom (ipip0). 3). ip output / start_xmit moves skb on to ipip0. which runs the same code path again (xmit recursion). 4). Routing step for the post-gre0-encap packet finds gre0 as output device to use for ipip0 encapsulated packet. tunl0->needed_headroom is then incremented based on the (already bumped) gre0 device headroom. This repeats for every future packet: gre0->needed_headroom gets inflated because previous packets' ipip0 step incremented rt->dev (gre0) headroom, and ipip0 incremented because gre0 needed_headroom was increased. For each subsequent packet, gre/ipip0->needed_headroom grows until post-expand-head reallocations result in a skb->head/data distance of more than 64k. Once that happens, skb->network_header (u16) wraps around when pskb_expand_head tries to make sure that skb_network_offset() is unchanged after the headroom expansion/reallocation. After this skb_network_offset(skb) returns a different (and negative) result post headroom expansion. The next trip to neigh layer (or anything else that would __skb_pull the network header) makes skb->data point to a memory location outside skb->head area. v2: Cap the needed_headroom update to an arbitarily chosen upperlimit to prevent perpetual increase instead of dropping the headroom increment completely.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2024-26804 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: net: ip_tunnel: prevent perpetual headroom growth
64 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
A use-after-free flaw was found in the Linux kernel’s ip_tunnel functionality when a user uses the ip_tunnel infrastructure. This flaw allows a local user to crash the system.
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.
SSA-613116 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-613116: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.1
3 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
In the Linux kernel, the following vulnerability has been resolved: net: ip_tunnel: prevent perpetual headroom growth
Remediation
No remediation text is recorded.
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-24066

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 actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net: ip_tunnel: prevent perpetual headroom growth syzkaller triggered following kasan splat: BUG: KASAN: use-after-free in __skb_flow_dissect+0x19d1/0x7a50 net/core/flow_dissector.c:1170 Read of size 1 at addr ffff88812fb4000e by task syz-executor183/5191 [..] kasan_report+0xda/0x110 mm/kasan/report.c:588 __skb_flow_dissect+0x19d1/0x7a50 net/core/flow_dissector.c:1170 skb_flow_dissect_flow_keys include/linux/skbuff.h:1514 [inline] ___skb_get_hash net/core/flow_dissector.c:1791 [inline] __skb_get_hash+0xc7/0x540 net/core/flow_dissector.c:1856 skb_get_hash include/linux/skbuff.h:1556 [inline] ip_tunnel_xmit+0x1855/0x33c0 net/ipv4/ip_tunnel.c:748 ipip_tunnel_xmit+0x3cc/0x4e0 net/ipv4/ipip.c:308 __netdev_start_xmit include/linux/netdevice.h:4940 [inline] netdev_start_xmit include/linux/netdevice.h:4954 [inline] xmit_one net/core/dev.c:3548 [inline] dev_hard_start_xmit+0x13d/0x6d0 net/core/dev.c:3564 __dev_queue_xmit+0x7c1/0x3d60 net/core/dev.c:4349 dev_queue_xmit include/linux/netdevice.h:3134 [inline] neigh_connected_output+0x42c/0x5d0 net/core/neighbour.c:1592 ... ip_finish_output2+0x833/0x2550 net/ipv4/ip_output.c:235 ip_finish_output+0x31/0x310 net/ipv4/ip_output.c:323 .. iptunnel_xmit+0x5b4/0x9b0 net/ipv4/ip_tunnel_core.c:82 ip_tunnel_xmit+0x1dbc/0x33c0 net/ipv4/ip_tunnel.c:831 ipgre_xmit+0x4a1/0x980 net/ipv4/ip_gre.c:665 __netdev_start_xmit include/linux/netdevice.h:4940 [inline] netdev_start_xmit include/linux/netdevice.h:4954 [inline] xmit_one net/core/dev.c:3548 [inline] dev_hard_start_xmit+0x13d/0x6d0 net/core/dev.c:3564 ... The splat occurs because skb->data points past skb->head allocated area. This is because neigh layer does: __skb_pull(skb, skb_network_offset(skb)); ... but skb_network_offset() returns a negative offset and __skb_pull() arg is unsigned. IOW, we skb->data gets "adjusted" by a huge value. The negative value is returned because skb->head and skb->data distance is more than 64k and skb->network_header (u16) has wrapped around. The bug is in the ip_tunnel infrastructure, which can cause dev->needed_headroom to increment ad infinitum. The syzkaller reproducer consists of packets getting routed via a gre tunnel, and route of gre encapsulated packets pointing at another (ipip) tunnel. The ipip encapsulation finds gre0 as next output device. This results in the following pattern: 1). First packet is to be sent out via gre0. Route lookup found an output device, ipip0. 2). ip_tunnel_xmit for gre0 bumps gre0->needed_headroom based on the future output device, rt.dev->needed_headroom (ipip0). 3). ip output / start_xmit moves skb on to ipip0. which runs the same code path again (xmit recursion). 4). Routing step for the post-gre0-encap packet finds gre0 as output device to use for ipip0 encapsulated packet. tunl0->needed_headroom is then incremented based on the (already bumped) gre0 device headroom. This repeats for every future packet: gre0->needed_headroom gets inflated because previous packets' ipip0 step incremented rt->dev (gre0) headroom, and ipip0 incremented because gre0 needed_headroom was increased. For each subsequent packet, gre/ipip0->needed_headroom grows until post-expand-head reallocations result in a skb->head/data distance of more than 64k. Once that happens, skb->network_header (u16) wraps around when pskb_expand_head tries to make sure that skb_network_offset() is unchanged after the headroom expansion/reallocation. After this skb_network_offset(skb) returns a different (and negative) result post headroom expansion. The next trip to neigh layer (or anything else that would __skb_pull the network header) makes skb->data point to a memory location outside skb->head area. v2: Cap the needed_headroom update to an arbitarily chosen upperlimit to prevent perpetual increase instead of dropping the headroom increment completely.

What

In the Linux kernel, the following vulnerability has been resolved: net: ip_tunnel: prevent perpetual headroom growth syzkaller triggered following kasan splat: BUG: KASAN: use-after-free in __skb_flow_dissect+0x19d1/0x7a50 net/core/flow_dissector.c:1170 Read of size 1 at addr ffff88812fb4000e by task syz-executor183/5191 [..] kasan_report+0xda/0x110 mm/kasan/report.c:588 __skb_flow_dissect+0x19d1/0x7a50 net/core/flow_dissector.c:1170 skb_flow_dissect_flow_keys include/linux/skbuff.h:1514 [inline] ___skb_get_hash net/core/flow_dissector.c:1791 [inline] __skb_get_hash+0xc7/0x540 net/core/flow_dissector.c:1856 skb_get_hash include/linux/skbuff.h:1556 [inline] ip_tunnel_xmit+0x1855/0x33c0 net/ipv4/ip_tunnel.c:748 ipip_tunnel_xmit+0x3cc/0x4e0 net/ipv4/ipip.c:308 __netdev_start_xmit include/linux/netdevice.h:4940 [inline] netdev_start_xmit include/linux/netdevice.h:4954 [inline] xmit_one net/core/dev.c:3548 [inline] dev_hard_start_xmit+0x13d/0x6d0 net/core/dev.c:3564 __dev_queue_xmit+0x7c1/0x3d60 net/core/dev.c:4349 dev_queue_xmit include/linux/netdevice.h:3134 [inline] neigh_connected_output+0x42c/0x5d0 net/core/neighbour.c:1592 ... ip_finish_output2+0x833/0x2550 net/ipv4/ip_output.c:235 ip_finish_output+0x31/0x310 net/ipv4/ip_output.c:323 .. iptunnel_xmit+0x5b4/0x9b0 net/ipv4/ip_tunnel_core.c:82 ip_tunnel_xmit+0x1dbc/0x33c0 net/ipv4/ip_tunnel.c:831 ipgre_xmit+0x4a1/0x980 net/ipv4/ip_gre.c:665 __netdev_start_xmit include/linux/netdevice.h:4940 [inline] netdev_start_xmit include/linux/netdevice.h:4954 [inline] xmit_one net/core/dev.c:3548 [inline] dev_hard_start_xmit+0x13d/0x6d0 net/core/dev.c:3564 ... The splat occurs because skb->data points past skb->head allocated area. This is because neigh layer does: __skb_pull(skb, skb_network_offset(skb)); ... but skb_network_offset() returns a negative offset and __skb_pull() arg is unsigned. IOW, we skb->data gets "adjusted" by a huge value. The negative value is returned because skb->head and skb->data distance is more than 64k and skb->network_header (u16) has wrapped around. The bug is in the ip_tunnel infrastructure, which can cause dev->needed_headroom to increment ad infinitum. The syzkaller reproducer consists of packets getting routed via a gre tunnel, and route of gre encapsulated packets pointing at another (ipip) tunnel. The ipip encapsulation finds gre0 as next output device. This results in the following pattern: 1). First packet is to be sent out via gre0. Route lookup found an output device, ipip0. 2). ip_tunnel_xmit for gre0 bumps gre0->needed_headroom based on the future output device, rt.dev->needed_headroom (ipip0). 3). ip output / start_xmit moves skb on to ipip0. which runs the same code path again (xmit recursion). 4). Routing step for the post-gre0-encap packet finds gre0 as output device to use for ipip0 encapsulated packet. tunl0->needed_headroom is then incremented based on the (already bumped) gre0 device headroom. This repeats for every future packet: gre0->needed_headroom gets inflated because previous packets' ipip0 step incremented rt->dev (gre0) headroom, and ipip0 incremented because gre0 needed_headroom was increased. For each subsequent packet, gre/ipip0->needed_headroom grows until post-expand-head reallocations result in a skb->head/data distance of more than 64k. Once that happens, skb->network_header (u16) wraps around when pskb_expand_head tries to make sure that skb_network_offset() is unchanged after the headroom expansion/reallocation. After this skb_network_offset(skb) returns a different (and negative) result post headroom expansion. The next trip to neigh layer (or anything else that would __skb_pull the network header) makes skb->data point to a memory location outside skb->head area. v2: Cap the needed_headroom update to an arbitarily chosen upperlimit to prevent perpetual increase instead of dropping the headroom increment completely.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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: net: ip_tunnel: prevent perpetual headroom growth syzkaller triggered following kasan splat: BUG: KASAN: use-after-free in __skb_flow_dissect+0x19d1/0x7a50 net/core/flow_dissector.c:1170 Read of size 1 at addr ffff88812fb4000e by task syz-executor183/5191 [..] kasan_report+0xda/0x110 mm/kasan/report.c:588 __skb_flow_dissect+0x19d1/0x7a50 net/core/flow_dissector.c:1170 skb_flow_dissect_flow_keys include/linux/skbuff.h:1514 [inline] ___skb_get_hash net/core/flow_dissector.c:1791 [inline] __skb_get_hash+0xc7/0x540 net/core/flow_dissector.c:1856 skb_get_hash include/linux/skbuff.h:1556 [inline] ip_tunnel_xmit+0x1855/0x33c0 net/ipv4/ip_tunnel.c:748 ipip_tunnel_xmit+0x3cc/0x4e0 net/ipv4/ipip.c:308 __netdev_start_xmit include/linux/netdevice.h:4940 [inline] netdev_start_xmit include/linux/netdevice.h:4954 [inline] xmit_one net/core/dev.c:3548 [inline] dev_hard_start_xmit+0x13d/0x6d0 net/core/dev.c:3564 __dev_queue_xmit+0x7c1/0x3d60 net/core/dev.c:4349 dev_queue_xmit include/linux/netdevice.h:3134 [inline] neigh_connected_output+0x42c/0x5d0 net/core/neighbour.c:1592 ... ip_finish_output2+0x833/0x2550 net/ipv4/ip_output.c:235 ip_finish_output+0x31/0x310 net/ipv4/ip_output.c:323 .. iptunnel_xmit+0x5b4/0x9b0 net/ipv4/ip_tunnel_core.c:82 ip_tunnel_xmit+0x1dbc/0x33c0 net/ipv4/ip_tunnel.c:831 ipgre_xmit+0x4a1/0x980 net/ipv4/ip_gre.c:665 __netdev_start_xmit include/linux/netdevice.h:4940 [inline] netdev_start_xmit include/linux/netdevice.h:4954 [inline] xmit_one net/core/dev.c:3548 [inline] dev_hard_start_xmit+0x13d/0x6d0 net/core/dev.c:3564 ... The splat occurs because skb->data points past skb->head allocated area. This is because neigh layer does: __skb_pull(skb, skb_network_offset(skb)); ... but skb_network_offset() returns a negative offset and __skb_pull() arg is unsigned. IOW, we skb->data gets "adjusted" by a huge value. The negative value is returned because skb->head and skb->data distance is more than 64k and skb->network_header (u16) has wrapped around. The bug is in the ip_tunnel infrastructure, which can cause dev->needed_headroom to increment ad infinitum. The syzkaller reproducer consists of packets getting routed via a gre tunnel, and route of gre encapsulated packets pointing at another (ipip) tunnel. The ipip encapsulation finds gre0 as next output device. This results in the following pattern: 1). First packet is to be sent out via gre0. Route lookup found an output device, ipip0. 2). ip_tunnel_xmit for gre0 bumps gre0->needed_headroom based on the future output device, rt.dev->needed_headroom (ipip0). 3). ip output / start_xmit moves skb on to ipip0. which runs the same code path again (xmit recursion). 4). Routing step for the post-gre0-encap packet finds gre0 as output device to use for ipip0 encapsulated packet. tunl0->needed_headroom is then incremented based on the (already bumped) gre0 device headroom. This repeats for every future packet: gre0->needed_headroom gets inflated because previous packets' ipip0 step incremented rt->dev (gre0) headroom, and ipip0 incremented because gre0 needed_headroom was increased. For each subsequent packet, gre/ipip0->needed_headroom grows until post-expand-head reallocations result in a skb->head/data distance of more than 64k. Once that happens, skb->network_header (u16) wraps around when pskb_expand_head tries to make sure that skb_network_offset() is unchanged after the headroom expansion/reallocation. After this skb_network_offset(skb) returns a different (and negative) result post headroom expansion. The next trip to neigh layer (or anything else that would __skb_pull the network header) makes skb->data point to a memory location outside skb->head area. v2: Cap the needed_headroom update to an arbitarily chosen upperlimit to prevent perpetual increase instead of dropping the headroom increment completely.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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 → Use After Free → 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: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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.
CWE-416
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-1905IBM QRadar SIEM: Mehrere Schwachstellen

Ein entfernter, anonymer oder lokaler Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, eine Man-in-the-Middle-Situation zu schaffen, Sicherheitsmaßnahmen zu umgehen oder eine Denial-of-Service-Situation zu schaffen.

Official advisory ↗
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-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-26733 Référence CVE CVE-2024-26735 https://www.cve.org/CVERecord?id=CVE-2024-26735 Référence CVE CVE-2024-26740 https://www.cve.org/CVERecord?id=CVE-2024-26740 Référence CVE CVE-2024-26759 https://www.cve.org/CVERecord?id=CVE-2024-26759 Référence CVE CVE-2024-26769 https://www.cve.org/CVERecord?id=CVE-2024-26769 Référence CVE CVE-2024-26772 https://www.cve.org/CVERecord?id=CVE-2024-26772 Référence CVE CVE-2024-26773 https://www.cve.org/CVERecord?id=CVE-2024-26773 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-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26810 https://www.cve.org/CVERecord?id=CVE-2024-26810 Référence CVE CVE-2024-26826 https://www.cve.org/CVERecord?id=CVE-2024-26826 Référence CVE CVE-2024-26837 https://www.cve.org/CVERecord?id=CVE-2024-26837 Référence CVE CVE-2024-26840 https://www.cve.org/CVERecord?id=CVE-2024-26840 Référence CVE CVE-2024-26843 https://www.cve.org/CVERecord?id=CVE-2024-26843 Référence CVE CVE-2024-26846 https://www.cve.org/CVERecord?id=CVE-2024-26846 Référence CVE CVE-2024-26851 https://www.cve.org/CVERecord?id=CVE-2024-26851 Référence CVE CVE-2024-26852 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53725 Référence CVE CVE-2023-53726 https://www.cve.org/CVERecord?id=CVE-2023-53726 Référence CVE CVE-2023-53727 https://www.cve.org/CVERecord?id=CVE-2023-53727 Référence CVE CVE-2023-53728 https://www.cve.org/CVERecord?id=CVE-2023-53728 Référence CVE CVE-2023-53729 https://www.cve.org/CVERecord?id=CVE-2023-53729 Référence CVE CVE-2023-53730 https://www.cve.org/CVERecord?id=CVE-2023-53730 Référence CVE CVE-2023-53731 https://www.cve.org/CVERecord?id=CVE-2023-53731 Référence CVE CVE-2023-53733 https://www.cve.org/CVERecord?id=CVE-2023-53733 Référence CVE CVE-2024-26584 https://www.cve.org/CVERecord?id=CVE-2024-26584 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26808 https://www.cve.org/CVERecord?id=CVE-2024-26808 Référence CVE CVE-2024-26924 https://www.cve.org/CVERecord?id=CVE-2024-26924 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-28956 https://www.cve.org/CVERecord?id=CVE-2024-28956 Référence CVE CVE-2024-35840 https://www.cve.org/CVERecord?id=CVE-2024-35840 Référence CVE CVE-2024-36978 https://www.cve.org/CVERecord?id=CVE-2024-36978 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26773 Référence CVE CVE-2024-26777 https://www.cve.org/CVERecord?id=CVE-2024-26777 Référence CVE CVE-2024-26778 https://www.cve.org/CVERecord?id=CVE-2024-26778 Référence CVE CVE-2024-26779 https://www.cve.org/CVERecord?id=CVE-2024-26779 Référence CVE CVE-2024-26788 https://www.cve.org/CVERecord?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-26793 https://www.cve.org/CVERecord?id=CVE-2024-26793 Référence CVE CVE-2024-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 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-26825 https://www.cve.org/CVERecord?id=CVE-2024-26825 Référence CVE CVE-2024-26835 https://www.cve.org/CVERecord?id=CVE-2024-26835 Référence CVE CVE-2024-26839 https://www.cve.org/CVERecord?id=CVE-2024-26839 Référence CVE CVE-2024-26840 https://www.cve.org/CVERecord?id=CVE-2024-26840 Référence CVE CVE-2024-26845 https://www.cve.org/CVERecord?id=CVE-2024-26845 Référence CVE CVE-2024-26910 https://www.cve.org/CVERecord?id=CVE-2024-26910 Référence CVE CVE-2024-27405 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53128 Référence CVE CVE-2023-53131 https://www.cve.org/CVERecord?id=CVE-2023-53131 Référence CVE CVE-2023-53134 https://www.cve.org/CVERecord?id=CVE-2023-53134 Référence CVE CVE-2023-53137 https://www.cve.org/CVERecord?id=CVE-2023-53137 Référence CVE CVE-2023-53139 https://www.cve.org/CVERecord?id=CVE-2023-53139 Référence CVE CVE-2023-53140 https://www.cve.org/CVERecord?id=CVE-2023-53140 Référence CVE CVE-2023-53142 https://www.cve.org/CVERecord?id=CVE-2023-53142 Référence CVE CVE-2023-53143 https://www.cve.org/CVERecord?id=CVE-2023-53143 Référence CVE CVE-2023-53145 https://www.cve.org/CVERecord?id=CVE-2023-53145 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-28956 https://www.cve.org/CVERecord?id=CVE-2024-28956 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-50124 https://www.cve.org/CVERecord?id=CVE-2024-50124 Référence CVE CVE-2024-50125 https://www.cve.org/CVERecord?id=CVE-2024-50125 Référence CVE CVE-2024-50127 https://www.cve.org/CVERecord?id=CVE-2024-50127 Référence CVE CVE-2024-50257 https://www.cve.org/CVERecord?id=CVE-2024-50257 Référence CVE CVE-2024-50279 https://www.cve.org/CVERecord?id=CVE-2024-50279 Référence CVE CVE-2024-50301 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2023-53139 Référence CVE CVE-2023-53140 https://www.cve.org/CVERecord?id=CVE-2023-53140 Référence CVE CVE-2023-53141 https://www.cve.org/CVERecord?id=CVE-2023-53141 Référence CVE CVE-2023-53142 https://www.cve.org/CVERecord?id=CVE-2023-53142 Référence CVE CVE-2023-53143 https://www.cve.org/CVERecord?id=CVE-2023-53143 Référence CVE CVE-2023-53145 https://www.cve.org/CVERecord?id=CVE-2023-53145 Référence CVE CVE-2023-53146 https://www.cve.org/CVERecord?id=CVE-2023-53146 Référence CVE CVE-2023-6531 https://www.cve.org/CVERecord?id=CVE-2023-6531 Référence CVE CVE-2024-26740 https://www.cve.org/CVERecord?id=CVE-2024-26740 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-27010 https://www.cve.org/CVERecord?id=CVE-2024-27010 Référence CVE CVE-2024-27018 https://www.cve.org/CVERecord?id=CVE-2024-27018 Référence CVE CVE-2024-27415 https://www.cve.org/CVERecord?id=CVE-2024-27415 Référence CVE CVE-2024-28956 https://www.cve.org/CVERecord?id=CVE-2024-28956 Référence CVE CVE-2024-35811 https://www.cve.org/CVERecord?id=CVE-2024-35811 Référence CVE CVE-2024-35840 https://www.cve.org/CVERecord?id=CVE-2024-35840 Référence CVE CVE-2024-35895 https://www.cve.org/CVERecord?id=CVE-2024-35895 Référence CVE CVE-2024-35910 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2022-49028 Référence CVE CVE-2022-49029 https://www.cve.org/CVERecord?id=CVE-2022-49029 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=CVE-2023-46343 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2023-52898 https://www.cve.org/CVERecord?id=CVE-2023-52898 Référence CVE CVE-2023-52918 https://www.cve.org/CVERecord?id=CVE-2023-52918 Référence CVE CVE-2023-52919 https://www.cve.org/CVERecord?id=CVE-2023-52919 Référence CVE CVE-2023-6270 https://www.cve.org/CVERecord?id=CVE-2023-6270 Référence CVE CVE-2024-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26852 https://www.cve.org/CVERecord?id=CVE-2024-26852 Référence CVE CVE-2024-26886 https://www.cve.org/CVERecord?id=CVE-2024-26886 Référence CVE CVE-2024-27043 https://www.cve.org/CVERecord?id=CVE-2024-27043 Référence CVE CVE-2024-27051 https://www.cve.org/CVERecord?id=CVE-2024-27051 Référence CVE CVE-2024-35937 https://www.cve.org/CVERecord?id=CVE-2024-35937 Référence CVE CVE-2024-36886 https://www.cve.org/CVERecord?id=CVE-2024-36886 Référence CVE CVE-2024-36905 https://www.cve.org/CVERecord?id=CVE-2024-36905 Référence CVE CVE-2024-36954 https://www.cve.org/CVERecord?id=

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

ecord?id=CVE-2023-52918 Référence CVE CVE-2023-52919 https://www.cve.org/CVERecord?id=CVE-2023-52919 Référence CVE CVE-2023-6270 https://www.cve.org/CVERecord?id=CVE-2023-6270 Référence CVE CVE-2023-6546 https://www.cve.org/CVERecord?id=CVE-2023-6546 Référence CVE CVE-2024-23307 https://www.cve.org/CVERecord?id=CVE-2024-23307 Référence CVE CVE-2024-26585 https://www.cve.org/CVERecord?id=CVE-2024-26585 Référence CVE CVE-2024-26610 https://www.cve.org/CVERecord?id=CVE-2024-26610 Référence CVE CVE-2024-26622 https://www.cve.org/CVERecord?id=CVE-2024-26622 Référence CVE CVE-2024-26766 https://www.cve.org/CVERecord?id=CVE-2024-26766 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26828 https://www.cve.org/CVERecord?id=CVE-2024-26828 Référence CVE CVE-2024-26852 https://www.cve.org/CVERecord?id=CVE-2024-26852 Référence CVE CVE-2024-26923 https://www.cve.org/CVERecord?id=CVE-2024-26923 Référence CVE CVE-2024-26930 https://www.cve.org/CVERecord?id=CVE-2024-26930 Référence CVE CVE-2024-27043 https://www.cve.org/CVERecord?id=CVE-2024-27043 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-35817 https://www.cve.org/CVERecord?id=CVE-2024-35817 Référence CVE CVE-2024-35861 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26308 Référence CVE CVE-2024-26583 https://www.cve.org/CVERecord?id=CVE-2024-26583 Référence CVE CVE-2024-26584 https://www.cve.org/CVERecord?id=CVE-2024-26584 Référence CVE CVE-2024-26585 https://www.cve.org/CVERecord?id=CVE-2024-26585 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26735 https://www.cve.org/CVERecord?id=CVE-2024-26735 Référence CVE CVE-2024-26759 https://www.cve.org/CVERecord?id=CVE-2024-26759 Référence CVE CVE-2024-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26826 https://www.cve.org/CVERecord?id=CVE-2024-26826 Référence CVE CVE-2024-26859 https://www.cve.org/CVERecord?id=CVE-2024-26859 Référence CVE CVE-2024-26906 https://www.cve.org/CVERecord?id=CVE-2024-26906 Référence CVE CVE-2024-26907 https://www.cve.org/CVERecord?id=CVE-2024-26907 Référence CVE CVE-2024-26974 https://www.cve.org/CVERecord?id=CVE-2024-26974 Référence CVE CVE-2024-26982 https://www.cve.org/CVERecord?id=CVE-2024-26982 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-27410 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-48945 Référence CVE CVE-2023-52610 https://www.cve.org/CVERecord?id=CVE-2023-52610 Référence CVE CVE-2023-52752 https://www.cve.org/CVERecord?id=CVE-2023-52752 Référence CVE CVE-2023-52766 https://www.cve.org/CVERecord?id=CVE-2023-52766 Référence CVE CVE-2023-52915 https://www.cve.org/CVERecord?id=CVE-2023-52915 Référence CVE CVE-2023-52916 https://www.cve.org/CVERecord?id=CVE-2023-52916 Référence CVE CVE-2024-26640 https://www.cve.org/CVERecord?id=CVE-2024-26640 Référence CVE CVE-2024-26759 https://www.cve.org/CVERecord?id=CVE-2024-26759 Référence CVE CVE-2024-26767 https://www.cve.org/CVERecord?id=CVE-2024-26767 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26837 https://www.cve.org/CVERecord?id=CVE-2024-26837 Référence CVE CVE-2024-27024 https://www.cve.org/CVERecord?id=CVE-2024-27024 Référence CVE CVE-2024-36953 https://www.cve.org/CVERecord?id=CVE-2024-36953 Référence CVE CVE-2024-36971 https://www.cve.org/CVERecord?id=CVE-2024-36971 Référence CVE CVE-2024-37353 https://www.cve.org/CVERecord?id=CVE-2024-37353 Référence CVE CVE-2024-38381 https://www.cve.org/CVERecord?id=CVE-2024-38381 Référence CVE CVE-2024-38538 https://www.cve.org/CVERecord?id=CVE-2024-38538 Référence CVE CVE-2024-38596 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0741Multiples vulnérabilités dans Juniper Secure Analytics

d?id=CVE-2024-26675 Référence CVE CVE-2024-26693 https://www.cve.org/CVERecord?id=CVE-2024-26693 Référence CVE CVE-2024-26694 https://www.cve.org/CVERecord?id=CVE-2024-26694 Référence CVE CVE-2024-26735 https://www.cve.org/CVERecord?id=CVE-2024-26735 Référence CVE CVE-2024-26743 https://www.cve.org/CVERecord?id=CVE-2024-26743 Référence CVE CVE-2024-26744 https://www.cve.org/CVERecord?id=CVE-2024-26744 Référence CVE CVE-2024-26759 https://www.cve.org/CVERecord?id=CVE-2024-26759 Référence CVE CVE-2024-26779 https://www.cve.org/CVERecord?id=CVE-2024-26779 Référence CVE CVE-2024-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26826 https://www.cve.org/CVERecord?id=CVE-2024-26826 Référence CVE CVE-2024-26859 https://www.cve.org/CVERecord?id=CVE-2024-26859 Référence CVE CVE-2024-26872 https://www.cve.org/CVERecord?id=CVE-2024-26872 Référence CVE CVE-2024-26892 https://www.cve.org/CVERecord?id=CVE-2024-26892 Référence CVE CVE-2024-26897 https://www.cve.org/CVERecord?id=CVE-2024-26897 Référence CVE CVE-2024-26901 https://www.cve.org/CVERecord?id=CVE-2024-26901 Référence CVE CVE-2024-26906 https://www.cve.org/CVERecord?id=CVE-2024-26906 Référence CVE CVE-2024-26907 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0720Multiples vulnérabilités dans IBM QRadar SIEM

d?id=CVE-2024-22365 Référence CVE CVE-2024-26583 https://www.cve.org/CVERecord?id=CVE-2024-26583 Référence CVE CVE-2024-26584 https://www.cve.org/CVERecord?id=CVE-2024-26584 Référence CVE CVE-2024-26585 https://www.cve.org/CVERecord?id=CVE-2024-26585 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26735 https://www.cve.org/CVERecord?id=CVE-2024-26735 Référence CVE CVE-2024-26759 https://www.cve.org/CVERecord?id=CVE-2024-26759 Référence CVE CVE-2024-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26826 https://www.cve.org/CVERecord?id=CVE-2024-26826 Référence CVE CVE-2024-26859 https://www.cve.org/CVERecord?id=CVE-2024-26859 Référence CVE CVE-2024-26906 https://www.cve.org/CVERecord?id=CVE-2024-26906 Référence CVE CVE-2024-26907 https://www.cve.org/CVERecord?id=CVE-2024-26907 Référence CVE CVE-2024-26974 https://www.cve.org/CVERecord?id=CVE-2024-26974 Référence CVE CVE-2024-26982 https://www.cve.org/CVERecord?id=CVE-2024-26982 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-27410 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-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=CVE-2024-26814 Référence CVE CVE-2024-26816 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-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=CVE-2024-26838 Référence CVE CVE-2024-26839 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26584 Référence CVE CVE-2024-26585 https://www.cve.org/CVERecord?id=CVE-2024-26585 Référence CVE CVE-2024-26598 https://www.cve.org/CVERecord?id=CVE-2024-26598 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26735 https://www.cve.org/CVERecord?id=CVE-2024-26735 Référence CVE CVE-2024-26759 https://www.cve.org/CVERecord?id=CVE-2024-26759 Référence CVE CVE-2024-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26826 https://www.cve.org/CVERecord?id=CVE-2024-26826 Référence CVE CVE-2024-26859 https://www.cve.org/CVERecord?id=CVE-2024-26859 Référence CVE CVE-2024-26906 https://www.cve.org/CVERecord?id=CVE-2024-26906 Référence CVE CVE-2024-26907 https://www.cve.org/CVERecord?id=CVE-2024-26907 Référence CVE CVE-2024-26974 https://www.cve.org/CVERecord?id=CVE-2024-26974 Référence CVE CVE-2024-26982 https://www.cve.org/CVERecord?id=CVE-2024-26982 Référence CVE CVE-2024-27393 https://www.cve.org/CVERecord?id=CVE-2024-27393 Référence CVE CVE-2024-27397 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-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=CVE-2024-26815 Référence CVE CVE-2024-26816 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26781 Référence CVE CVE-2024-26782 https://www.cve.org/CVERecord?id=CVE-2024-26782 Référence CVE CVE-2024-26787 https://www.cve.org/CVERecord?id=CVE-2024-26787 Référence CVE CVE-2024-26788 https://www.cve.org/CVERecord?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-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-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 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-26808 https://www.cve.org/CVERecord?id=CVE-2024-26808 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-26816 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données, un déni de service.

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

rd?id=CVE-2024-1086 Référence CVE CVE-2024-25742 https://www.cve.org/CVERecord?id=CVE-2024-25742 Référence CVE CVE-2024-25743 https://www.cve.org/CVERecord?id=CVE-2024-25743 Référence CVE CVE-2024-26602 https://www.cve.org/CVERecord?id=CVE-2024-26602 Référence CVE CVE-2024-26609 https://www.cve.org/CVERecord?id=CVE-2024-26609 Référence CVE CVE-2024-26642 https://www.cve.org/CVERecord?id=CVE-2024-26642 Référence CVE CVE-2024-26643 https://www.cve.org/CVERecord?id=CVE-2024-26643 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Gestion détaillée du document le 24 mai 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-0381Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2024-26781 Référence CVE CVE-2024-26782 https://www.cve.org/CVERecord?id=CVE-2024-26782 Référence CVE CVE-2024-26787 https://www.cve.org/CVERecord?id=CVE-2024-26787 Référence CVE CVE-2024-26788 https://www.cve.org/CVERecord?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-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-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 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-26808 https://www.cve.org/CVERecord?id=CVE-2024-26808 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-26816 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-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=CVE-2024-26814 Référence CVE CVE-2024-26815 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-020741Linux の 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
Linux: < 2.6.34, 5.4.271 ≤ 5.4.*, 5.10.212 ≤ 5.10.*, 5.15.151 ≤ 5.15.*, 6.1.81 ≤ 6.1.*, 6.6.21 ≤ 6.6.*, 6.7.9 ≤ 6.7.*, 6.8 ≤ *
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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 12 Aug 2026, 17:39 UTC · CWE-416 · Use After Free

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-24066
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
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-24066↗Vendor CSAF · SUSE Product Security Team↗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-26804 · cve.blacktree.nl