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

topology: Keep the cpumask unchanged when printing cpumap

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 24 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 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.22% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: 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 24 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 19 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.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.128-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.10-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-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.

2 current
CVE-2024-57917 · CSAF 2.0 · revision 66 · interimSUSE Product Security TeamCVE-2024-57917
161 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 High Availability Extension 15 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: topology: Keep the cpumask unchanged when printing cpumap During fuzz testing, the following warning was discovered: different return values (15 and 11) from vsnprintf("%*pbl ", ...) test:keyward is WARNING in kvasprintf WARNING: CPU: 55 PID: 1168477 at lib/kasprintf.c:30 kvasprintf+0x121/0x130 Call Trace: kvasprintf+0x121/0x130 kasprintf+0xa6/0xe0 bitmap_print_to_buf+0x89/0x100 core_siblings_list_read+0x7e/0xb0 kernfs_file_read_iter+0x15b/0x270 new_sync_read+0x153/0x260 vfs_read+0x215/0x290 ksys_read+0xb9/0x160 do_syscall_64+0x56/0x100 entry_SYSCALL_64_after_hwframe+0x78/0xe2 The call trace shows that kvasprintf() reported this warning during the printing of core_siblings_list. kvasprintf() has several steps: (1) First, calculate the length of the resulting formatted string. (2) Allocate a buffer based on the returned length. (3) Then, perform the actual string formatting. (4) Check whether the lengths of the formatted strings returned in steps (1) and (2) are consistent. If the core_cpumask is modified between steps (1) and (3), the lengths obtained in these two steps may not match. Indeed our test includes cpu hotplugging, which should modify core_cpumask while printing. To fix this issue, cache the cpumask into a temporary variable before calling cpumap_print_{list, cpumask}_to_buf(), to keep it unchanged during the printing process.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: topology: Keep the cpumask unchanged when printing cpumap During fuzz testing, the following warning was discovered: different return values (15 and 11) from vsnprintf("%*pbl ", ...) test:keyward is WARNING in kvasprintf WARNING: CPU: 55 PID: 1168477 at lib/kasprintf.c:30 kvasprintf+0x121/0x130 Call Trace: kvasprintf+0x121/0x130 kasprintf+0xa6/0xe0 bitmap_print_to_buf+0x89/0x100 core_siblings_list_read+0x7e/0xb0 kernfs_file_read_iter+0x15b/0x270 new_sync_read+0x153/0x260 vfs_read+0x215/0x290 ksys_read+0xb9/0x160 do_syscall_64+0x56/0x100 entry_SYSCALL_64_after_hwframe+0x78/0xe2 The call trace shows that kvasprintf() reported this warning during the printing of core_siblings_list. kvasprintf() has several steps: (1) First, calculate the length of the resulting formatted string. (2) Allocate a buffer based on the returned length. (3) Then, perform the actual string formatting. (4) Check whether the lengths of the formatted strings returned in steps (1) and (2) are consistent. If the core_cpumask is modified between steps (1) and (3), the lengths obtained in these two steps may not match. Indeed our test includes cpu hotplugging, which should modify core_cpumask while printing. To fix this issue, cache the cpumask into a temporary variable before calling cpumap_print_{list, cpumask}_to_buf(), to keep it unchanged during the printing process.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-53820

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: topology: Keep the cpumask unchanged when printing cpumap During fuzz testing, the following warning was discovered: different return values (15 and 11) from vsnprintf("%*pbl ", ...) test:keyward is WARNING in kvasprintf WARNING: CPU: 55 PID: 1168477 at lib/kasprintf.c:30 kvasprintf+0x121/0x130 Call Trace: kvasprintf+0x121/0x130 kasprintf+0xa6/0xe0 bitmap_print_to_buf+0x89/0x100 core_siblings_list_read+0x7e/0xb0 kernfs_file_read_iter+0x15b/0x270 new_sync_read+0x153/0x260 vfs_read+0x215/0x290 ksys_read+0xb9/0x160 do_syscall_64+0x56/0x100 entry_SYSCALL_64_after_hwframe+0x78/0xe2 The call trace shows that kvasprintf() reported this warning during the printing of core_siblings_list. kvasprintf() has several steps: (1) First, calculate the length of the resulting formatted string. (2) Allocate a buffer based on the returned length. (3) Then, perform the actual string formatting. (4) Check whether the lengths of the formatted strings returned in steps (1) and (2) are consistent. If the core_cpumask is modified between steps (1) and (3), the lengths obtained in these two steps may not match. Indeed our test includes cpu hotplugging, which should modify core_cpumask while printing. To fix this issue, cache the cpumask into a temporary variable before calling cpumap_print_{list, cpumask}_to_buf(), to keep it unchanged during the printing process.

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
0.0
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 24 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: topology: Keep the cpumask unchanged when printing cpumap During fuzz testing, the following warning was discovered: different return values (15 and 11) from vsnprintf("%*pbl ", ...) test:keyward is WARNING in kvasprintf WARNING: CPU: 55 PID: 1168477 at lib/kasprintf.c:30 kvasprintf+0x121/0x130 Call Trace: kvasprintf+0x121/0x130 kasprintf+0xa6/0xe0 bitmap_print_to_buf+0x89/0x100 core_siblings_list_read+0x7e/0xb0 kernfs_file_read_iter+0x15b/0x270 new_sync_read+0x153/0x260 vfs_read+0x215/0x290 ksys_read+0xb9/0x160 do_syscall_64+0x56/0x100 entry_SYSCALL_64_after_hwframe+0x78/0xe2 The call trace shows that kvasprintf() reported this warning during the printing of core_siblings_list. kvasprintf() has several steps: (1) First, calculate the length of the resulting formatted string. (2) Allocate a buffer based on the returned length. (3) Then, perform the actual string formatting. (4) Check whether the lengths of the formatted strings returned in steps (1) and (2) are consistent. If the core_cpumask is modified between steps (1) and (3), the lengths obtained in these two steps may not match. Indeed our test includes cpu hotplugging, which should modify core_cpumask while printing. To fix this issue, cache the cpumask into a temporary variable before calling cpumap_print_{list, cpumask}_to_buf(), to keep it unchanged during the printing process.

