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

vsock: fix recursive ->recvmsg calls

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 14 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.21% 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 14 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.

18 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 14 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.10.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.7-1Debian Security Tracker ↗Source updated 6 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-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.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
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-44996 · CSAF 2.0 · revision 82 · interimSUSE Product Security TeamCVE-2024-44996
39 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Server 16.0
  • kernel-devel as component of SUSE Linux Enterprise Server 16.0
  • kernel-devel-azure as component of SUSE Linux Enterprise Server 16.0
  • kernel-macros as component of SUSE Linux Enterprise Server 16.0
  • kernel-source as component of SUSE Linux Enterprise Server 16.0
  • kernel-source-azure as component of SUSE Linux Enterprise Server 16.0
  • kernel-source-vanilla as component of SUSE Linux Enterprise Server 16.0
  • kernel-default as component of SUSE Linux Enterprise Server for SAP applications 16.0
Summary
In the Linux kernel, the following vulnerability has been resolved: vsock: fix recursive ->recvmsg calls After a vsock socket has been added to a BPF sockmap, its prot->recvmsg has been replaced with vsock_bpf_recvmsg(). Thus the following recursiion could happen: vsock_bpf_recvmsg() -> __vsock_recvmsg() -> vsock_connectible_recvmsg() -> prot->recvmsg() -> vsock_bpf_recvmsg() again We need to fix it by calling the original ->recvmsg() without any BPF sockmap logic in __vsock_recvmsg().
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-41198

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 14 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: vsock: fix recursive ->recvmsg calls After a vsock socket has been added to a BPF sockmap, its prot->recvmsg has been replaced with vsock_bpf_recvmsg(). Thus the following recursiion could happen: vsock_bpf_recvmsg() -> __vsock_recvmsg() -> vsock_connectible_recvmsg() -> prot->recvmsg() -> vsock_bpf_recvmsg() again We need to fix it by calling the original ->recvmsg() without any BPF sockmap logic in __vsock_recvmsg().

What

In the Linux kernel, the following vulnerability has been resolved: vsock: fix recursive ->recvmsg calls After a vsock socket has been added to a BPF sockmap, its prot->recvmsg has been replaced with vsock_bpf_recvmsg(). Thus the following recursiion could happen: vsock_bpf_recvmsg() -> __vsock_recvmsg() -> vsock_connectible_recvmsg() -> prot->recvmsg() -> vsock_bpf_recvmsg() again We need to fix it by calling the original ->recvmsg() without any BPF sockmap logic in __vsock_recvmsg().

Why

The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

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: vsock: fix recursive ->recvmsg calls After a vsock socket has been added to a BPF sockmap, its prot->recvmsg has been replaced with vsock_bpf_recvmsg(). Thus the following recursiion could happen: vsock_bpf_recvmsg() -> __vsock_recvmsg() -> vsock_connectible_recvmsg() -> prot->recvmsg() -> vsock_bpf_recvmsg() again We need to fix it by calling the original ->recvmsg() without any BPF sockmap logic in __vsock_recvmsg().

Why

The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

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 → Uncontrolled Recursion → 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-674 ↗

CWE-674: Uncontrolled Recursion. The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

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

Official authority intelligence

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

BSI · German · WID-SEC-2024-2057Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service oder unspezifischer Angriff

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder weitere unspezifische Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240911Security Bulletin 11 Sep 2024

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

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

