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

net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 20 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 severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.57% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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: Within 3 daysRemediation target: Within 90 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 20 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.

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

1 current
CVE-2024-49568 · CSAF 2.0 · revision 56 · interimSUSE Product Security TeamCVE-2024-49568
246 known affected

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

  • 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 Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP5
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg When receiving proposal msg in server, the fields v2_ext_offset/ eid_cnt/ism_gid_cnt in proposal msg are from the remote client and can not be fully trusted. Especially the field v2_ext_offset, once exceed the max value, there has the chance to access wrong address, and crash may happen. This patch checks the fields v2_ext_offset/eid_cnt/ism_gid_cnt before using them.
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-43705

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg When receiving proposal msg in server, the fields v2_ext_offset/ eid_cnt/ism_gid_cnt in proposal msg are from the remote client and can not be fully trusted. Especially the field v2_ext_offset, once exceed the max value, there has the chance to access wrong address, and crash may happen. This patch checks the fields v2_ext_offset/eid_cnt/ism_gid_cnt before using them.

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
9.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 20 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: net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg When receiving proposal msg in server, the fields v2_ext_offset/ eid_cnt/ism_gid_cnt in proposal msg are from the remote client and can not be fully trusted. Especially the field v2_ext_offset, once exceed the max value, there has the chance to access wrong address, and crash may happen. This patch checks the fields v2_ext_offset/eid_cnt/ism_gid_cnt before using them.

What

In the Linux kernel, the following vulnerability has been resolved: net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg When receiving proposal msg in server, the fields v2_ext_offset/ eid_cnt/ism_gid_cnt in proposal msg are from the remote client and can not be fully trusted. Especially the field v2_ext_offset, once exceed the max value, there has the chance to access wrong address, and crash may happen. This patch checks the fields v2_ext_offset/eid_cnt/ism_gid_cnt before using them.

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 a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg When receiving proposal msg in server, the fields v2_ext_offset/ eid_cnt/ism_gid_cnt in proposal msg are from the remote client and can not be fully trusted. Especially the field v2_ext_offset, once exceed the max value, there has the chance to access wrong address, and crash may happen. This patch checks the fields v2_ext_offset/eid_cnt/ism_gid_cnt before using them.

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 a network path may attempt exploitation without authentication or user interaction. 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
a network path → vulnerable operation → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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:N/AC:L/PR:N/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.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of service
A

Official authority intelligence

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

ENISA EUVD · EUVD-2024-43705Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg When receiving proposal msg in server, the fields v2_ext_offset/ eid_cnt/ism_gid_cnt in proposal msg are from the remote client and can not be fully trusted. Especially the field v2_ext_offset, once exceed the max value, there has the chance to access wrong address, and crash may happen. This patch checks the fields v2_ext_offset/eid_cnt/ism_gid_cnt before using them.

Official EUVD record ↗
BSI · German · WID-SEC-2025-0047Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen und weitere nicht spezifizierte Angriffe zu starten.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250115Security Bulletin 15 Jan 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 15 Jan 2025, published on 15 January 2025. 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-47736 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47794 https://www.cve.org/CVERecord?id=CVE-2024-47794 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-47866 https://www.cve.org/CVERecord?id=CVE-2024-47866 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48875 https://www.cve.org/CVERecord?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=

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

d?id=CVE-2024-47736 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47794 https://www.cve.org/CVERecord?id=CVE-2024-47794 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-47866 https://www.cve.org/CVERecord?id=CVE-2024-47866 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48875 https://www.cve.org/CVERecord?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=

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

CVE-2025-39980 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39981 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39982 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39985 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39987 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39990 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39994 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39998 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49124 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49133 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2024-49568 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2024-53687 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2024-56709 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-21629 du 18 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-21645 du 18 octobre 2025 Une gestion de version détaillée se trouve à la fin de ce document. Risques Atteinte à la confidentialité des données Contournement de la politique de sécurité Déni de service Exécution de code arbitraire à distance Non spécifié par l'éditeur Systèmes affectés azl3 binutils 2.41-7 azl3 kernel 6.6.104.2-1 azl3 kernel 6.6.96.2-2 azl3 openssh 9.8p1-4 azl3 python3 3.12.9-

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

