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

l2tp: prevent possible tunnel refcount underflow

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 206 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 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: 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.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 206 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.

25 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 22 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 · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.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-fdeAffected, 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-intelAffected, 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-nvidia-tegraAffected, 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-raspi-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-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.

2 current
CVE-2024-49940 · CSAF 2.0 · revision 78 · interimSUSE Product Security TeamCVE-2024-49940
447 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • 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
Summary
In the Linux kernel, the following vulnerability has been resolved: l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session->tunnel is non-NULL. However, session->tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session->tunnel is non-NULL when the tunnel refcount hasn't been bumped. Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session->tunnel to get the tunnel's encap. Add an encap arg to l2tp_session_set_header_len to avoid using session->tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn't yet have session->tunnel set. Add a check for this case.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2024-49940 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: l2tp: prevent possible tunnel refcount underflow
184 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 Linux kernel's implementation of the Layer 2 Tunneling Protocol (L2TP). A race condition during the creation and registration of L2TP sessions can lead to a tunnel reference count underflow. This issue allows a local attacker with low privileges to cause a Denial of Service (DoS) by making the system unstable or unresponsive.
Remediation
To mitigate this issue, prevent the `l2tp_core` kernel module from loading. This can be achieved by blacklisting the module. To temporarily unload the module (if not in use): `# modprobe -r l2tp_core` To permanently blacklist the module, create a configuration file: `# echo "blacklist l2tp_core" >> /etc/modprobe.d/blacklist-l2tp.conf` A system reboot or module reload is required for the change to take full effect. Disabling this module may impact L2TP VPN functionality.
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-43621

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 206 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: l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session->tunnel is non-NULL. However, session->tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session->tunnel is non-NULL when the tunnel refcount hasn't been bumped. Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session->tunnel to get the tunnel's encap. Add an encap arg to l2tp_session_set_header_len to avoid using session->tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn't yet have session->tunnel set. Add a check for this case.

What

