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

bpf: Fix a sdiv overflow issue

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 17 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.24% 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 17 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.

21 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 17 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.11.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-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-azure-nvidiaAffected, 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-gkeopAffected, 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-nvidiaAffected, 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-nvidia-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.11Affected, 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-realtimeAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, 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
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-49888 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: bpf: Fix a sdiv overflow issue
98 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 7
  • kernel as a component of Red Hat Enterprise Linux 7
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 7
  • kernel-debug as a component of Red Hat Enterprise Linux 7
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 7
  • kernel-devel as a component of Red Hat Enterprise Linux 7
  • kernel-doc as a component of Red Hat Enterprise Linux 7
  • kernel-headers as a component of Red Hat Enterprise Linux 7
  • kernel-kdump as a component of Red Hat Enterprise Linux 7
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 7
  • kernel-rt as a component of Red Hat Enterprise Linux 7
Summary
A flaw was found in the kernel's Berkeley Packet Filter (BPF) subsystem. A privileged local user can trigger a signed division or modulo overflow when executing a BPF program on an x86_64 system. This overflow can lead to a kernel exception and subsequently cause a system crash, resulting in a Denial of Service (DoS).
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2024-43588

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 17 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: bpf: Fix a sdiv overflow issue Zac Ecob reported a problem where a bpf program may cause kernel crash due to the following error: Oops: divide error: 0000 [#1] PREEMPT SMP KASAN PTI The failure is due to the below signed divide: LLONG_MIN/-1 where LLONG_MIN equals to -9,223,372,036,854,775,808. LLONG_MIN/-1 is supposed to give a positive number 9,223,372,036,854,775,808, but it is impossible since for 64-bit system, the maximum positive number is 9,223,372,036,854,775,807. On x86_64, LLONG_MIN/-1 will cause a kernel exception. On arm64, the result for LLONG_MIN/-1 is LLONG_MIN. Further investigation found all the following sdiv/smod cases may trigger an exception when bpf program is running on x86_64 platform: - LLONG_MIN/-1 for 64bit operation - INT_MIN/-1 for 32bit operation - LLONG_MIN%-1 for 64bit operation - INT_MIN%-1 for 32bit operation where -1 can be an immediate or in a register. On arm64, there are no exceptions: - LLONG_MIN/-1 = LLONG_MIN - INT_MIN/-1 = INT_MIN - LLONG_MIN%-1 = 0 - INT_MIN%-1 = 0 where -1 can be an immediate or in a register. Insn patching is needed to handle the above cases and the patched codes produced results aligned with above arm64 result. The below are pseudo codes to handle sdiv/smod exceptions including both divisor -1 and divisor 0 and the divisor is stored in a register. sdiv: tmp = rX tmp += 1 /* [-1, 0] -> [0, 1] if tmp >(unsigned) 1 goto L2 if tmp == 0 goto L1 rY = 0 L1: rY = -rY; goto L3 L2: rY /= rX L3: smod: tmp = rX tmp += 1 /* [-1, 0] -> [0, 1] if tmp >(unsigned) 1 goto L1 if tmp == 1 (is64 ? goto L2 : goto L3) rY = 0; goto L2 L1: rY %= rX L2: goto L4 // only when !is64 L3: wY = wY // only when !is64 L4: [1] https://lore.kernel.org/bpf/tPJLTEh7S_DxFEqAI2Ji5MBSoZVg7_G-Py2iaZpAaWtM961fFTWtsnlzwvTbzBzaUzwQAoNATXKUlt0LZOFgnDcIyKCswAnAGdUF3LBrhGQ=@protonmail.com/

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a sdiv overflow issue Zac Ecob reported a problem where a bpf program may cause kernel crash due to the following error: Oops: divide error: 0000 [#1] PREEMPT SMP KASAN PTI The failure is due to the below signed divide: LLONG_MIN/-1 where LLONG_MIN equals to -9,223,372,036,854,775,808. LLONG_MIN/-1 is supposed to give a positive number 9,223,372,036,854,775,808, but it is impossible since for 64-bit system, the maximum positive number is 9,223,372,036,854,775,807. On x86_64, LLONG_MIN/-1 will cause a kernel exception. On arm64, the result for LLONG_MIN/-1 is LLONG_MIN. Further investigation found all the following sdiv/smod cases may trigger an exception when bpf program is running on x86_64 platform: - LLONG_MIN/-1 for 64bit operation - INT_MIN/-1 for 32bit operation - LLONG_MIN%-1 for 64bit operation - INT_MIN%-1 for 32bit operation where -1 can be an immediate or in a register. On arm64, there are no exceptions: - LLONG_MIN/-1 = LLONG_MIN - INT_MIN/-1 = INT_MIN - LLONG_MIN%-1 = 0 - INT_MIN%-1 = 0 where -1 can be an immediate or in a register. Insn patching is needed to handle the above cases and the patched codes produced results aligned with above arm64 result. The below are pseudo codes to handle sdiv/smod exceptions including both divisor -1 and divisor 0 and the divisor is stored in a register. sdiv: tmp = rX tmp += 1 /* [-1, 0] -> [0, 1] if tmp >(unsigned) 1 goto L2 if tmp == 0 goto L1 rY = 0 L1: rY = -rY; goto L3 L2: rY /= rX L3: smod: tmp = rX tmp += 1 /* [-1, 0] -> [0, 1] if tmp >(unsigned) 1 goto L1 if tmp == 1 (is64 ? goto L2 : goto L3) rY = 0; goto L2 L1: rY %= rX L2: goto L4 // only when !is64 L3: wY = wY // only when !is64 L4: [1] https://lore.kernel.org/bpf/tPJLTEh7S_DxFEqAI2Ji5MBSoZVg7_G-Py2iaZpAaWtM961fFTWtsnlzwvTbzBzaUzwQAoNATXKUlt0LZOFgnDcIyKCswAnAGdUF3LBrhGQ=@protonmail.com/

Why

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How

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

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a sdiv overflow issue Zac Ecob reported a problem where a bpf program may cause kernel crash due to the following error: Oops: divide error: 0000 [#1] PREEMPT SMP KASAN PTI The failure is due to the below signed divide: LLONG_MIN/-1 where LLONG_MIN equals to -9,223,372,036,854,775,808. LLONG_MIN/-1 is supposed to give a positive number 9,223,372,036,854,775,808, but it is impossible since for 64-bit system, the maximum positive number is 9,223,372,036,854,775,807. On x86_64, LLONG_MIN/-1 will cause a kernel exception. On arm64, the result for LLONG_MIN/-1 is LLONG_MIN. Further investigation found all the following sdiv/smod cases may trigger an exception when bpf program is running on x86_64 platform: - LLONG_MIN/-1 for 64bit operation - INT_MIN/-1 for 32bit operation - LLONG_MIN%-1 for 64bit operation - INT_MIN%-1 for 32bit operation where -1 can be an immediate or in a register. On arm64, there are no exceptions: - LLONG_MIN/-1 = LLONG_MIN - INT_MIN/-1 = INT_MIN - LLONG_MIN%-1 = 0 - INT_MIN%-1 = 0 where -1 can be an immediate or in a register. Insn patching is needed to handle the above cases and the patched codes produced results aligned with above arm64 result. The below are pseudo codes to handle sdiv/smod exceptions including both divisor -1 and divisor 0 and the divisor is stored in a register. sdiv: tmp = rX tmp += 1 /* [-1, 0] -> [0, 1] if tmp >(unsigned) 1 goto L2 if tmp == 0 goto L1 rY = 0 L1: rY = -rY; goto L3 L2: rY /= rX L3: smod: tmp = rX tmp += 1 /* [-1, 0] -> [0, 1] if tmp >(unsigned) 1 goto L1 if tmp == 1 (is64 ? goto L2 : goto L3) rY = 0; goto L2 L1: rY %= rX L2: goto L4 // only when !is64 L3: wY = wY // only when !is64 L4: [1] https://lore.kernel.org/bpf/tPJLTEh7S_DxFEqAI2Ji5MBSoZVg7_G-Py2iaZpAaWtM961fFTWtsnlzwvTbzBzaUzwQAoNATXKUlt0LZOFgnDcIyKCswAnAGdUF3LBrhGQ=@protonmail.com/

Why

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How

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

02

Exploit reality and attack path

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

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

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

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

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

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

CWE-190: Integer Overflow or Wraparound. The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

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

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

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

Official authority intelligence

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

BSI · German · WID-SEC-2024-3251Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241023Security Bulletin 23 Oct 2024

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

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

d?id=CVE-2024-48875 Référence CVE CVE-2024-49504 https://www.cve.org/CVERecord?id=CVE-2024-49504 Référence CVE CVE-2024-49568 https://www.cve.org/CVERecord?id=CVE-2024-49568 Référence CVE CVE-2024-49569 https://www.cve.org/CVERecord?id=CVE-2024-49569 Référence CVE CVE-2024-49855 https://www.cve.org/CVERecord?id=CVE-2024-49855 Référence CVE CVE-2024-49859 https://www.cve.org/CVERecord?id=CVE-2024-49859 Référence CVE CVE-2024-49861 https://www.cve.org/CVERecord?id=CVE-2024-49861 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49893 https://www.cve.org/CVERecord?id=CVE-2024-49893 Référence CVE CVE-2024-49898 https://www.cve.org/CVERecord?id=CVE-2024-49898 Référence CVE CVE-2024-49899 https://www.cve.org/CVERecord?id=CVE-2024-49899 Référence CVE CVE-2024-49901 https://www.cve.org/CVERecord?id=CVE-2024-49901 Référence CVE CVE-2024-49904 https://www.cve.org/CVERecord?id=CVE-2024-49904 Référence CVE CVE-2024-49905 https://www.cve.org/CVERecord?id=CVE-2024-49905 Référence CVE CVE-2024-49906 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-48875 Référence CVE CVE-2024-49504 https://www.cve.org/CVERecord?id=CVE-2024-49504 Référence CVE CVE-2024-49568 https://www.cve.org/CVERecord?id=CVE-2024-49568 Référence CVE CVE-2024-49569 https://www.cve.org/CVERecord?id=CVE-2024-49569 Référence CVE CVE-2024-49855 https://www.cve.org/CVERecord?id=CVE-2024-49855 Référence CVE CVE-2024-49859 https://www.cve.org/CVERecord?id=CVE-2024-49859 Référence CVE CVE-2024-49861 https://www.cve.org/CVERecord?id=CVE-2024-49861 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49893 https://www.cve.org/CVERecord?id=CVE-2024-49893 Référence CVE CVE-2024-49898 https://www.cve.org/CVERecord?id=CVE-2024-49898 Référence CVE CVE-2024-49899 https://www.cve.org/CVERecord?id=CVE-2024-49899 Référence CVE CVE-2024-49901 https://www.cve.org/CVERecord?id=CVE-2024-49901 Référence CVE CVE-2024-49904 https://www.cve.org/CVERecord?id=CVE-2024-49904 Référence CVE CVE-2024-49905 https://www.cve.org/CVERecord?id=CVE-2024-49905 Référence CVE CVE-2024-49906 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49893 https://www.cve.org/CVERecord?id=CVE-2024-49893 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49885 https://www.cve.org/CVERecord?id=CVE-2024-49885 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49893 https://www.cve.org/CVERecord?id=CVE-2024-49893 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49879 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49885 https://www.cve.org/CVERecord?id=CVE-2024-49885 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49887 https://www.cve.org/CVERecord?id=CVE-2024-49887 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=CVE-2024-49896 Référence CVE CVE-2024-49897 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49885 https://www.cve.org/CVERecord?id=CVE-2024-49885 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=CVE-2024-49896 Référence CVE CVE-2024-49897 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49879 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49885 https://www.cve.org/CVERecord?id=CVE-2024-49885 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49887 https://www.cve.org/CVERecord?id=CVE-2024-49887 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49893 https://www.cve.org/CVERecord?id=CVE-2024-49893 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=CVE-2024-49896 Référence CVE CVE-2024-49897 https://www.cve.org/CVERecord?id=CVE-2024-49897 Référence CVE CVE-2024-49898 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-38564 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41064 https://www.cve.org/CVERecord?id=CVE-2024-41064 Référence CVE CVE-2024-42124 https://www.cve.org/CVERecord?id=CVE-2024-42124 Référence CVE CVE-2024-43854 https://www.cve.org/CVERecord?id=CVE-2024-43854 Référence CVE CVE-2024-44994 https://www.cve.org/CVERecord?id=CVE-2024-44994 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-46695 https://www.cve.org/CVERecord?id=CVE-2024-46695 Référence CVE CVE-2024-47675 https://www.cve.org/CVERecord?id=CVE-2024-47675 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49949 https://www.cve.org/CVERecord?id=CVE-2024-49949 Référence CVE CVE-2024-50082 https://www.cve.org/CVERecord?id=CVE-2024-50082 Référence CVE CVE-2024-50099 https://www.cve.org/CVERecord?id=CVE-2024-50099 Référence CVE CVE-2024-50110 https://www.cve.org/CVERecord?id=CVE-2024-50110 Référence CVE CVE-2024-50142 https://www.cve.org/CVERecord?id=CVE-2024-50142 Référence CVE CVE-2024-50192 https://www.cve.org/CVERecord?id=CVE-2024-50192 Référence CVE CVE-2024-50251 https://www.cve.org/CVERecord?id=CVE-2024-50251 Référence CVE CVE-2024-50256 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49874 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=CVE-2024-49896 Référence CVE CVE-2024-49897 https://www.cve.org/CVERecord?id=CVE-2024-49897 Référence CVE CVE-2024-49898 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-012590Linux の 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
Fixed
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 21 Oct 2024 · Last source change 11 May 2026, 20:41 UTC · CWE-190 · Integer Overflow or Wraparound

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

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

Material change intelligence

What changed after publication

View recent updates ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-43588↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor 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-49888 · cve.blacktree.nl