d?id=CVE-2024-36350 Référence CVE CVE-2024-36357 https://www.cve.org/CVERecord?id=CVE-2024-36357 Référence CVE CVE-2024-36972 https://www.cve.org/CVERecord?id=CVE-2024-36972 Référence CVE CVE-2024-36978 https://www.cve.org/CVERecord?id=CVE-2024-36978 Référence CVE CVE-2024-42134 https://www.cve.org/CVERecord?id=CVE-2024-42134 Référence CVE CVE-2024-42265 https://www.cve.org/CVERecord?id=CVE-2024-42265 Référence CVE CVE-2024-43869 https://www.cve.org/CVERecord?id=CVE-2024-43869 Référence CVE CVE-2024-44963 https://www.cve.org/CVERecord?id=CVE-2024-44963 Référence CVE CVE-2024-46713 https://www.cve.org/CVERecord?id=CVE-2024-46713 Référence CVE CVE-2024-49568 https://www.cve.org/CVERecord?id=CVE-2024-49568 Référence CVE CVE-2024-49861 https://www.cve.org/CVERecord?id=CVE-2024-49861 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-53057 https://www.cve.org/CVERecord?id=CVE-2024-53057 Référence CVE CVE-2024-53164 https://www.cve.org/CVERecord?id=CVE-2024-53164 Référence CVE CVE-2024-56613 https://www.cve.org/CVERecord?id=CVE-2024-56613 Référence CVE CVE-2024-56699 https://www.cve.org/CVERecord?id=CVE-2024-56699 Référence CVE CVE-2024-56742 https://www.cve.org/CVERecord?id=CVE-2024-56742 Référence CVE CVE-2024-57947 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53097 Référence CVE CVE-2024-26808 https://www.cve.org/CVERecord?id=CVE-2024-26808 Référence CVE CVE-2024-26831 https://www.cve.org/CVERecord?id=CVE-2024-26831 Référence CVE CVE-2024-26924 https://www.cve.org/CVERecord?id=CVE-2024-26924 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-35840 https://www.cve.org/CVERecord?id=CVE-2024-35840 Référence CVE CVE-2024-36978 https://www.cve.org/CVERecord?id=CVE-2024-36978 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-49568 https://www.cve.org/CVERecord?id=CVE-2024-49568 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-53057 https://www.cve.org/CVERecord?id=CVE-2024-53057 Référence CVE CVE-2024-53125 https://www.cve.org/CVERecord?id=CVE-2024-53125 Référence CVE CVE-2024-53141 https://www.cve.org/CVERecord?id=CVE-2024-53141 Référence CVE CVE-2024-56613 https://www.cve.org/CVERecord?id=CVE-2024-56613 Référence CVE CVE-2024-56699 https://www.cve.org/CVERecord?id=CVE-2024-56699 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=CVE-2024-56770 Référence CVE CVE-2024-57947 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35790 Référence CVE CVE-2024-35839 https://www.cve.org/CVERecord?id=CVE-2024-35839 Référence CVE CVE-2024-35840 https://www.cve.org/CVERecord?id=CVE-2024-35840 Référence CVE CVE-2024-36959 https://www.cve.org/CVERecord?id=CVE-2024-36959 Référence CVE CVE-2024-36978 https://www.cve.org/CVERecord?id=CVE-2024-36978 Référence CVE CVE-2024-38588 https://www.cve.org/CVERecord?id=CVE-2024-38588 Référence CVE CVE-2024-41085 https://www.cve.org/CVERecord?id=CVE-2024-41085 Référence CVE CVE-2024-43869 https://www.cve.org/CVERecord?id=CVE-2024-43869 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-49568 https://www.cve.org/CVERecord?id=CVE-2024-49568 Référence CVE CVE-2024-50034 https://www.cve.org/CVERecord?id=CVE-2024-50034 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-50293 https://www.cve.org/CVERecord?id=CVE-2024-50293 Référence CVE CVE-2024-53057 https://www.cve.org/CVERecord?id=CVE-2024-53057 Référence CVE CVE-2024-53125 https://www.cve.org/CVERecord?id=CVE-2024-53125 Référence CVE CVE-2024-53141 https://www.cve.org/CVERecord?id=CVE-2024-53141 Référence CVE CVE-2024-53197 https://www.cve.org/CVERecord?id=CVE-2024-53197 Référence CVE CVE-2024-56541 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26831 Référence CVE CVE-2024-26924 https://www.cve.org/CVERecord?id=CVE-2024-26924 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-35840 https://www.cve.org/CVERecord?id=CVE-2024-35840 Référence CVE CVE-2024-36978 https://www.cve.org/CVERecord?id=CVE-2024-36978 Référence CVE CVE-2024-41085 https://www.cve.org/CVERecord?id=CVE-2024-41085 Référence CVE CVE-2024-43869 https://www.cve.org/CVERecord?id=CVE-2024-43869 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-49568 https://www.cve.org/CVERecord?id=CVE-2024-49568 Référence CVE CVE-2024-50034 https://www.cve.org/CVERecord?id=CVE-2024-50034 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-50293 https://www.cve.org/CVERecord?id=CVE-2024-50293 Référence CVE CVE-2024-53125 https://www.cve.org/CVERecord?id=CVE-2024-53125 Référence CVE CVE-2024-53141 https://www.cve.org/CVERecord?id=CVE-2024-53141 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=CVE-2024-53168 Référence CVE CVE-2024-53197 https://www.cve.org/CVERecord?id=CVE-2024-53197 Référence CVE CVE-2024-56541 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46713 Référence CVE CVE-2024-46751 https://www.cve.org/CVERecord?id=CVE-2024-46751 Référence CVE CVE-2024-46752 https://www.cve.org/CVERecord?id=CVE-2024-46752 Référence CVE CVE-2024-46763 https://www.cve.org/CVERecord?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-46814 https://www.cve.org/CVERecord?id=CVE-2024-46814 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-49568 https://www.cve.org/CVERecord?id=CVE-2024-49568 Référence CVE CVE-2024-49570 https://www.cve.org/CVERecord?id=CVE-2024-49570 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-49994 https://www.cve.org/CVERecord?id=CVE-2024-49994 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=

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