d?id=CVE-2024-43910 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-44967 https://www.cve.org/CVERecord?id=CVE-2024-44967 Référence CVE CVE-2024-44975 https://www.cve.org/CVERecord?id=CVE-2024-44975 Référence CVE CVE-2024-44983 https://www.cve.org/CVERecord?id=CVE-2024-44983 Référence CVE CVE-2024-44984 https://www.cve.org/CVERecord?id=CVE-2024-44984 Référence CVE CVE-2024-44986 https://www.cve.org/CVERecord?id=CVE-2024-44986 Référence CVE CVE-2024-44994 https://www.cve.org/CVERecord?id=CVE-2024-44994 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-45000 https://www.cve.org/CVERecord?id=CVE-2024-45000 Référence CVE CVE-2024-45001 https://www.cve.org/CVERecord?id=CVE-2024-45001 Référence CVE CVE-2024-45005 https://www.cve.org/CVERecord?id=CVE-2024-45005 Référence CVE CVE-2024-45010 https://www.cve.org/CVERecord?id=CVE-2024-45010 Référence CVE CVE-2024-45012 https://www.cve.org/CVERecord?id=CVE-2024-45012 Référence CVE CVE-2024-45013 https://www.cve.org/CVERecord?id=CVE-2024-45013 Référence CVE CVE-2024-45017 https://www.cve.org/CVERecord?id=CVE-2024-45017 Référence CVE CVE-2024-45019 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41013 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41057 https://www.cve.org/CVERecord?id=CVE-2024-41057 Référence CVE CVE-2024-41059 https://www.cve.org/CVERecord?id=CVE-2024-41059 Référence CVE CVE-2024-42133 https://www.cve.org/CVERecord?id=CVE-2024-42133 Référence CVE CVE-2024-42232 https://www.cve.org/CVERecord?id=CVE-2024-42232 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-43913 https://www.cve.org/CVERecord?id=CVE-2024-43913 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-45828 https://www.cve.org/CVERecord?id=CVE-2024-45828 Référence CVE CVE-2024-46680 https://www.cve.org/CVERecord?id=CVE-2024-46680 Référence CVE CVE-2024-46765 https://www.cve.org/CVERecord?id=CVE-2024-46765 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-46896 https://www.cve.org/CVERecord?id=CVE-2024-46896 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-47143 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40909 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41059 https://www.cve.org/CVERecord?id=CVE-2024-41059 Référence CVE CVE-2024-41087 https://www.cve.org/CVERecord?id=CVE-2024-41087 Référence CVE CVE-2024-42133 https://www.cve.org/CVERecord?id=CVE-2024-42133 Référence CVE CVE-2024-42232 https://www.cve.org/CVERecord?id=CVE-2024-42232 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-49854 https://www.cve.org/CVERecord?id=CVE-2024-49854 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49915 https://www.cve.org/CVERecord?id=CVE-2024-49915 Référence CVE CVE-2024-49944 https://www.cve.org/CVERecord?id=CVE-2024-49944 Référence CVE CVE-2024-49952 https://www.cve.org/CVERecord?id=CVE-2024-49952 Référence CVE CVE-2024-50016 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36915 Référence CVE CVE-2024-36964 https://www.cve.org/CVERecord?id=CVE-2024-36964 Référence CVE CVE-2024-39480 https://www.cve.org/CVERecord?id=CVE-2024-39480 Référence CVE CVE-2024-40909 https://www.cve.org/CVERecord?id=CVE-2024-40909 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41059 https://www.cve.org/CVERecord?id=CVE-2024-41059 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-49854 https://www.cve.org/CVERecord?id=CVE-2024-49854 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49915 https://www.cve.org/CVERecord?id=CVE-2024-49915 Référence CVE CVE-2024-50016 https://www.cve.org/CVERecord?id=CVE-2024-50016 Référence CVE CVE-2024-50018 https://www.cve.org/CVERecord?id=CVE-2024-50018 Référence CVE CVE-2024-50039 https://www.cve.org/CVERecord?id=CVE-2024-50039 Référence CVE CVE-2024-50047 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-44985 Référence CVE CVE-2024-44986 https://www.cve.org/CVERecord?id=CVE-2024-44986 Référence CVE CVE-2024-44987 https://www.cve.org/CVERecord?id=CVE-2024-44987 Référence CVE CVE-2024-44988 https://www.cve.org/CVERecord?id=CVE-2024-44988 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-44991 https://www.cve.org/CVERecord?id=CVE-2024-44991 Référence CVE CVE-2024-44993 https://www.cve.org/CVERecord?id=CVE-2024-44993 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-44998 https://www.cve.org/CVERecord?id=CVE-2024-44998 Référence CVE CVE-2024-44999 https://www.cve.org/CVERecord?id=CVE-2024-44999 Référence CVE CVE-2024-45000 https://www.cve.org/CVERecord?id=CVE-2024-45000 Référence CVE CVE-2024-45001 https://www.cve.org/CVERecord?id=CVE-2024-45001 Référence CVE CVE-2024-45002 https://www.cve.org/CVERecord?id=CVE-2024-45002 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45005 https://www.cve.org/CVERecord?id=CVE-2024-45005 Référence CVE CVE-2024-45006 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-44985 Référence CVE CVE-2024-44986 https://www.cve.org/CVERecord?id=CVE-2024-44986 Référence CVE CVE-2024-44987 https://www.cve.org/CVERecord?id=CVE-2024-44987 Référence CVE CVE-2024-44988 https://www.cve.org/CVERecord?id=CVE-2024-44988 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-44991 https://www.cve.org/CVERecord?id=CVE-2024-44991 Référence CVE CVE-2024-44993 https://www.cve.org/CVERecord?id=CVE-2024-44993 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-44998 https://www.cve.org/CVERecord?id=CVE-2024-44998 Référence CVE CVE-2024-44999 https://www.cve.org/CVERecord?id=CVE-2024-44999 Référence CVE CVE-2024-45000 https://www.cve.org/CVERecord?id=CVE-2024-45000 Référence CVE CVE-2024-45001 https://www.cve.org/CVERecord?id=CVE-2024-45001 Référence CVE CVE-2024-45002 https://www.cve.org/CVERecord?id=CVE-2024-45002 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45005 https://www.cve.org/CVERecord?id=CVE-2024-45005 Référence CVE CVE-2024-45006 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-008311Linux の 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: < 6.4, 6.6.48 ≤ 6.6.*, 6.10.7 ≤ 6.10.*, 6.11 ≤ *
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 4 Sept 2024 · Last source change 11 May 2026, 20:33 UTC · CWE-674 · Uncontrolled Recursion

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-41198
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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
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-44996 · cve.blacktree.nl