Linux Kernel: security vulnerability (CVE-2024-26869)
Published Last modified Sources: BSI, EUVD, CVE.org
What is affected, what to do
Update Linux Kernel to version 6.1.191, Linux Kernel to version 6.6.23, Linux Kernel to version 6.7.11.
- Affected
- Linux Kernel
lt 4.19..6.1.191 - Linux Kernel
lt 6.2..6.6.23 - Linux Kernel
lt 6.7..6.7.11 - Linux Kernel
lt 6.8..6.8.2
- Linux Kernel
- Fixed in
- Linux Kernel
6.1.191 - Linux Kernel
6.6.23 - Linux Kernel
6.7.11 - Linux Kernel
6.8.2 - Linux Kernel
6.9
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.8
XIEM Effective CVSS
Highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
7.8
CVSS v3
Severity High on the scale from 0 to 10.
Source: BSI, EUVD, CVE.org
0.2 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 7.8
Show all metrics
- Severity
- High
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- 44.34 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- 7.8 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- 7.8
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- 7.8
- Low — this CVE sits in the lower 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: total
- Source: CISA Vulnrichment, as of 12 June 2024
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- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
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:
f2fs: fix to truncate meta inode pages forcely
Below race case can cause data corruption:
Thread A GC thread - gc_data_segment - ra_data_block - locked meta_inode page
- f2fs_inplace_write_data
- invalidate_mapping_pages : fail to invalidate meta_inode page due to lock failure or dirty|writeback status
- f2fs_submit_page_bio : write last dirty data to old blkaddr - move_data_block - load old data from meta_inode page - f2fs_submit_page_write : write old data to new blkaddr
Because invalidate_mapping_pages() will skip invalidating page which has unclear status including locked, dirty, writeback and so on, so we need to use truncate_inode_pages_range() instead of invalidate_mapping_pages() to make sure meta_inode page will be dropped.
Source: BSI CSAF, BSI WID Portal, ENISA EUVD, cvelistv5, NVD (NIST)
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 |
|
|
Vendors and products
Affected operating systems
| Linux | linux | linux_kernel | — |
References & sources
- git.kernel.orgstable/c/c92f2927df860a60ba815d3ee610a944b92a8694euvd, Patch
- git.kernel.orgstable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189euvd, Patch
- git.kernel.orgstable/c/04226d8e3c4028dc451e9d8777356ec0f7919253euvd, Patch
- git.kernel.orgstable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65euvd, Patch
- git.kernel.orgstable/c/0721a4f85d12a364002a9476c84b930fbc993f83euvd
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/04226d8e3c4028dc451e9d8777356ec0f7919253
- https://git.kernel.org/stable/c/0721a4f85d12a364002a9476c84b930fbc993f83
- https://git.kernel.org/stable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189
- https://git.kernel.org/stable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65
and 1 more reference
Show 14 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2024/26xxx/CVE-2024-26869.json">CVE-2024-26869</a>Reference added —https://git.kernel.org/stable/c/04226d8e3c4028dc451e9d8777356ec0f7919253Reference added —https://git.kernel.org/stable/c/0721a4f85d12a364002a9476c84b930fbc993f83Reference added —https://git.kernel.org/stable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189Reference added —https://git.kernel.org/stable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65Reference added —https://git.kernel.org/stable/c/c92f2927df860a60ba815d3ee610a944b92a8694Reference removed https://git.kernel.org/stable/c/04226d8e3c4028dc451e9d8777356ec0f7919253—Reference removed https://git.kernel.org/stable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189—Reference removed https://git.kernel.org/stable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65—Reference removed https://git.kernel.org/stable/c/c92f2927df860a60ba815d3ee610a944b92a8694—Reference type removed https://git.kernel.org/stable/c/04226d8e3c4028dc451e9d8777356ec0f7919253 Types: Patch—Reference type removed https://git.kernel.org/stable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189 Types: Patch—Reference type removed https://git.kernel.org/stable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65 Types: Patch—Reference type removed https://git.kernel.org/stable/c/c92f2927df860a60ba815d3ee610a944b92a8694 Types: Patch—Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedCVE Program
New references:Show 12 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://git.kernel.org/stable/c/04226d8e3c4028dc451e9d8777356ec0f7919253Reference added —https://git.kernel.org/stable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189Reference added —https://git.kernel.org/stable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65Reference added —https://git.kernel.org/stable/c/c92f2927df860a60ba815d3ee610a944b92a8694Reference removed https://git.kernel.org/stable/c/04226d8e3c4028dc451e9d8777356ec0f7919253—Reference removed https://git.kernel.org/stable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189—Reference removed https://git.kernel.org/stable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65—Reference removed https://git.kernel.org/stable/c/c92f2927df860a60ba815d3ee610a944b92a8694—Reference type removed https://git.kernel.org/stable/c/04226d8e3c4028dc451e9d8777356ec0f7919253 Types: Patch—Reference type removed https://git.kernel.org/stable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189 Types: Patch—Reference type removed https://git.kernel.org/stable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65 Types: Patch—Reference type removed https://git.kernel.org/stable/c/c92f2927df860a60ba815d3ee610a944b92a8694 Types: Patch—Source identifier: af854a3a-2127-422b-91ae-364da2661108
Record modifiedLinux
CVSS V3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Show the original change
Individual changes of this event as published by NVD Type Action Before After CVSS added —AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
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-26869"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-26869.svg?lang=en" alt="CVE-2024-26869 – NEOSEC Intel" height="20"></a>