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

wifi: wfx: fix memory leak when starting AP

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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 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.

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 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.85-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-24158

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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: wifi: wfx: fix memory leak when starting AP Kmemleak reported this error: unreferenced object 0xd73d1180 (size 184): comm "wpa_supplicant", pid 1559, jiffies 13006305 (age 964.245s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 1e 00 01 00 00 00 00 00 ................ backtrace: [<5ca11420>] kmem_cache_alloc+0x20c/0x5ac [<127bdd74>] __alloc_skb+0x144/0x170 [<fb8a5e38>] __netdev_alloc_skb+0x50/0x180 [<0f9fa1d5>] __ieee80211_beacon_get+0x290/0x4d4 [mac80211] [<7accd02d>] ieee80211_beacon_get_tim+0x54/0x18c [mac80211] [<41e25cc3>] wfx_start_ap+0xc8/0x234 [wfx] [<93a70356>] ieee80211_start_ap+0x404/0x6b4 [mac80211] [<a4a661cd>] nl80211_start_ap+0x76c/0x9e0 [cfg80211] [<47bd8b68>] genl_rcv_msg+0x198/0x378 [<453ef796>] netlink_rcv_skb+0xd0/0x130 [<6b7c977a>] genl_rcv+0x34/0x44 [<66b2d04d>] netlink_unicast+0x1b4/0x258 [<f965b9b6>] netlink_sendmsg+0x1e8/0x428 [<aadb8231>] ____sys_sendmsg+0x1e0/0x274 [<d2b5212d>] ___sys_sendmsg+0x80/0xb4 [<69954f45>] __sys_sendmsg+0x64/0xa8 unreferenced object 0xce087000 (size 1024): comm "wpa_supplicant", pid 1559, jiffies 13006305 (age 964.246s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 10 00 07 40 00 00 00 00 00 00 00 00 00 00 00 00 ...@............ backtrace: [<9a993714>] __kmalloc_track_caller+0x230/0x600 [<f83ea192>] kmalloc_reserve.constprop.0+0x30/0x74 [<a2c61343>] __alloc_skb+0xa0/0x170 [<fb8a5e38>] __netdev_alloc_skb+0x50/0x180 [<0f9fa1d5>] __ieee80211_beacon_get+0x290/0x4d4 [mac80211] [<7accd02d>] ieee80211_beacon_get_tim+0x54/0x18c [mac80211] [<41e25cc3>] wfx_start_ap+0xc8/0x234 [wfx] [<93a70356>] ieee80211_start_ap+0x404/0x6b4 [mac80211] [<a4a661cd>] nl80211_start_ap+0x76c/0x9e0 [cfg80211] [<47bd8b68>] genl_rcv_msg+0x198/0x378 [<453ef796>] netlink_rcv_skb+0xd0/0x130 [<6b7c977a>] genl_rcv+0x34/0x44 [<66b2d04d>] netlink_unicast+0x1b4/0x258 [<f965b9b6>] netlink_sendmsg+0x1e8/0x428 [<aadb8231>] ____sys_sendmsg+0x1e0/0x274 [<d2b5212d>] ___sys_sendmsg+0x80/0xb4 However, since the kernel is build optimized, it seems the stack is not accurate. It appears the issue is related to wfx_set_mfp_ap(). The issue is obvious in this function: memory allocated by ieee80211_beacon_get() is never released. Fixing this leak makes kmemleak happy.

What

In the Linux kernel, the following vulnerability has been resolved: wifi: wfx: fix memory leak when starting AP Kmemleak reported this error: unreferenced object 0xd73d1180 (size 184): comm "wpa_supplicant", pid 1559, jiffies 13006305 (age 964.245s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 1e 00 01 00 00 00 00 00 ................ backtrace: [<5ca11420>] kmem_cache_alloc+0x20c/0x5ac [<127bdd74>] __alloc_skb+0x144/0x170 [<fb8a5e38>] __netdev_alloc_skb+0x50/0x180 [<0f9fa1d5>] __ieee80211_beacon_get+0x290/0x4d4 [mac80211] [<7accd02d>] ieee80211_beacon_get_tim+0x54/0x18c [mac80211] [<41e25cc3>] wfx_start_ap+0xc8/0x234 [wfx] [<93a70356>] ieee80211_start_ap+0x404/0x6b4 [mac80211] [<a4a661cd>] nl80211_start_ap+0x76c/0x9e0 [cfg80211] [<47bd8b68>] genl_rcv_msg+0x198/0x378 [<453ef796>] netlink_rcv_skb+0xd0/0x130 [<6b7c977a>] genl_rcv+0x34/0x44 [<66b2d04d>] netlink_unicast+0x1b4/0x258 [<f965b9b6>] netlink_sendmsg+0x1e8/0x428 [<aadb8231>] ____sys_sendmsg+0x1e0/0x274 [<d2b5212d>] ___sys_sendmsg+0x80/0xb4 [<69954f45>] __sys_sendmsg+0x64/0xa8 unreferenced object 0xce087000 (size 1024): comm "wpa_supplicant", pid 1559, jiffies 13006305 (age 964.246s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 10 00 07 40 00 00 00 00 00 00 00 00 00 00 00 00 ...@............ backtrace: [<9a993714>] __kmalloc_track_caller+0x230/0x600 [<f83ea192>] kmalloc_reserve.constprop.0+0x30/0x74 [<a2c61343>] __alloc_skb+0xa0/0x170 [<fb8a5e38>] __netdev_alloc_skb+0x50/0x180 [<0f9fa1d5>] __ieee80211_beacon_get+0x290/0x4d4 [mac80211] [<7accd02d>] ieee80211_beacon_get_tim+0x54/0x18c [mac80211] [<41e25cc3>] wfx_start_ap+0xc8/0x234 [wfx] [<93a70356>] ieee80211_start_ap+0x404/0x6b4 [mac80211] [<a4a661cd>] nl80211_start_ap+0x76c/0x9e0 [cfg80211] [<47bd8b68>] genl_rcv_msg+0x198/0x378 [<453ef796>] netlink_rcv_skb+0xd0/0x130 [<6b7c977a>] genl_rcv+0x34/0x44 [<66b2d04d>] netlink_unicast+0x1b4/0x258 [<f965b9b6>] netlink_sendmsg+0x1e8/0x428 [<aadb8231>] ____sys_sendmsg+0x1e0/0x274 [<d2b5212d>] ___sys_sendmsg+0x80/0xb4 However, since the kernel is build optimized, it seems the stack is not accurate. It appears the issue is related to wfx_set_mfp_ap(). The issue is obvious in this function: memory allocated by ieee80211_beacon_get() is never released. Fixing this leak makes kmemleak happy.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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: wifi: wfx: fix memory leak when starting AP Kmemleak reported this error: unreferenced object 0xd73d1180 (size 184): comm "wpa_supplicant", pid 1559, jiffies 13006305 (age 964.245s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 1e 00 01 00 00 00 00 00 ................ backtrace: [<5ca11420>] kmem_cache_alloc+0x20c/0x5ac [<127bdd74>] __alloc_skb+0x144/0x170 [<fb8a5e38>] __netdev_alloc_skb+0x50/0x180 [<0f9fa1d5>] __ieee80211_beacon_get+0x290/0x4d4 [mac80211] [<7accd02d>] ieee80211_beacon_get_tim+0x54/0x18c [mac80211] [<41e25cc3>] wfx_start_ap+0xc8/0x234 [wfx] [<93a70356>] ieee80211_start_ap+0x404/0x6b4 [mac80211] [<a4a661cd>] nl80211_start_ap+0x76c/0x9e0 [cfg80211] [<47bd8b68>] genl_rcv_msg+0x198/0x378 [<453ef796>] netlink_rcv_skb+0xd0/0x130 [<6b7c977a>] genl_rcv+0x34/0x44 [<66b2d04d>] netlink_unicast+0x1b4/0x258 [<f965b9b6>] netlink_sendmsg+0x1e8/0x428 [<aadb8231>] ____sys_sendmsg+0x1e0/0x274 [<d2b5212d>] ___sys_sendmsg+0x80/0xb4 [<69954f45>] __sys_sendmsg+0x64/0xa8 unreferenced object 0xce087000 (size 1024): comm "wpa_supplicant", pid 1559, jiffies 13006305 (age 964.246s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 10 00 07 40 00 00 00 00 00 00 00 00 00 00 00 00 ...@............ backtrace: [<9a993714>] __kmalloc_track_caller+0x230/0x600 [<f83ea192>] kmalloc_reserve.constprop.0+0x30/0x74 [<a2c61343>] __alloc_skb+0xa0/0x170 [<fb8a5e38>] __netdev_alloc_skb+0x50/0x180 [<0f9fa1d5>] __ieee80211_beacon_get+0x290/0x4d4 [mac80211] [<7accd02d>] ieee80211_beacon_get_tim+0x54/0x18c [mac80211] [<41e25cc3>] wfx_start_ap+0xc8/0x234 [wfx] [<93a70356>] ieee80211_start_ap+0x404/0x6b4 [mac80211] [<a4a661cd>] nl80211_start_ap+0x76c/0x9e0 [cfg80211] [<47bd8b68>] genl_rcv_msg+0x198/0x378 [<453ef796>] netlink_rcv_skb+0xd0/0x130 [<6b7c977a>] genl_rcv+0x34/0x44 [<66b2d04d>] netlink_unicast+0x1b4/0x258 [<f965b9b6>] netlink_sendmsg+0x1e8/0x428 [<aadb8231>] ____sys_sendmsg+0x1e0/0x274 [<d2b5212d>] ___sys_sendmsg+0x80/0xb4 However, since the kernel is build optimized, it seems the stack is not accurate. It appears the issue is related to wfx_set_mfp_ap(). The issue is obvious in this function: memory allocated by ieee80211_beacon_get() is never released. Fixing this leak makes kmemleak happy.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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 → Out-of-bounds Read → 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-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

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.
CWE-125
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-2025-AVI-1135Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2022-50327 Référence CVE CVE-2023-52574 https://www.cve.org/CVERecord?id=CVE-2023-52574 Référence CVE CVE-2023-52593 https://www.cve.org/CVERecord?id=CVE-2023-52593 Référence CVE CVE-2023-52650 https://www.cve.org/CVERecord?id=CVE-2023-52650 Référence CVE CVE-2023-52854 https://www.cve.org/CVERecord?id=CVE-2023-52854 Référence CVE CVE-2023-52935 https://www.cve.org/CVERecord?id=CVE-2023-52935 Référence CVE CVE-2023-53034 https://www.cve.org/CVERecord?id=CVE-2023-53034 Référence CVE CVE-2023-53074 https://www.cve.org/CVERecord?id=CVE-2023-53074 Référence CVE CVE-2024-26700 https://www.cve.org/CVERecord?id=CVE-2024-26700 Référence CVE CVE-2024-26896 https://www.cve.org/CVERecord?id=CVE-2024-26896 Référence CVE CVE-2024-35867 https://www.cve.org/CVERecord?id=CVE-2024-35867 Référence CVE CVE-2024-36331 https://www.cve.org/CVERecord?id=CVE-2024-36331 Référence CVE CVE-2024-41006 https://www.cve.org/CVERecord?id=CVE-2024-41006 Référence CVE CVE-2024-47691 https://www.cve.org/CVERecord?id=CVE-2024-47691 Référence CVE CVE-2024-49935 https://www.cve.org/CVERecord?id=CVE-2024-49935 Référence CVE CVE-2024-49963 https://www.cve.org/CVERecord?id=CVE-2024-49963 Référence CVE CVE-2024-50006 https://www.cve.org/CVERecord?id=CVE-2024-50006 Référence CVE CVE-2024-50061 https://www.cve.org/CVERecord?id=

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

cord?id=CVE-2024-0727 Référence CVE CVE-2024-11168 https://www.cve.org/CVERecord?id=CVE-2024-11168 Référence CVE CVE-2024-12254 https://www.cve.org/CVERecord?id=CVE-2024-12254 Référence CVE CVE-2024-12718 https://www.cve.org/CVERecord?id=CVE-2024-12718 Référence CVE CVE-2024-13176 https://www.cve.org/CVERecord?id=CVE-2024-13176 Référence CVE CVE-2024-2511 https://www.cve.org/CVERecord?id=CVE-2024-2511 Référence CVE CVE-2024-26700 https://www.cve.org/CVERecord?id=CVE-2024-26700 Référence CVE CVE-2024-26726 https://www.cve.org/CVERecord?id=CVE-2024-26726 Référence CVE CVE-2024-26775 https://www.cve.org/CVERecord?id=CVE-2024-26775 Référence CVE CVE-2024-26896 https://www.cve.org/CVERecord?id=CVE-2024-26896 Référence CVE CVE-2024-4032 https://www.cve.org/CVERecord?id=CVE-2024-4032 Référence CVE CVE-2024-44939 https://www.cve.org/CVERecord?id=CVE-2024-44939 Référence CVE CVE-2024-4603 https://www.cve.org/CVERecord?id=CVE-2024-4603 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2024-50602 https://www.cve.org/CVERecord?id=CVE-2024-50602 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-57883 https://www.cve.org/CVERecord?id=CVE-2024-57883 Référence CVE CVE-2024-6119 https://www.cve.org/CVERecord?id=CVE-2024-

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

de sécurité Ubuntu USN-7864-1 du 07 novembre 2025 https://ubuntu.com/security/notices/USN-7864-1 Référence CVE CVE-2021-47294 https://www.cve.org/CVERecord?id=CVE-2021-47294 Référence CVE CVE-2021-47330 https://www.cve.org/CVERecord?id=CVE-2021-47330 Référence CVE CVE-2023-52574 https://www.cve.org/CVERecord?id=CVE-2023-52574 Référence CVE CVE-2023-52593 https://www.cve.org/CVERecord?id=CVE-2023-52593 Référence CVE CVE-2023-52650 https://www.cve.org/CVERecord?id=CVE-2023-52650 Référence CVE CVE-2023-53034 https://www.cve.org/CVERecord?id=CVE-2023-53034 Référence CVE CVE-2024-26700 https://www.cve.org/CVERecord?id=CVE-2024-26700 Référence CVE CVE-2024-26896 https://www.cve.org/CVERecord?id=CVE-2024-26896 Référence CVE CVE-2024-36350 https://www.cve.org/CVERecord?id=CVE-2024-36350 Référence CVE CVE-2024-36357 https://www.cve.org/CVERecord?id=CVE-2024-36357 Référence CVE CVE-2024-50006 https://www.cve.org/CVERecord?id=CVE-2024-50006 Référence CVE CVE-2024-50299 https://www.cve.org/CVERecord?id=CVE-2024-50299 Référence CVE CVE-2024-53124 https://www.cve.org/CVERecord?id=CVE-2024-53124 Référence CVE CVE-2024-53150 https://www.cve.org/CVERecord?id=CVE-2024-53150 Référence CVE CVE-2024-56767 https://www.cve.org/CVERecord?id=CVE-2024-56767 Référence CVE CVE-2024-58092 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26141 Référence CVE CVE-2024-26146 https://www.cve.org/CVERecord?id=CVE-2024-26146 Référence CVE CVE-2024-26256 https://www.cve.org/CVERecord?id=CVE-2024-26256 Référence CVE CVE-2024-26458 https://www.cve.org/CVERecord?id=CVE-2024-26458 Référence CVE CVE-2024-26461 https://www.cve.org/CVERecord?id=CVE-2024-26461 Référence CVE CVE-2024-26462 https://www.cve.org/CVERecord?id=CVE-2024-26462 Référence CVE CVE-2024-26700 https://www.cve.org/CVERecord?id=CVE-2024-26700 Référence CVE CVE-2024-26726 https://www.cve.org/CVERecord?id=CVE-2024-26726 Référence CVE CVE-2024-26775 https://www.cve.org/CVERecord?id=CVE-2024-26775 Référence CVE CVE-2024-26896 https://www.cve.org/CVERecord?id=CVE-2024-26896 Référence CVE CVE-2024-27280 https://www.cve.org/CVERecord?id=CVE-2024-27280 Référence CVE CVE-2024-27281 https://www.cve.org/CVERecord?id=CVE-2024-27281 Référence CVE CVE-2024-27407 https://www.cve.org/CVERecord?id=CVE-2024-27407 Référence CVE CVE-2024-27766 https://www.cve.org/CVERecord?id=CVE-2024-27766 Référence CVE CVE-2024-28085 https://www.cve.org/CVERecord?id=CVE-2024-28085 Référence CVE CVE-2024-28182 https://www.cve.org/CVERecord?id=CVE-2024-28182 Référence CVE CVE-2024-28757 https://www.cve.org/CVERecord?id=CVE-2024-28757 Référence CVE CVE-2024-28834 https://www.cve.org/CVERecord?id=

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

s/USN-7850-1 Bulletin de sécurité Ubuntu USN-7853-1 du 30 octobre 2025 https://ubuntu.com/security/notices/USN-7853-1 Bulletin de sécurité Ubuntu USN-7853-2 du 30 octobre 2025 https://ubuntu.com/security/notices/USN-7853-2 Bulletin de sécurité Ubuntu USN-7854-1 du 30 octobre 2025 https://ubuntu.com/security/notices/USN-7854-1 Référence CVE CVE-2023-52574 https://www.cve.org/CVERecord?id=CVE-2023-52574 Référence CVE CVE-2023-52593 https://www.cve.org/CVERecord?id=CVE-2023-52593 Référence CVE CVE-2023-52650 https://www.cve.org/CVERecord?id=CVE-2023-52650 Référence CVE CVE-2024-26700 https://www.cve.org/CVERecord?id=CVE-2024-26700 Référence CVE CVE-2024-26896 https://www.cve.org/CVERecord?id=CVE-2024-26896 Référence CVE CVE-2024-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 Référence CVE CVE-2024-36350 https://www.cve.org/CVERecord?id=CVE-2024-36350 Référence CVE CVE-2024-36357 https://www.cve.org/CVERecord?id=CVE-2024-36357 Référence CVE CVE-2024-41006 https://www.cve.org/CVERecord?id=CVE-2024-41006 Référence CVE CVE-2024-49924 https://www.cve.org/CVERecord?id=CVE-2024-49924 Référence CVE CVE-2024-50006 https://www.cve.org/CVERecord?id=CVE-2024-50006 Référence CVE CVE-2024-50299 https://www.cve.org/CVERecord?id=CVE-2024-50299 Référence CVE CVE-2024-53124 https://www.cve.org/CVERecord?id=

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

/notices/USN-7795-4 Référence CVE CVE-2021-47149 https://www.cve.org/CVERecord?id=CVE-2021-47149 Référence CVE CVE-2021-47319 https://www.cve.org/CVERecord?id=CVE-2021-47319 Référence CVE CVE-2021-47589 https://www.cve.org/CVERecord?id=CVE-2021-47589 Référence CVE CVE-2023-52593 https://www.cve.org/CVERecord?id=CVE-2023-52593 Référence CVE CVE-2023-52757 https://www.cve.org/CVERecord?id=CVE-2023-52757 Référence CVE CVE-2023-52975 https://www.cve.org/CVERecord?id=CVE-2023-52975 Référence CVE CVE-2023-53034 https://www.cve.org/CVERecord?id=CVE-2023-53034 Référence CVE CVE-2024-26700 https://www.cve.org/CVERecord?id=CVE-2024-26700 Référence CVE CVE-2024-26896 https://www.cve.org/CVERecord?id=CVE-2024-26896 Référence CVE CVE-2024-27078 https://www.cve.org/CVERecord?id=CVE-2024-27078 Référence CVE CVE-2024-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 Référence CVE CVE-2024-36350 https://www.cve.org/CVERecord?id=CVE-2024-36350 Référence CVE CVE-2024-36357 https://www.cve.org/CVERecord?id=CVE-2024-36357 Référence CVE CVE-2024-38541 https://www.cve.org/CVERecord?id=CVE-2024-38541 Référence CVE CVE-2024-49924 https://www.cve.org/CVERecord?id=CVE-2024-49924 Référence CVE CVE-2024-49950 https://www.cve.org/CVERecord?id=CVE-2024-49950 Référence CVE CVE-2024-50073 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-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=CVE-2024-26889 Référence CVE CVE-2024-26890 https://www.cve.org/CVERecord?id=CVE-2024-26890 Référence CVE CVE-2024-26891 https://www.cve.org/CVERecord?id=CVE-2024-26891 Référence CVE CVE-2024-26892 https://www.cve.org/CVERecord?id=CVE-2024-26892 Référence CVE CVE-2024-26893 https://www.cve.org/CVERecord?id=CVE-2024-26893 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=CVE-2024-26895 Référence CVE CVE-2024-26896 https://www.cve.org/CVERecord?id=CVE-2024-26896 Référence CVE CVE-2024-26897 https://www.cve.org/CVERecord?id=CVE-2024-26897 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=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=CVE-2024-26901 Référence CVE CVE-2024-26903 https://www.cve.org/CVERecord?id=CVE-2024-26903 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-0420Multiples vulnérabilités dans le noyau Linux de SUSE

d?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=CVE-2024-26896 Référence CVE CVE-2024-26897 https://www.cve.org/CVERecord?id=CVE-2024-26897 Référence CVE CVE-2024-26898 https://www.cve.org/CVERecord?id=CVE-2024-26898 Référence CVE CVE-2024-26901 https://www.cve.org/CVERecord?id=CVE-2024-26901 Référence CVE CVE-2024-26903 https://www.cve.org/CVERecord?id=CVE-2024-26903 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-26915 https://www.cve.org/CVERecord?id=CVE-2024-26915 Référence CVE CVE-2024-26917 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-020782Linux の Linux Kernel における境界外読み取りに関する脆弱性

Linux の Linux Kernel には、境界外読み取りに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Linux: 268bceec1684932e194ae87877dcc73f534d921c < a1f57a0127b89a6b6620514564aa7eaec16d9af3, 268bceec1684932e194ae87877dcc73f534d921c < 3a71ec74e5e3478d202a1874f085ca3ef40be49b, 268bceec1684932e194ae87877dcc73f534d921c < 12f00a367b2b62756e0396f14b54c2c15524e1c3, 268bceec1684932e194ae87877dcc73f534d921c < dadbb5d29d6c5f571a50272fce8c1505a9559487, 268bceec1684932e194ae87877dcc73f534d921c < b8cfb7c819dd39965136a66fe3a7fde688d976fc, 5.10
Fixed
Linux: < 5.10, 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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 17 Apr 2024 · Last source change 11 May 2026, 20:06 UTC · CWE-125 · Out-of-bounds Read

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-24158
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
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-24158↗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-26896 · cve.blacktree.nl