What

In the Linux kernel, the following vulnerability has been resolved: topology: Keep the cpumask unchanged when printing cpumap During fuzz testing, the following warning was discovered: different return values (15 and 11) from vsnprintf("%*pbl ", ...) test:keyward is WARNING in kvasprintf WARNING: CPU: 55 PID: 1168477 at lib/kasprintf.c:30 kvasprintf+0x121/0x130 Call Trace: kvasprintf+0x121/0x130 kasprintf+0xa6/0xe0 bitmap_print_to_buf+0x89/0x100 core_siblings_list_read+0x7e/0xb0 kernfs_file_read_iter+0x15b/0x270 new_sync_read+0x153/0x260 vfs_read+0x215/0x290 ksys_read+0xb9/0x160 do_syscall_64+0x56/0x100 entry_SYSCALL_64_after_hwframe+0x78/0xe2 The call trace shows that kvasprintf() reported this warning during the printing of core_siblings_list. kvasprintf() has several steps: (1) First, calculate the length of the resulting formatted string. (2) Allocate a buffer based on the returned length. (3) Then, perform the actual string formatting. (4) Check whether the lengths of the formatted strings returned in steps (1) and (2) are consistent. If the core_cpumask is modified between steps (1) and (3), the lengths obtained in these two steps may not match. Indeed our test includes cpu hotplugging, which should modify core_cpumask while printing. To fix this issue, cache the cpumask into a temporary variable before calling cpumap_print_{list, cpumask}_to_buf(), to keep it unchanged during the printing process.

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: topology: Keep the cpumask unchanged when printing cpumap During fuzz testing, the following warning was discovered: different return values (15 and 11) from vsnprintf("%*pbl ", ...) test:keyward is WARNING in kvasprintf WARNING: CPU: 55 PID: 1168477 at lib/kasprintf.c:30 kvasprintf+0x121/0x130 Call Trace: kvasprintf+0x121/0x130 kasprintf+0xa6/0xe0 bitmap_print_to_buf+0x89/0x100 core_siblings_list_read+0x7e/0xb0 kernfs_file_read_iter+0x15b/0x270 new_sync_read+0x153/0x260 vfs_read+0x215/0x290 ksys_read+0xb9/0x160 do_syscall_64+0x56/0x100 entry_SYSCALL_64_after_hwframe+0x78/0xe2 The call trace shows that kvasprintf() reported this warning during the printing of core_siblings_list. kvasprintf() has several steps: (1) First, calculate the length of the resulting formatted string. (2) Allocate a buffer based on the returned length. (3) Then, perform the actual string formatting. (4) Check whether the lengths of the formatted strings returned in steps (1) and (2) are consistent. If the core_cpumask is modified between steps (1) and (3), the lengths obtained in these two steps may not match. Indeed our test includes cpu hotplugging, which should modify core_cpumask while printing. To fix this issue, cache the cpumask into a temporary variable before calling cpumap_print_{list, cpumask}_to_buf(), to keep it unchanged during the printing process.

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.

