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

s390/dasd: fix error recovery leading to data corruption on ESE devices

Linux · Linux

7.0HighCVSS 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 15 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 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.24% 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 15 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.

19 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 15 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.112-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
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-45026 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: s390/dasd: fix error recovery leading to data corruption on ESE devices
106 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 9
  • kernel as a component of Red Hat Enterprise Linux 9
  • kernel-64k as a component of Red Hat Enterprise Linux 9
  • kernel-64k-core as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules-internal as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in the kernel. The `s390/dasd` component, responsible for handling Extent Space Efficient (ESE) devices, contains an error in its recovery process. An imprecise check for data length during on-demand formatting of ESE volumes can lead to incorrect error handling. This vulnerability can result in data corruption, especially during events such as a storage server warmstart.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
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-41506

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 15 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: s390/dasd: fix error recovery leading to data corruption on ESE devices Extent Space Efficient (ESE) or thin provisioned volumes need to be formatted on demand during usual IO processing. The dasd_ese_needs_format function checks for error codes that signal the non existence of a proper track format. The check for incorrect length is to imprecise since other error cases leading to transport of insufficient data also have this flag set. This might lead to data corruption in certain error cases for example during a storage server warmstart. Fix by removing the check for incorrect length and replacing by explicitly checking for invalid track format in transport mode. Also remove the check for file protected since this is not a valid ESE handling case.

What

In the Linux kernel, the following vulnerability has been resolved: s390/dasd: fix error recovery leading to data corruption on ESE devices Extent Space Efficient (ESE) or thin provisioned volumes need to be formatted on demand during usual IO processing. The dasd_ese_needs_format function checks for error codes that signal the non existence of a proper track format. The check for incorrect length is to imprecise since other error cases leading to transport of insufficient data also have this flag set. This might lead to data corruption in certain error cases for example during a storage server warmstart. Fix by removing the check for incorrect length and replacing by explicitly checking for invalid track format in transport mode. Also remove the check for file protected since this is not a valid ESE handling case.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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: s390/dasd: fix error recovery leading to data corruption on ESE devices Extent Space Efficient (ESE) or thin provisioned volumes need to be formatted on demand during usual IO processing. The dasd_ese_needs_format function checks for error codes that signal the non existence of a proper track format. The check for incorrect length is to imprecise since other error cases leading to transport of insufficient data also have this flag set. This might lead to data corruption in certain error cases for example during a storage server warmstart. Fix by removing the check for incorrect length and replacing by explicitly checking for invalid track format in transport mode. Also remove the check for file protected since this is not a valid ESE handling case.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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 → Out-of-bounds Write → 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
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-787 ↗

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

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:H/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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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.
CWE-787
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-2124Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen unspezifischen Angriff durchzuführen.

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

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

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

