Linux Kernel: security vulnerability (CVE-2024-56657)
Published Last modified Sources: Debian LTS, BSI, Siemens ProductCERT, Ubuntu, CVE.org, Msrc Update Guide, EUVD
What is affected, what to do
In the Linux kernel, the following vulnerability has been resolved: ALSA: control: Avoid WARN() for symlink errors Using WARN() for showing the error of symlink creations don't give more information than telling that something goes wrong, since the usual code path is a lregister callback from each control element creation. More badly, the use of WARN() rather confuses fuzzer as if it were serious issues.
Update Linux Kernel to version 5.15.209, Linux Kernel to version 6.1.175, Linux Kernel to version 6.6.67.
- Affected
- Linux Kernel
lt 5.13..5.15.209 - Linux Kernel
lt 5.16..6.1.175 - Linux Kernel
lt 6.2..6.6.67 - Linux Kernel
lt 6.7..6.12.6
- Linux Kernel
- Fixed in
- Linux Kernel
5.15.209 - Linux Kernel
6.1.175 - Linux Kernel
6.6.67 - Linux Kernel
6.12.6 - Linux Kernel
6.13
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
5.5
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
5.5
CVSS v3
Severity Medium on the scale from 0 to 10.
Source: Debian LTS, BSI, Siemens ProductCERT, Ubuntu, CVE.org, Msrc Update Guide, EUVD
0.2 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 12.7
Show all metrics
- Severity
- Medium
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 36.10 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 5.5 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 5.5
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.2 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 12.7
- Elevated — this CVE ranks above at least 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 1 October 2025
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
In the Linux kernel, the following vulnerability has been resolved: ALSA: control: Avoid WARN() for symlink errors Using WARN() for showing the error of symlink creations don't give more information than telling that something goes wrong, since the usual code path is a lregister callback from each control element creation. More badly, the use of WARN() rather confuses fuzzer as if it were serious issues. This patch downgrades the warning messages to use the normal dev_err() instead of WARN(). For making it clearer, add the function name to the prefix, too.
Source: Debian LTS Advisories, BSI WID Portal, BSI CSAF, siemens_advisory, Ubuntu Security Notices, cvelistv5, NVD (NIST), Microsoft Security Update Guide, CVE.org (MITRE), ENISA EUVD
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
| Siemens | SIMATIC S7 |
|
|
Vendors and products
Affected operating systems
| Linux | debian | linux | bookworm |
| Linux | debian | linux-6.1 | bullseye |
| Linux | linux | linux_kernel | 6.13 |
| Linux | linux | linux_kernel | — |
References & sources
- git.kernel.orgstable/c/4e5a92a7223c83c1f5f2db6cd010ac9347948972
- git.kernel.orgstable/c/365ee29e559269cbb2108c4cc05dd8e262b4e84e
- git.kernel.orgstable/c/d5a1ca7b59804d6779644001a878ed925a4688ca
- git.kernel.orgstable/c/36c0764474b637bbee498806485bed524cad486b
- git.kernel.orgstable/c/b2e538a9827dd04ab5273bf4be8eb2edb84357b0
- Siemens ProductCERTproductcert/html/ssa-784472.html
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedLinux
New references:- https://git.kernel.org/stable/c/365ee29e559269cbb2108c4cc05dd8e262b4e84e
- https://git.kernel.org/stable/c/36c0764474b637bbee498806485bed524cad486b
- https://git.kernel.org/stable/c/4e5a92a7223c83c1f5f2db6cd010ac9347948972
- https://git.kernel.org/stable/c/b2e538a9827dd04ab5273bf4be8eb2edb84357b0
and 1 more reference
Show 13 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://git.kernel.org/stable/c/365ee29e559269cbb2108c4cc05dd8e262b4e84eReference added —https://git.kernel.org/stable/c/36c0764474b637bbee498806485bed524cad486bReference added —https://git.kernel.org/stable/c/4e5a92a7223c83c1f5f2db6cd010ac9347948972Reference added —https://git.kernel.org/stable/c/b2e538a9827dd04ab5273bf4be8eb2edb84357b0Reference added —https://git.kernel.org/stable/c/d5a1ca7b59804d6779644001a878ed925a4688caReference removed https://git.kernel.org/stable/c/365ee29e559269cbb2108c4cc05dd8e262b4e84e—Reference removed https://git.kernel.org/stable/c/36c0764474b637bbee498806485bed524cad486b—Reference removed https://git.kernel.org/stable/c/4e5a92a7223c83c1f5f2db6cd010ac9347948972—Reference removed https://git.kernel.org/stable/c/b2e538a9827dd04ab5273bf4be8eb2edb84357b0—Reference removed https://git.kernel.org/stable/c/d5a1ca7b59804d6779644001a878ed925a4688ca—Reference type removed https://git.kernel.org/stable/c/36c0764474b637bbee498806485bed524cad486b Types: Patch—Reference type removed https://git.kernel.org/stable/c/b2e538a9827dd04ab5273bf4be8eb2edb84357b0 Types: Patch—Reference type removed https://git.kernel.org/stable/c/d5a1ca7b59804d6779644001a878ed925a4688ca Types: Patch—Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedSiemens ADP
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2024/56xxx/CVE-2024-56657.json">CVE-2024-56657</a>Reference added —https://cert-portal.siemens.com/productcert/html/ssa-784472.htmlSource identifier: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2024-56657"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-56657.svg?lang=en" alt="CVE-2024-56657 – NEOSEC Intel" height="20"></a>