ENISA EUVD · EUVD-2024-53820Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: topology: Keep the cpumask unchanged when printing cpumap During fuzz testing, the following warning was discovered: different return values (15 and 11) from vsnprintf("%*pbl ", ...) test:keyward is WARNING in kvasprintf WARNING: CPU: 55 PID: 1168477 at lib/kasprintf.c:30 kvasprintf+0x121/0x130 Call Trace: kvasprintf+0x121/0x130 kasprintf+0xa6/0xe0 bitmap_print_to_buf+0x89/0x100 core_siblings_list_read+0x7e/0xb0 kernfs_file_read_iter+0x15b/0x270 new_sync_read+0x153/0x260 vfs_read+0x215/0x290 ksys_read+0xb9/0x160 do_syscall_64+0x56/0x100 entry_SYSCALL_64_after_hwframe+0x78/0xe2 The call trace shows that kvasprintf() reported this warning during the printing of core_siblings_list. kvasprintf() has several steps: (1) First, calculate the length of the resulting formatted string. (2) Allocate a buffer based on the returned length. (3) Then, perform the actual string formatting. (4) Check whether the lengths of the formatted strings returned in steps (1) and (2) are consistent. If the core_cpumask is modified between steps (1) and (3), the lengths obtained in these two steps may not match. Indeed our test includes cpu hotplugging, which should modify core_cpumask while printing. To fix this issue, cache the cpumask into a temporary variable before calling cpumap_print_{list, cpumask}_to_buf(), to keep it unchanged during the printing process.

Official EUVD record ↗
BSI · German · WID-SEC-2025-0119Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Auswirkungen zu verursachen.

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

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jan 2025, published on 22 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-0880Multiples vulnérabilités dans les produits Siemens