In the Linux kernel, the following vulnerability has been resolved: l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session->tunnel is non-NULL. However, session->tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session->tunnel is non-NULL when the tunnel refcount hasn't been bumped. Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session->tunnel to get the tunnel's encap. Add an encap arg to l2tp_session_set_header_len to avoid using session->tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn't yet have session->tunnel set. Add a check for this case.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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: l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session->tunnel is non-NULL. However, session->tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session->tunnel is non-NULL when the tunnel refcount hasn't been bumped. Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session->tunnel to get the tunnel's encap. Add an encap arg to l2tp_session_set_header_len to avoid using session->tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn't yet have session->tunnel set. Add a check for this case.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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 → vulnerable operation → 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.
CWE not yet assigned
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.
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-1439Dell Secure Connect Gateway: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
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-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2021-47378 Référence CVE CVE-2022-50401 https://www.cve.org/CVERecord?id=CVE-2022-50401 Référence CVE CVE-2024-14040 https://www.cve.org/CVERecord?id=CVE-2024-14040 Référence CVE CVE-2024-35948 https://www.cve.org/CVERecord?id=CVE-2024-35948 Référence CVE CVE-2024-41008 https://www.cve.org/CVERecord?id=CVE-2024-41008 Référence CVE CVE-2024-43872 https://www.cve.org/CVERecord?id=CVE-2024-43872 Référence CVE CVE-2024-44932 https://www.cve.org/CVERecord?id=CVE-2024-44932 Référence CVE CVE-2024-44964 https://www.cve.org/CVERecord?id=CVE-2024-44964 Référence CVE CVE-2024-49932 https://www.cve.org/CVERecord?id=CVE-2024-49932 Référence CVE CVE-2024-49940 https://www.cve.org/CVERecord?id=CVE-2024-49940 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-50217 https://www.cve.org/CVERecord?id=CVE-2024-50217 Référence CVE CVE-2024-52560 https://www.cve.org/CVERecord?id=CVE-2024-52560 Référence CVE CVE-2024-53098 https://www.cve.org/CVERecord?id=CVE-2024-53098 Référence CVE CVE-2024-56552 https://www.cve.org/CVERecord?id=CVE-2024-56552 Référence CVE CVE-2024-56591 https://www.cve.org/CVERecord?id=CVE-2024-56591 Référence CVE CVE-2024-57857 https://www.cve.org/CVERecord?id=CVE-2024-57857 Référence CVE CVE-2024-58089 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49921 Référence CVE CVE-2024-49922 https://www.cve.org/CVERecord?id=CVE-2024-49922 Référence CVE CVE-2024-49923 https://www.cve.org/CVERecord?id=CVE-2024-49923 Référence CVE CVE-2024-49928 https://www.cve.org/CVERecord?id=CVE-2024-49928 Référence CVE CVE-2024-49929 https://www.cve.org/CVERecord?id=CVE-2024-49929 Référence CVE CVE-2024-49931 https://www.cve.org/CVERecord?id=CVE-2024-49931 Référence CVE CVE-2024-49932 https://www.cve.org/CVERecord?id=CVE-2024-49932 Référence CVE CVE-2024-49934 https://www.cve.org/CVERecord?id=CVE-2024-49934 Référence CVE CVE-2024-49939 https://www.cve.org/CVERecord?id=CVE-2024-49939 Référence CVE CVE-2024-49940 https://www.cve.org/CVERecord?id=CVE-2024-49940 Référence CVE CVE-2024-49945 https://www.cve.org/CVERecord?id=CVE-2024-49945 Référence CVE CVE-2024-49968 https://www.cve.org/CVERecord?id=CVE-2024-49968 Référence CVE CVE-2024-49970 https://www.cve.org/CVERecord?id=CVE-2024-49970 Référence CVE CVE-2024-49978 https://www.cve.org/CVERecord?id=CVE-2024-49978 Référence CVE CVE-2024-49987 https://www.cve.org/CVERecord?id=CVE-2024-49987 Référence CVE CVE-2024-49988 https://www.cve.org/CVERecord?id=CVE-2024-49988 Référence CVE CVE-2024-49990 https://www.cve.org/CVERecord?id=CVE-2024-49990 Référence CVE CVE-2024-49991 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-49921 Référence CVE CVE-2024-49922 https://www.cve.org/CVERecord?id=CVE-2024-49922 Référence CVE CVE-2024-49923 https://www.cve.org/CVERecord?id=CVE-2024-49923 Référence CVE CVE-2024-49928 https://www.cve.org/CVERecord?id=CVE-2024-49928 Référence CVE CVE-2024-49929 https://www.cve.org/CVERecord?id=CVE-2024-49929 Référence CVE CVE-2024-49931 https://www.cve.org/CVERecord?id=CVE-2024-49931 Référence CVE CVE-2024-49932 https://www.cve.org/CVERecord?id=CVE-2024-49932 Référence CVE CVE-2024-49934 https://www.cve.org/CVERecord?id=CVE-2024-49934 Référence CVE CVE-2024-49939 https://www.cve.org/CVERecord?id=CVE-2024-49939 Référence CVE CVE-2024-49940 https://www.cve.org/CVERecord?id=CVE-2024-49940 Référence CVE CVE-2024-49945 https://www.cve.org/CVERecord?id=CVE-2024-49945 Référence CVE CVE-2024-49968 https://www.cve.org/CVERecord?id=CVE-2024-49968 Référence CVE CVE-2024-49970 https://www.cve.org/CVERecord?id=CVE-2024-49970 Référence CVE CVE-2024-49978 https://www.cve.org/CVERecord?id=CVE-2024-49978 Référence CVE CVE-2024-49987 https://www.cve.org/CVERecord?id=CVE-2024-49987 Référence CVE CVE-2024-49988 https://www.cve.org/CVERecord?id=CVE-2024-49988 Référence CVE CVE-2024-49990 https://www.cve.org/CVERecord?id=CVE-2024-49990 Référence CVE CVE-2024-49991 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46763 Référence CVE CVE-2024-46782 https://www.cve.org/CVERecord?id=CVE-2024-46782 Référence CVE CVE-2024-46796 https://www.cve.org/CVERecord?id=CVE-2024-46796 Référence CVE CVE-2024-46865 https://www.cve.org/CVERecord?id=CVE-2024-46865 Référence CVE CVE-2024-47408 https://www.cve.org/CVERecord?id=CVE-2024-47408 Référence CVE CVE-2024-47794 https://www.cve.org/CVERecord?id=CVE-2024-47794 Référence CVE CVE-2024-49571 https://www.cve.org/CVERecord?id=CVE-2024-49571 Référence CVE CVE-2024-49855 https://www.cve.org/CVERecord?id=CVE-2024-49855 Référence CVE CVE-2024-49924 https://www.cve.org/CVERecord?id=CVE-2024-49924 Référence CVE CVE-2024-49940 https://www.cve.org/CVERecord?id=CVE-2024-49940 Référence CVE CVE-2024-49994 https://www.cve.org/CVERecord?id=CVE-2024-49994 Référence CVE CVE-2024-50029 https://www.cve.org/CVERecord?id=CVE-2024-50029 Référence CVE CVE-2024-50036 https://www.cve.org/CVERecord?id=CVE-2024-50036 Référence CVE CVE-2024-50038 https://www.cve.org/CVERecord?id=CVE-2024-50038 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50083 https://www.cve.org/CVERecord?id=CVE-2024-50083 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-50126 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26634 Référence CVE CVE-2024-35910 https://www.cve.org/CVERecord?id=CVE-2024-35910 Référence CVE CVE-2024-36968 https://www.cve.org/CVERecord?id=CVE-2024-36968 Référence CVE CVE-2024-38559 https://www.cve.org/CVERecord?id=CVE-2024-38559 Référence CVE CVE-2024-41005 https://www.cve.org/CVERecord?id=CVE-2024-41005 Référence CVE CVE-2024-41090 https://www.cve.org/CVERecord?id=CVE-2024-41090 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-49571 https://www.cve.org/CVERecord?id=CVE-2024-49571 Référence CVE CVE-2024-49935 https://www.cve.org/CVERecord?id=CVE-2024-49935 Référence CVE CVE-2024-49940 https://www.cve.org/CVERecord?id=CVE-2024-49940 Référence CVE CVE-2024-50269 https://www.cve.org/CVERecord?id=CVE-2024-50269 Référence CVE CVE-2024-50290 https://www.cve.org/CVERecord?id=CVE-2024-50290 Référence CVE CVE-2024-53063 https://www.cve.org/CVERecord?id=CVE-2024-53063 Référence CVE CVE-2024-53124 https://www.cve.org/CVERecord?id=CVE-2024-53124 Référence CVE CVE-2024-53140 https://www.cve.org/CVERecord?id=CVE-2024-53140 Référence CVE CVE-2024-53176 https://www.cve.org/CVERecord?id=CVE-2024-53176 Référence CVE CVE-2024-53178 https://www.cve.org/CVERecord?id=CVE-2024-53178 Référence CVE CVE-2024-53680 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-43820 Référence CVE CVE-2024-46736 https://www.cve.org/CVERecord?id=CVE-2024-46736 Référence CVE CVE-2024-46782 https://www.cve.org/CVERecord?id=CVE-2024-46782 Référence CVE CVE-2024-46796 https://www.cve.org/CVERecord?id=CVE-2024-46796 Référence CVE CVE-2024-47408 https://www.cve.org/CVERecord?id=CVE-2024-47408 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47794 https://www.cve.org/CVERecord?id=CVE-2024-47794 Référence CVE CVE-2024-49571 https://www.cve.org/CVERecord?id=CVE-2024-49571 Référence CVE CVE-2024-49924 https://www.cve.org/CVERecord?id=CVE-2024-49924 Référence CVE CVE-2024-49940 https://www.cve.org/CVERecord?id=CVE-2024-49940 Référence CVE CVE-2024-49994 https://www.cve.org/CVERecord?id=CVE-2024-49994 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50126 https://www.cve.org/CVERecord?id=CVE-2024-50126 Référence CVE CVE-2024-50140 https://www.cve.org/CVERecord?id=CVE-2024-50140 Référence CVE CVE-2024-50152 https://www.cve.org/CVERecord?id=CVE-2024-50152 Référence CVE CVE-2024-50290 https://www.cve.org/CVERecord?id=CVE-2024-50290 Référence CVE CVE-2024-52559 https://www.cve.org/CVERecord?id=CVE-2024-52559 Référence CVE CVE-2024-53057 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-49931 Référence CVE CVE-2024-49932 https://www.cve.org/CVERecord?id=CVE-2024-49932 Référence CVE CVE-2024-49933 https://www.cve.org/CVERecord?id=CVE-2024-49933 Référence CVE CVE-2024-49934 https://www.cve.org/CVERecord?id=CVE-2024-49934 Référence CVE CVE-2024-49935 https://www.cve.org/CVERecord?id=CVE-2024-49935 Référence CVE CVE-2024-49936 https://www.cve.org/CVERecord?id=CVE-2024-49936 Référence CVE CVE-2024-49937 https://www.cve.org/CVERecord?id=CVE-2024-49937 Référence CVE CVE-2024-49938 https://www.cve.org/CVERecord?id=CVE-2024-49938 Référence CVE CVE-2024-49939 https://www.cve.org/CVERecord?id=CVE-2024-49939 Référence CVE CVE-2024-49940 https://www.cve.org/CVERecord?id=CVE-2024-49940 Référence CVE CVE-2024-49941 https://www.cve.org/CVERecord?id=CVE-2024-49941 Référence CVE CVE-2024-49942 https://www.cve.org/CVERecord?id=CVE-2024-49942 Référence CVE CVE-2024-49943 https://www.cve.org/CVERecord?id=CVE-2024-49943 Référence CVE CVE-2024-49944 https://www.cve.org/CVERecord?id=CVE-2024-49944 Référence CVE CVE-2024-49945 https://www.cve.org/CVERecord?id=CVE-2024-49945 Référence CVE CVE-2024-49946 https://www.cve.org/CVERecord?id=CVE-2024-49946 Référence CVE CVE-2024-49947 https://www.cve.org/CVERecord?id=CVE-2024-49947 Référence CVE CVE-2024-49948 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-49931 Référence CVE CVE-2024-49932 https://www.cve.org/CVERecord?id=CVE-2024-49932 Référence CVE CVE-2024-49933 https://www.cve.org/CVERecord?id=CVE-2024-49933 Référence CVE CVE-2024-49934 https://www.cve.org/CVERecord?id=CVE-2024-49934 Référence CVE CVE-2024-49935 https://www.cve.org/CVERecord?id=CVE-2024-49935 Référence CVE CVE-2024-49936 https://www.cve.org/CVERecord?id=CVE-2024-49936 Référence CVE CVE-2024-49937 https://www.cve.org/CVERecord?id=CVE-2024-49937 Référence CVE CVE-2024-49938 https://www.cve.org/CVERecord?id=CVE-2024-49938 Référence CVE CVE-2024-49939 https://www.cve.org/CVERecord?id=CVE-2024-49939 Référence CVE CVE-2024-49940 https://www.cve.org/CVERecord?id=CVE-2024-49940 Référence CVE CVE-2024-49941 https://www.cve.org/CVERecord?id=CVE-2024-49941 Référence CVE CVE-2024-49942 https://www.cve.org/CVERecord?id=CVE-2024-49942 Référence CVE CVE-2024-49943 https://www.cve.org/CVERecord?id=CVE-2024-49943 Référence CVE CVE-2024-49944 https://www.cve.org/CVERecord?id=CVE-2024-49944 Référence CVE CVE-2024-49945 https://www.cve.org/CVERecord?id=CVE-2024-49945 Référence CVE CVE-2024-49946 https://www.cve.org/CVERecord?id=CVE-2024-49946 Référence CVE CVE-2024-49947 https://www.cve.org/CVERecord?id=CVE-2024-49947 Référence CVE CVE-2024-49948 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-012604Linux の 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
Linux: < 4.15, 6.11.3 ≤ 6.11.*, 6.12 ≤ *
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 5 Aug 2026, 11:40 UTC · CWE not yet assigned

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-43621
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

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-43621↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-49940 · cve.blacktree.nl