d?id=CVE-2024-47141 Référence CVE CVE-2024-47143 https://www.cve.org/CVERecord?id=CVE-2024-47143 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-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48875 https://www.cve.org/CVERecord?id=CVE-2024-48875 Référence CVE CVE-2024-48876 https://www.cve.org/CVERecord?id=CVE-2024-48876 Référence CVE CVE-2024-48881 https://www.cve.org/CVERecord?id=CVE-2024-48881 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-49571 https://www.cve.org/CVERecord?id=CVE-2024-49571 Référence CVE CVE-2024-50051 https://www.cve.org/CVERecord?id=CVE-2024-50051 Référence CVE CVE-2024-51729 https://www.cve.org/CVERecord?id=CVE-2024-51729 Référence CVE CVE-2024-52319 https://www.cve.org/CVERecord?id=CVE-2024-52319 Référence CVE CVE-2024-52332 https://www.cve.org/CVERecord?id=CVE-2024-52332 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53140 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-029165Linux の 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: < 5.10, 5.10.271 ≤ 5.10.*, 5.15.222 ≤ 5.15.*, 6.1.189 ≤ 6.1.*, 6.6.68 ≤ 6.6.*, 6.12.7 ≤ 6.12.*, 6.13 ≤ *
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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 11 Jan 2025 · Last source change 3 Oct 2026, 10:55 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-43705
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    8c3dca341aea885249e08856c4380300b75d2cf5 < 295a92e3df32e72aff0f4bc25c310e349d07ffbf; 8c3dca341aea885249e08856c4380300b75d2cf5 < 42f6beb2d5779429417b5f8115a4e3fa695d2a6c; 8c3dca341aea885249e08856c4380300b75d2cf5 < 7863c9f3d24ba49dbead7e03dfbe40deb5888fdf; 5.10 · Fixed: < 5.10; 6.6.68 ≤ 6.6.*; 6.12.7 ≤ 6.12.*; 6.13 ≤ *
    After
    Linux: 8c3dca341aea885249e08856c4380300b75d2cf5 < 9cc0170ae646876aa5de2f0cad3066ce53e86f27, 8c3dca341aea885249e08856c4380300b75d2cf5 < 49798283fce4c1a24fb1ba4c7c39127739535571, 8c3dca341aea885249e08856c4380300b75d2cf5 < 690b9a8db9460d065785548e43fd6a02d247c1b7, 8c3dca341aea885249e08856c4380300b75d2cf5 < 295a92e3df32e72aff0f4bc25c310e349d07ffbf, 8c3dca341aea885249e08856c4380300b75d2cf5 < 42f6beb2d5779429417b5f8115a4e3fa695d2a6c, 8c3dca341aea885249e08856c4380300b75d2cf5 < 7863c9f3d24ba49dbead7e03dfbe40deb5888fdf, 5.10 · Fixed: Linux: < 5.10, 5.10.271 ≤ 5.10.*, 5.15.222 ≤ 5.15.*, 6.1.189 ≤ 6.1.*, 6.6.68 ≤ 6.6.*, 6.12.7 ≤ 6.12.*, 6.13 ≤ *
    CNA ↗
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-43705↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor 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-49568 · cve.blacktree.nl