ivilèges Systèmes affectés Desigo CC toutes versions Desigo CC toutes versions pour la vulnérabilité CVE-2025-15467 Desigo CC versions antérieures à 9.0.1 SIMATIC S7-1500 versions supérieures ou égales à 3.1.6 pour les vulnérabilités CVE-2021-41617, CVE-2023-28531, CVE-2023-51384, CVE-2023-52927, CVE-2024-26783, CVE-2024-27056, CVE-2024-28956, CVE-2024-36903, CVE-2024-36927, CVE-2024-42079, CVE-2024-46786, CVE-2024-47736, CVE-2024-47809, CVE-2024-49968, CVE-2024-49994, CVE-2024-49998, CVE-2024-50014, CVE-2024-50063, CVE-2024-50164, CVE-2024-50298, CVE-2024-53124, CVE-2024-53170, CVE-2024-54458, CVE-2024-56631, CVE-2024-56703, CVE-2024-56719, CVE-2024-57917, CVE-2024-57924, CVE-2024-57973, CVE-2024-57977, CVE-2024-57979, CVE-2024-58011, CVE-2024-58016, CVE-2024-58020, CVE-2024-58056, CVE-2024-58058, CVE-2024-58061, CVE-2024-58086, CVE-2025-21645, CVE-2025-21648, CVE-2025-21655, CVE-2025-21676, CVE-2025-21682, CVE-2025-21702, CVE-2025-21705, CVE-2025-21706, CVE-2025-21707, CVE-2025-21718, CVE-2025-21731, CVE-2025-21745, CVE-2025-21758, CVE-2025-21760, CVE-2025-21764, CVE-2025-21765, CVE-2025-21780, CVE-2025-21795, CVE-2025-21796, CVE-2025-21802, CVE-2025-21814, CVE-2025-21846, CVE-2025-21853, CVE-2025-21861, CVE-2025-21864, CVE-2025-21867, CVE-2025-21875, CVE-2025-21887, CVE-2025-21913, CVE-2025

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