d?id=CVE-2024-45013 Référence CVE CVE-2024-45015 https://www.cve.org/CVERecord?id=CVE-2024-45015 Référence CVE CVE-2024-45017 https://www.cve.org/CVERecord?id=CVE-2024-45017 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45019 https://www.cve.org/CVERecord?id=CVE-2024-45019 Référence CVE CVE-2024-45020 https://www.cve.org/CVERecord?id=CVE-2024-45020 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=CVE-2024-45021 Référence CVE CVE-2024-45022 https://www.cve.org/CVERecord?id=CVE-2024-45022 Référence CVE CVE-2024-45025 https://www.cve.org/CVERecord?id=CVE-2024-45025 Référence CVE CVE-2024-45026 https://www.cve.org/CVERecord?id=CVE-2024-45026 Référence CVE CVE-2024-45027 https://www.cve.org/CVERecord?id=CVE-2024-45027 Référence CVE CVE-2024-45028 https://www.cve.org/CVERecord?id=CVE-2024-45028 Référence CVE CVE-2024-45029 https://www.cve.org/CVERecord?id=CVE-2024-45029 Référence CVE CVE-2024-45030 https://www.cve.org/CVERecord?id=CVE-2024-45030 Référence CVE CVE-2024-46672 https://www.cve.org/CVERecord?id=CVE-2024-46672 Référence CVE CVE-2024-46673 https://www.cve.org/CVERecord?id=CVE-2024-46673 Référence CVE CVE-2024-46675 https://www.cve.org/CVERecord?id=CVE-2024-46675 Référence CVE CVE-2024-46676 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-45009 Référence CVE CVE-2024-45010 https://www.cve.org/CVERecord?id=CVE-2024-45010 Référence CVE CVE-2024-45011 https://www.cve.org/CVERecord?id=CVE-2024-45011 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45019 https://www.cve.org/CVERecord?id=CVE-2024-45019 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=CVE-2024-45021 Référence CVE CVE-2024-45022 https://www.cve.org/CVERecord?id=CVE-2024-45022 Référence CVE CVE-2024-45025 https://www.cve.org/CVERecord?id=CVE-2024-45025 Référence CVE CVE-2024-45026 https://www.cve.org/CVERecord?id=CVE-2024-45026 Référence CVE CVE-2024-45028 https://www.cve.org/CVERecord?id=CVE-2024-45028 Référence CVE CVE-2024-45029 https://www.cve.org/CVERecord?id=CVE-2024-45029 Référence CVE CVE-2024-46673 https://www.cve.org/CVERecord?id=CVE-2024-46673 Référence CVE CVE-2024-46674 https://www.cve.org/CVERecord?id=CVE-2024-46674 Référence CVE CVE-2024-46675 https://www.cve.org/CVERecord?id=CVE-2024-46675 Référence CVE CVE-2024-46676 https://www.cve.org/CVERecord?id=CVE-2024-46676 Référence CVE CVE-2024-46677 https://www.cve.org/CVERecord?id=CVE-2024-46677 Référence CVE CVE-2024-46679 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-45015 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45017 https://www.cve.org/CVERecord?id=CVE-2024-45017 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45019 https://www.cve.org/CVERecord?id=CVE-2024-45019 Référence CVE CVE-2024-45020 https://www.cve.org/CVERecord?id=CVE-2024-45020 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=CVE-2024-45021 Référence CVE CVE-2024-45022 https://www.cve.org/CVERecord?id=CVE-2024-45022 Référence CVE CVE-2024-45025 https://www.cve.org/CVERecord?id=CVE-2024-45025 Référence CVE CVE-2024-45026 https://www.cve.org/CVERecord?id=CVE-2024-45026 Référence CVE CVE-2024-45027 https://www.cve.org/CVERecord?id=CVE-2024-45027 Référence CVE CVE-2024-45028 https://www.cve.org/CVERecord?id=CVE-2024-45028 Référence CVE CVE-2024-45029 https://www.cve.org/CVERecord?id=CVE-2024-45029 Référence CVE CVE-2024-45030 https://www.cve.org/CVERecord?id=CVE-2024-45030 Référence CVE CVE-2024-46672 https://www.cve.org/CVERecord?id=CVE-2024-46672 Référence CVE CVE-2024-46673 https://www.cve.org/CVERecord?id=CVE-2024-46673 Référence CVE CVE-2024-46675 https://www.cve.org/CVERecord?id=CVE-2024-46675 Référence CVE CVE-2024-46676 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-42145 Référence CVE CVE-2024-42253 https://www.cve.org/CVERecord?id=CVE-2024-42253 Référence CVE CVE-2024-43854 https://www.cve.org/CVERecord?id=CVE-2024-43854 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-44931 https://www.cve.org/CVERecord?id=CVE-2024-44931 Référence CVE CVE-2024-44947 https://www.cve.org/CVERecord?id=CVE-2024-44947 Référence CVE CVE-2024-44958 https://www.cve.org/CVERecord?id=CVE-2024-44958 Référence CVE CVE-2024-45013 https://www.cve.org/CVERecord?id=CVE-2024-45013 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45026 https://www.cve.org/CVERecord?id=CVE-2024-45026 Référence CVE CVE-2024-46716 https://www.cve.org/CVERecord?id=CVE-2024-46716 Référence CVE CVE-2024-46724 https://www.cve.org/CVERecord?id=CVE-2024-46724 Référence CVE CVE-2024-46755 https://www.cve.org/CVERecord?id=CVE-2024-46755 Référence CVE CVE-2024-46802 https://www.cve.org/CVERecord?id=CVE-2024-46802 Référence CVE CVE-2024-46809 https://www.cve.org/CVERecord?id=CVE-2024-46809 Référence CVE CVE-2024-46813 https://www.cve.org/CVERecord?id=CVE-2024-46813 Référence CVE CVE-2024-46814 https://www.cve.org/CVERecord?id=CVE-2024-46814 Référence CVE CVE-2024-46815 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2023-52881 Référence CVE CVE-2023-52919 https://www.cve.org/CVERecord?id=CVE-2023-52919 Référence CVE CVE-2023-6270 https://www.cve.org/CVERecord?id=CVE-2023-6270 Référence CVE CVE-2024-27043 https://www.cve.org/CVERecord?id=CVE-2024-27043 Référence CVE CVE-2024-36971 https://www.cve.org/CVERecord?id=CVE-2024-36971 Référence CVE CVE-2024-42145 https://www.cve.org/CVERecord?id=CVE-2024-42145 Référence CVE CVE-2024-44947 https://www.cve.org/CVERecord?id=CVE-2024-44947 Référence CVE CVE-2024-45013 https://www.cve.org/CVERecord?id=CVE-2024-45013 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45026 https://www.cve.org/CVERecord?id=CVE-2024-45026 Référence CVE CVE-2024-46716 https://www.cve.org/CVERecord?id=CVE-2024-46716 Référence CVE CVE-2024-46813 https://www.cve.org/CVERecord?id=CVE-2024-46813 Référence CVE CVE-2024-46814 https://www.cve.org/CVERecord?id=CVE-2024-46814 Référence CVE CVE-2024-46815 https://www.cve.org/CVERecord?id=CVE-2024-46815 Référence CVE CVE-2024-46816 https://www.cve.org/CVERecord?id=CVE-2024-46816 Référence CVE CVE-2024-46817 https://www.cve.org/CVERecord?id=CVE-2024-46817 Référence CVE CVE-2024-46818 https://www.cve.org/CVERecord?id=CVE-2024-46818 Référence CVE CVE-2024-46849 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-45006 Référence CVE CVE-2024-45007 https://www.cve.org/CVERecord?id=CVE-2024-45007 Référence CVE CVE-2024-45008 https://www.cve.org/CVERecord?id=CVE-2024-45008 Référence CVE CVE-2024-45009 https://www.cve.org/CVERecord?id=CVE-2024-45009 Référence CVE CVE-2024-45011 https://www.cve.org/CVERecord?id=CVE-2024-45011 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=CVE-2024-45021 Référence CVE CVE-2024-45025 https://www.cve.org/CVERecord?id=CVE-2024-45025 Référence CVE CVE-2024-45026 https://www.cve.org/CVERecord?id=CVE-2024-45026 Référence CVE CVE-2024-45028 https://www.cve.org/CVERecord?id=CVE-2024-45028 Référence CVE CVE-2024-46673 https://www.cve.org/CVERecord?id=CVE-2024-46673 Référence CVE CVE-2024-46675 https://www.cve.org/CVERecord?id=CVE-2024-46675 Référence CVE CVE-2024-46676 https://www.cve.org/CVERecord?id=CVE-2024-46676 Référence CVE CVE-2024-46677 https://www.cve.org/CVERecord?id=CVE-2024-46677 Référence CVE CVE-2024-46679 https://www.cve.org/CVERecord?id=CVE-2024-46679 Référence CVE CVE-2024-46685 https://www.cve.org/CVERecord?id=CVE-2024-46685 Référence CVE CVE-2024-46689 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-45006 Référence CVE CVE-2024-45007 https://www.cve.org/CVERecord?id=CVE-2024-45007 Référence CVE CVE-2024-45008 https://www.cve.org/CVERecord?id=CVE-2024-45008 Référence CVE CVE-2024-45009 https://www.cve.org/CVERecord?id=CVE-2024-45009 Référence CVE CVE-2024-45011 https://www.cve.org/CVERecord?id=CVE-2024-45011 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=CVE-2024-45021 Référence CVE CVE-2024-45025 https://www.cve.org/CVERecord?id=CVE-2024-45025 Référence CVE CVE-2024-45026 https://www.cve.org/CVERecord?id=CVE-2024-45026 Référence CVE CVE-2024-45028 https://www.cve.org/CVERecord?id=CVE-2024-45028 Référence CVE CVE-2024-46673 https://www.cve.org/CVERecord?id=CVE-2024-46673 Référence CVE CVE-2024-46675 https://www.cve.org/CVERecord?id=CVE-2024-46675 Référence CVE CVE-2024-46676 https://www.cve.org/CVERecord?id=CVE-2024-46676 Référence CVE CVE-2024-46677 https://www.cve.org/CVERecord?id=CVE-2024-46677 Référence CVE CVE-2024-46679 https://www.cve.org/CVERecord?id=CVE-2024-46679 Référence CVE CVE-2024-46685 https://www.cve.org/CVERecord?id=CVE-2024-46685 Référence CVE CVE-2024-46689 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-44998 Référence CVE CVE-2024-44999 https://www.cve.org/CVERecord?id=CVE-2024-44999 Référence CVE CVE-2024-45001 https://www.cve.org/CVERecord?id=CVE-2024-45001 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45006 https://www.cve.org/CVERecord?id=CVE-2024-45006 Référence CVE CVE-2024-45008 https://www.cve.org/CVERecord?id=CVE-2024-45008 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=CVE-2024-45021 Référence CVE CVE-2024-45025 https://www.cve.org/CVERecord?id=CVE-2024-45025 Référence CVE CVE-2024-45026 https://www.cve.org/CVERecord?id=CVE-2024-45026 Référence CVE CVE-2024-45028 https://www.cve.org/CVERecord?id=CVE-2024-45028 Référence CVE CVE-2024-46673 https://www.cve.org/CVERecord?id=CVE-2024-46673 Référence CVE CVE-2024-46675 https://www.cve.org/CVERecord?id=CVE-2024-46675 Référence CVE CVE-2024-46676 https://www.cve.org/CVERecord?id=CVE-2024-46676 Référence CVE CVE-2024-46677 https://www.cve.org/CVERecord?id=CVE-2024-46677 Référence CVE CVE-2024-46679 https://www.cve.org/CVERecord?id=CVE-2024-46679 Référence CVE CVE-2024-46685 https://www.cve.org/CVERecord?id=CVE-2024-46685 Référence CVE CVE-2024-46689 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-45013 Référence CVE CVE-2024-45015 https://www.cve.org/CVERecord?id=CVE-2024-45015 Référence CVE CVE-2024-45017 https://www.cve.org/CVERecord?id=CVE-2024-45017 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45019 https://www.cve.org/CVERecord?id=CVE-2024-45019 Référence CVE CVE-2024-45020 https://www.cve.org/CVERecord?id=CVE-2024-45020 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=CVE-2024-45021 Référence CVE CVE-2024-45022 https://www.cve.org/CVERecord?id=CVE-2024-45022 Référence CVE CVE-2024-45023 https://www.cve.org/CVERecord?id=CVE-2024-45023 Référence CVE CVE-2024-45026 https://www.cve.org/CVERecord?id=CVE-2024-45026 Référence CVE CVE-2024-45028 https://www.cve.org/CVERecord?id=CVE-2024-45028 Référence CVE CVE-2024-45029 https://www.cve.org/CVERecord?id=CVE-2024-45029 Référence CVE CVE-2024-45030 https://www.cve.org/CVERecord?id=CVE-2024-45030 Référence CVE CVE-2024-46672 https://www.cve.org/CVERecord?id=CVE-2024-46672 Référence CVE CVE-2024-46673 https://www.cve.org/CVERecord?id=CVE-2024-46673 Référence CVE CVE-2024-46674 https://www.cve.org/CVERecord?id=CVE-2024-46674 Référence CVE CVE-2024-46675 https://www.cve.org/CVERecord?id=CVE-2024-46675 Référence CVE CVE-2024-46676 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-45009 Référence CVE CVE-2024-45010 https://www.cve.org/CVERecord?id=CVE-2024-45010 Référence CVE CVE-2024-45011 https://www.cve.org/CVERecord?id=CVE-2024-45011 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45019 https://www.cve.org/CVERecord?id=CVE-2024-45019 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=CVE-2024-45021 Référence CVE CVE-2024-45022 https://www.cve.org/CVERecord?id=CVE-2024-45022 Référence CVE CVE-2024-45025 https://www.cve.org/CVERecord?id=CVE-2024-45025 Référence CVE CVE-2024-45026 https://www.cve.org/CVERecord?id=CVE-2024-45026 Référence CVE CVE-2024-45028 https://www.cve.org/CVERecord?id=CVE-2024-45028 Référence CVE CVE-2024-45029 https://www.cve.org/CVERecord?id=CVE-2024-45029 Référence CVE CVE-2024-46673 https://www.cve.org/CVERecord?id=CVE-2024-46673 Référence CVE CVE-2024-46674 https://www.cve.org/CVERecord?id=CVE-2024-46674 Référence CVE CVE-2024-46675 https://www.cve.org/CVERecord?id=CVE-2024-46675 Référence CVE CVE-2024-46676 https://www.cve.org/CVERecord?id=CVE-2024-46676 Référence CVE CVE-2024-46677 https://www.cve.org/CVERecord?id=CVE-2024-46677 Référence CVE CVE-2024-46679 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-008307Linux の 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
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 11 Sept 2024 · Last source change 5 Aug 2026, 11:37 UTC · CWE-787 · Out-of-bounds Write

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-41506
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-41506↗Vendor CSAF · Red Hat Product Security↗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-45026 · cve.blacktree.nl