d?id=CVE-2024-56783 Référence CVE CVE-2024-57793 https://www.cve.org/CVERecord?id=CVE-2024-57793 Référence CVE CVE-2024-57804 https://www.cve.org/CVERecord?id=CVE-2024-57804 Référence CVE CVE-2024-57852 https://www.cve.org/CVERecord?id=CVE-2024-57852 Référence CVE CVE-2024-57878 https://www.cve.org/CVERecord?id=CVE-2024-57878 Référence CVE CVE-2024-57879 https://www.cve.org/CVERecord?id=CVE-2024-57879 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57885 https://www.cve.org/CVERecord?id=CVE-2024-57885 Référence CVE CVE-2024-57914 https://www.cve.org/CVERecord?id=CVE-2024-57914 Référence CVE CVE-2024-57917 https://www.cve.org/CVERecord?id=CVE-2024-57917 Référence CVE CVE-2024-57932 https://www.cve.org/CVERecord?id=CVE-2024-57932 Référence CVE CVE-2024-57933 https://www.cve.org/CVERecord?id=CVE-2024-57933 Référence CVE CVE-2024-57936 https://www.cve.org/CVERecord?id=CVE-2024-57936 Référence CVE CVE-2024-57952 https://www.cve.org/CVERecord?id=CVE-2024-57952 Référence CVE CVE-2024-57985 https://www.cve.org/CVERecord?id=CVE-2024-57985 Référence CVE CVE-2024-57987 https://www.cve.org/CVERecord?id=CVE-2024-57987 Référence CVE CVE-2024-57988 https://www.cve.org/CVERecord?id=CVE-2024-57988 Référence CVE CVE-2024-57989 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=CVE-2024-57907 Référence CVE CVE-2024-57908 https://www.cve.org/CVERecord?id=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 https://www.cve.org/CVERecord?id=CVE-2024-57912 Référence CVE CVE-2024-57913 https://www.cve.org/CVERecord?id=CVE-2024-57913 Référence CVE CVE-2024-57917 https://www.cve.org/CVERecord?id=CVE-2024-57917 Référence CVE CVE-2024-57922 https://www.cve.org/CVERecord?id=CVE-2024-57922 Référence CVE CVE-2024-57925 https://www.cve.org/CVERecord?id=CVE-2024-57925 Référence CVE CVE-2024-57929 https://www.cve.org/CVERecord?id=CVE-2024-57929 Référence CVE CVE-2024-57931 https://www.cve.org/CVERecord?id=CVE-2024-57931 Référence CVE CVE-2024-57938 https://www.cve.org/CVERecord?id=CVE-2024-57938 Référence CVE CVE-2024-57939 https://www.cve.org/CVERecord?id=CVE-2024-57939 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=CVE-2024-57940 Référence CVE CVE-2024-57946 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=CVE-2024-57907 Référence CVE CVE-2024-57908 https://www.cve.org/CVERecord?id=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 https://www.cve.org/CVERecord?id=CVE-2024-57912 Référence CVE CVE-2024-57913 https://www.cve.org/CVERecord?id=CVE-2024-57913 Référence CVE CVE-2024-57917 https://www.cve.org/CVERecord?id=CVE-2024-57917 Référence CVE CVE-2024-57922 https://www.cve.org/CVERecord?id=CVE-2024-57922 Référence CVE CVE-2024-57925 https://www.cve.org/CVERecord?id=CVE-2024-57925 Référence CVE CVE-2024-57929 https://www.cve.org/CVERecord?id=CVE-2024-57929 Référence CVE CVE-2024-57931 https://www.cve.org/CVERecord?id=CVE-2024-57931 Référence CVE CVE-2024-57938 https://www.cve.org/CVERecord?id=CVE-2024-57938 Référence CVE CVE-2024-57939 https://www.cve.org/CVERecord?id=CVE-2024-57939 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=CVE-2024-57940 Référence CVE CVE-2024-57946 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=CVE-2024-57907 Référence CVE CVE-2024-57908 https://www.cve.org/CVERecord?id=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 https://www.cve.org/CVERecord?id=CVE-2024-57912 Référence CVE CVE-2024-57913 https://www.cve.org/CVERecord?id=CVE-2024-57913 Référence CVE CVE-2024-57917 https://www.cve.org/CVERecord?id=CVE-2024-57917 Référence CVE CVE-2024-57922 https://www.cve.org/CVERecord?id=CVE-2024-57922 Référence CVE CVE-2024-57925 https://www.cve.org/CVERecord?id=CVE-2024-57925 Référence CVE CVE-2024-57929 https://www.cve.org/CVERecord?id=CVE-2024-57929 Référence CVE CVE-2024-57931 https://www.cve.org/CVERecord?id=CVE-2024-57931 Référence CVE CVE-2024-57938 https://www.cve.org/CVERecord?id=CVE-2024-57938 Référence CVE CVE-2024-57939 https://www.cve.org/CVERecord?id=CVE-2024-57939 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=CVE-2024-57940 Référence CVE CVE-2024-57946 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=CVE-2024-57907 Référence CVE CVE-2024-57908 https://www.cve.org/CVERecord?id=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 https://www.cve.org/CVERecord?id=CVE-2024-57912 Référence CVE CVE-2024-57913 https://www.cve.org/CVERecord?id=CVE-2024-57913 Référence CVE CVE-2024-57917 https://www.cve.org/CVERecord?id=CVE-2024-57917 Référence CVE CVE-2024-57922 https://www.cve.org/CVERecord?id=CVE-2024-57922 Référence CVE CVE-2024-57925 https://www.cve.org/CVERecord?id=CVE-2024-57925 Référence CVE CVE-2024-57929 https://www.cve.org/CVERecord?id=CVE-2024-57929 Référence CVE CVE-2024-57931 https://www.cve.org/CVERecord?id=CVE-2024-57931 Référence CVE CVE-2024-57938 https://www.cve.org/CVERecord?id=CVE-2024-57938 Référence CVE CVE-2024-57939 https://www.cve.org/CVERecord?id=CVE-2024-57939 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=CVE-2024-57940 Référence CVE CVE-2024-57946 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-57905 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=CVE-2024-57907 Référence CVE CVE-2024-57908 https://www.cve.org/CVERecord?id=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 https://www.cve.org/CVERecord?id=CVE-2024-57912 Référence CVE CVE-2024-57913 https://www.cve.org/CVERecord?id=CVE-2024-57913 Référence CVE CVE-2024-57916 https://www.cve.org/CVERecord?id=CVE-2024-57916 Référence CVE CVE-2024-57917 https://www.cve.org/CVERecord?id=CVE-2024-57917 Référence CVE CVE-2024-57918 https://www.cve.org/CVERecord?id=CVE-2024-57918 Référence CVE CVE-2024-57919 https://www.cve.org/CVERecord?id=CVE-2024-57919 Référence CVE CVE-2024-57921 https://www.cve.org/CVERecord?id=CVE-2024-57921 Référence CVE CVE-2024-57924 https://www.cve.org/CVERecord?id=CVE-2024-57924 Référence CVE CVE-2024-57925 https://www.cve.org/CVERecord?id=CVE-2024-57925 Référence CVE CVE-2024-57926 https://www.cve.org/CVERecord?id=CVE-2024-57926 Référence CVE CVE-2024-57929 https://www.cve.org/CVERecord?id=CVE-2024-57929 Référence CVE CVE-2024-57931 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=CVE-2024-57907 Référence CVE CVE-2024-57908 https://www.cve.org/CVERecord?id=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 https://www.cve.org/CVERecord?id=CVE-2024-57912 Référence CVE CVE-2024-57913 https://www.cve.org/CVERecord?id=CVE-2024-57913 Référence CVE CVE-2024-57916 https://www.cve.org/CVERecord?id=CVE-2024-57916 Référence CVE CVE-2024-57917 https://www.cve.org/CVERecord?id=CVE-2024-57917 Référence CVE CVE-2024-57922 https://www.cve.org/CVERecord?id=CVE-2024-57922 Référence CVE CVE-2024-57925 https://www.cve.org/CVERecord?id=CVE-2024-57925 Référence CVE CVE-2024-57929 https://www.cve.org/CVERecord?id=CVE-2024-57929 Référence CVE CVE-2024-57930 https://www.cve.org/CVERecord?id=CVE-2024-57930 Référence CVE CVE-2024-57931 https://www.cve.org/CVERecord?id=CVE-2024-57931 Référence CVE CVE-2024-57938 https://www.cve.org/CVERecord?id=CVE-2024-57938 Référence CVE CVE-2024-57939 https://www.cve.org/CVERecord?id=CVE-2024-57939 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=CVE-2024-57907 Référence CVE CVE-2024-57908 https://www.cve.org/CVERecord?id=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 https://www.cve.org/CVERecord?id=CVE-2024-57912 Référence CVE CVE-2024-57913 https://www.cve.org/CVERecord?id=CVE-2024-57913 Référence CVE CVE-2024-57915 https://www.cve.org/CVERecord?id=CVE-2024-57915 Référence CVE CVE-2024-57916 https://www.cve.org/CVERecord?id=CVE-2024-57916 Référence CVE CVE-2024-57917 https://www.cve.org/CVERecord?id=CVE-2024-57917 Référence CVE CVE-2024-57922 https://www.cve.org/CVERecord?id=CVE-2024-57922 Référence CVE CVE-2024-57926 https://www.cve.org/CVERecord?id=CVE-2024-57926 Référence CVE CVE-2024-57929 https://www.cve.org/CVERecord?id=CVE-2024-57929 Référence CVE CVE-2024-57931 https://www.cve.org/CVERecord?id=CVE-2024-57931 Référence CVE CVE-2024-57932 https://www.cve.org/CVERecord?id=CVE-2024-57932 Référence CVE CVE-2024-57933 https://www.cve.org/CVERecord?id=CVE-2024-57933 Référence CVE CVE-2024-57935 https://www.cve.org/CVERecord?id=CVE-2024-57935 Référence CVE CVE-2024-57936 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=CVE-2024-57907 Référence CVE CVE-2024-57908 https://www.cve.org/CVERecord?id=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 https://www.cve.org/CVERecord?id=CVE-2024-57912 Référence CVE CVE-2024-57913 https://www.cve.org/CVERecord?id=CVE-2024-57913 Référence CVE CVE-2024-57915 https://www.cve.org/CVERecord?id=CVE-2024-57915 Référence CVE CVE-2024-57916 https://www.cve.org/CVERecord?id=CVE-2024-57916 Référence CVE CVE-2024-57917 https://www.cve.org/CVERecord?id=CVE-2024-57917 Référence CVE CVE-2024-57922 https://www.cve.org/CVERecord?id=CVE-2024-57922 Référence CVE CVE-2024-57925 https://www.cve.org/CVERecord?id=CVE-2024-57925 Référence CVE CVE-2024-57929 https://www.cve.org/CVERecord?id=CVE-2024-57929 Référence CVE CVE-2024-57939 https://www.cve.org/CVERecord?id=CVE-2024-57939 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=CVE-2024-57940 Référence CVE CVE-2024-57948 https://www.cve.org/CVERecord?id=CVE-2024-57948 Référence CVE CVE-2025-21631 https://www.cve.org/CVERecord?id=CVE-2025-21631 Référence CVE CVE-2025-21636 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=CVE-2024-57907 Référence CVE CVE-2024-57908 https://www.cve.org/CVERecord?id=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 https://www.cve.org/CVERecord?id=CVE-2024-57912 Référence CVE CVE-2024-57913 https://www.cve.org/CVERecord?id=CVE-2024-57913 Référence CVE CVE-2024-57915 https://www.cve.org/CVERecord?id=CVE-2024-57915 Référence CVE CVE-2024-57916 https://www.cve.org/CVERecord?id=CVE-2024-57916 Référence CVE CVE-2024-57917 https://www.cve.org/CVERecord?id=CVE-2024-57917 Référence CVE CVE-2024-57922 https://www.cve.org/CVERecord?id=CVE-2024-57922 Référence CVE CVE-2024-57926 https://www.cve.org/CVERecord?id=CVE-2024-57926 Référence CVE CVE-2024-57929 https://www.cve.org/CVERecord?id=CVE-2024-57929 Référence CVE CVE-2024-57931 https://www.cve.org/CVERecord?id=CVE-2024-57931 Référence CVE CVE-2024-57932 https://www.cve.org/CVERecord?id=CVE-2024-57932 Référence CVE CVE-2024-57933 https://www.cve.org/CVERecord?id=CVE-2024-57933 Référence CVE CVE-2024-57935 https://www.cve.org/CVERecord?id=CVE-2024-57935 Référence CVE CVE-2024-57936 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-029098Linux の 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.15, 5.15.177 ≤ 5.15.*, 6.1.125 ≤ 6.1.*, 6.6.72 ≤ 6.6.*, 6.12.10 ≤ 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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jan 2025 · Last source change 8 Sept 2026, 08:39 UTC · CWE not yet assigned

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-53820
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
    bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 < 1c7818e2746e747838a3de1687e89eac7b947f08; bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 < ca47e933a900492d89dcf5db18a99c28bd4a742d; bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 < b02cf1d27e460ab2b3e1c8c9ce472d562cad2e8d; bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 < 360596e7fe319a5db1b5fb34a3952862ae53c924; bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 < cbd399f78e23ad4492c174fc5e6b3676dba74a52; 5.15 · Fixed: < 5.15; 5.15.177 ≤ 5.15.*; 6.1.125 ≤ 6.1.*; 6.6.72 ≤ 6.6.*; 6.12.10 ≤ 6.12.*; 6.13 ≤ *
    After
    Linux: bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 < 1c7818e2746e747838a3de1687e89eac7b947f08, bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 < ca47e933a900492d89dcf5db18a99c28bd4a742d, bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 < b02cf1d27e460ab2b3e1c8c9ce472d562cad2e8d, bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 < 360596e7fe319a5db1b5fb34a3952862ae53c924, bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 < cbd399f78e23ad4492c174fc5e6b3676dba74a52, 5.15 · Fixed: Linux: < 5.15, 5.15.177 ≤ 5.15.*, 6.1.125 ≤ 6.1.*, 6.6.72 ≤ 6.6.*, 6.12.10 ≤ 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-53820↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-57917 · cve.blacktree.nl