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

scsi: ufs: core: Fix shift issue in ufshcd_clear_cmd()

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 11 May 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.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
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.7.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
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-24104

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 actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix shift issue in ufshcd_clear_cmd() When task_tag >= 32 (in MCQ mode) and sizeof(unsigned int) == 4, 1U << task_tag will out of bounds for a u32 mask. Fix this up to prevent SHIFT_ISSUE (bitwise shifts that are out of bounds for their data type). [name:debug_monitors&]Unexpected kernel BRK exception at EL1 [name:traps&]Internal error: BRK handler: 00000000f2005514 [#1] PREEMPT SMP [name:mediatek_cpufreq_hw&]cpufreq stop DVFS log done [name:mrdump&]Kernel Offset: 0x1ba5800000 from 0xffffffc008000000 [name:mrdump&]PHYS_OFFSET: 0x80000000 [name:mrdump&]pstate: 22400005 (nzCv daif +PAN -UAO) [name:mrdump&]pc : [0xffffffdbaf52bb2c] ufshcd_clear_cmd+0x280/0x288 [name:mrdump&]lr : [0xffffffdbaf52a774] ufshcd_wait_for_dev_cmd+0x3e4/0x82c [name:mrdump&]sp : ffffffc0081471b0 <snip> Workqueue: ufs_eh_wq_0 ufshcd_err_handler Call trace: dump_backtrace+0xf8/0x144 show_stack+0x18/0x24 dump_stack_lvl+0x78/0x9c dump_stack+0x18/0x44 mrdump_common_die+0x254/0x480 [mrdump] ipanic_die+0x20/0x30 [mrdump] notify_die+0x15c/0x204 die+0x10c/0x5f8 arm64_notify_die+0x74/0x13c do_debug_exception+0x164/0x26c el1_dbg+0x64/0x80 el1h_64_sync_handler+0x3c/0x90 el1h_64_sync+0x68/0x6c ufshcd_clear_cmd+0x280/0x288 ufshcd_wait_for_dev_cmd+0x3e4/0x82c ufshcd_exec_dev_cmd+0x5bc/0x9ac ufshcd_verify_dev_init+0x84/0x1c8 ufshcd_probe_hba+0x724/0x1ce0 ufshcd_host_reset_and_restore+0x260/0x574 ufshcd_reset_and_restore+0x138/0xbd0 ufshcd_err_handler+0x1218/0x2f28 process_one_work+0x5fc/0x1140 worker_thread+0x7d8/0xe20 kthread+0x25c/0x468 ret_from_fork+0x10/0x20

What

In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix shift issue in ufshcd_clear_cmd() When task_tag >= 32 (in MCQ mode) and sizeof(unsigned int) == 4, 1U << task_tag will out of bounds for a u32 mask. Fix this up to prevent SHIFT_ISSUE (bitwise shifts that are out of bounds for their data type). [name:debug_monitors&]Unexpected kernel BRK exception at EL1 [name:traps&]Internal error: BRK handler: 00000000f2005514 [#1] PREEMPT SMP [name:mediatek_cpufreq_hw&]cpufreq stop DVFS log done [name:mrdump&]Kernel Offset: 0x1ba5800000 from 0xffffffc008000000 [name:mrdump&]PHYS_OFFSET: 0x80000000 [name:mrdump&]pstate: 22400005 (nzCv daif +PAN -UAO) [name:mrdump&]pc : [0xffffffdbaf52bb2c] ufshcd_clear_cmd+0x280/0x288 [name:mrdump&]lr : [0xffffffdbaf52a774] ufshcd_wait_for_dev_cmd+0x3e4/0x82c [name:mrdump&]sp : ffffffc0081471b0 <snip> Workqueue: ufs_eh_wq_0 ufshcd_err_handler Call trace: dump_backtrace+0xf8/0x144 show_stack+0x18/0x24 dump_stack_lvl+0x78/0x9c dump_stack+0x18/0x44 mrdump_common_die+0x254/0x480 [mrdump] ipanic_die+0x20/0x30 [mrdump] notify_die+0x15c/0x204 die+0x10c/0x5f8 arm64_notify_die+0x74/0x13c do_debug_exception+0x164/0x26c el1_dbg+0x64/0x80 el1h_64_sync_handler+0x3c/0x90 el1h_64_sync+0x68/0x6c ufshcd_clear_cmd+0x280/0x288 ufshcd_wait_for_dev_cmd+0x3e4/0x82c ufshcd_exec_dev_cmd+0x5bc/0x9ac ufshcd_verify_dev_init+0x84/0x1c8 ufshcd_probe_hba+0x724/0x1ce0 ufshcd_host_reset_and_restore+0x260/0x574 ufshcd_reset_and_restore+0x138/0xbd0 ufshcd_err_handler+0x1218/0x2f28 process_one_work+0x5fc/0x1140 worker_thread+0x7d8/0xe20 kthread+0x25c/0x468 ret_from_fork+0x10/0x20

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: scsi: ufs: core: Fix shift issue in ufshcd_clear_cmd() When task_tag >= 32 (in MCQ mode) and sizeof(unsigned int) == 4, 1U << task_tag will out of bounds for a u32 mask. Fix this up to prevent SHIFT_ISSUE (bitwise shifts that are out of bounds for their data type). [name:debug_monitors&]Unexpected kernel BRK exception at EL1 [name:traps&]Internal error: BRK handler: 00000000f2005514 [#1] PREEMPT SMP [name:mediatek_cpufreq_hw&]cpufreq stop DVFS log done [name:mrdump&]Kernel Offset: 0x1ba5800000 from 0xffffffc008000000 [name:mrdump&]PHYS_OFFSET: 0x80000000 [name:mrdump&]pstate: 22400005 (nzCv daif +PAN -UAO) [name:mrdump&]pc : [0xffffffdbaf52bb2c] ufshcd_clear_cmd+0x280/0x288 [name:mrdump&]lr : [0xffffffdbaf52a774] ufshcd_wait_for_dev_cmd+0x3e4/0x82c [name:mrdump&]sp : ffffffc0081471b0 <snip> Workqueue: ufs_eh_wq_0 ufshcd_err_handler Call trace: dump_backtrace+0xf8/0x144 show_stack+0x18/0x24 dump_stack_lvl+0x78/0x9c dump_stack+0x18/0x44 mrdump_common_die+0x254/0x480 [mrdump] ipanic_die+0x20/0x30 [mrdump] notify_die+0x15c/0x204 die+0x10c/0x5f8 arm64_notify_die+0x74/0x13c do_debug_exception+0x164/0x26c el1_dbg+0x64/0x80 el1h_64_sync_handler+0x3c/0x90 el1h_64_sync+0x68/0x6c ufshcd_clear_cmd+0x280/0x288 ufshcd_wait_for_dev_cmd+0x3e4/0x82c ufshcd_exec_dev_cmd+0x5bc/0x9ac ufshcd_verify_dev_init+0x84/0x1c8 ufshcd_probe_hba+0x724/0x1ce0 ufshcd_host_reset_and_restore+0x260/0x574 ufshcd_reset_and_restore+0x138/0xbd0 ufshcd_err_handler+0x1218/0x2f28 process_one_work+0x5fc/0x1140 worker_thread+0x7d8/0xe20 kthread+0x25c/0x468 ret_from_fork+0x10/0x20

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
Low: no specialised conditions are recorded
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: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.
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-2025-0612IBM Security Guardium: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Guardium ausnutzen, um Sicherheitsbeschränkungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, beliebigen Code auszuführen und vertrauliche Informationen preiszugeben.

Official advisory ↗
BSI · German · WID-SEC-2024-0920Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240424Security Bulletin 24 Apr 2024

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

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

d?id=CVE-2024-26740 Référence CVE CVE-2024-26742 https://www.cve.org/CVERecord?id=CVE-2024-26742 Référence CVE CVE-2024-26756 https://www.cve.org/CVERecord?id=CVE-2024-26756 Référence CVE CVE-2024-26757 https://www.cve.org/CVERecord?id=CVE-2024-26757 Référence CVE CVE-2024-26758 https://www.cve.org/CVERecord?id=CVE-2024-26758 Référence CVE CVE-2024-26759 https://www.cve.org/CVERecord?id=CVE-2024-26759 Référence CVE CVE-2024-26767 https://www.cve.org/CVERecord?id=CVE-2024-26767 Référence CVE CVE-2024-26770 https://www.cve.org/CVERecord?id=CVE-2024-26770 Référence CVE CVE-2024-26807 https://www.cve.org/CVERecord?id=CVE-2024-26807 Référence CVE CVE-2024-26842 https://www.cve.org/CVERecord?id=CVE-2024-26842 Référence CVE CVE-2024-26844 https://www.cve.org/CVERecord?id=CVE-2024-26844 Référence CVE CVE-2024-26853 https://www.cve.org/CVERecord?id=CVE-2024-26853 Référence CVE CVE-2024-26866 https://www.cve.org/CVERecord?id=CVE-2024-26866 Référence CVE CVE-2024-26869 https://www.cve.org/CVERecord?id=CVE-2024-26869 Référence CVE CVE-2024-26876 https://www.cve.org/CVERecord?id=CVE-2024-26876 Référence CVE CVE-2024-26938 https://www.cve.org/CVERecord?id=CVE-2024-26938 Référence CVE CVE-2024-26948 https://www.cve.org/CVERecord?id=CVE-2024-26948 Référence CVE CVE-2024-26953 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26740 Référence CVE CVE-2024-26742 https://www.cve.org/CVERecord?id=CVE-2024-26742 Référence CVE CVE-2024-26756 https://www.cve.org/CVERecord?id=CVE-2024-26756 Référence CVE CVE-2024-26757 https://www.cve.org/CVERecord?id=CVE-2024-26757 Référence CVE CVE-2024-26758 https://www.cve.org/CVERecord?id=CVE-2024-26758 Référence CVE CVE-2024-26759 https://www.cve.org/CVERecord?id=CVE-2024-26759 Référence CVE CVE-2024-26767 https://www.cve.org/CVERecord?id=CVE-2024-26767 Référence CVE CVE-2024-26770 https://www.cve.org/CVERecord?id=CVE-2024-26770 Référence CVE CVE-2024-26807 https://www.cve.org/CVERecord?id=CVE-2024-26807 Référence CVE CVE-2024-26842 https://www.cve.org/CVERecord?id=CVE-2024-26842 Référence CVE CVE-2024-26844 https://www.cve.org/CVERecord?id=CVE-2024-26844 Référence CVE CVE-2024-26853 https://www.cve.org/CVERecord?id=CVE-2024-26853 Référence CVE CVE-2024-26866 https://www.cve.org/CVERecord?id=CVE-2024-26866 Référence CVE CVE-2024-26869 https://www.cve.org/CVERecord?id=CVE-2024-26869 Référence CVE CVE-2024-26876 https://www.cve.org/CVERecord?id=CVE-2024-26876 Référence CVE CVE-2024-26938 https://www.cve.org/CVERecord?id=CVE-2024-26938 Référence CVE CVE-2024-26948 https://www.cve.org/CVERecord?id=CVE-2024-26948 Référence CVE CVE-2024-26953 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0958Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-26810 Référence CVE CVE-2024-26818 https://www.cve.org/CVERecord?id=CVE-2024-26818 Référence CVE CVE-2024-26820 https://www.cve.org/CVERecord?id=CVE-2024-26820 Référence CVE CVE-2024-26823 https://www.cve.org/CVERecord?id=CVE-2024-26823 Référence CVE CVE-2024-26824 https://www.cve.org/CVERecord?id=CVE-2024-26824 Référence CVE CVE-2024-26825 https://www.cve.org/CVERecord?id=CVE-2024-26825 Référence CVE CVE-2024-26831 https://www.cve.org/CVERecord?id=CVE-2024-26831 Référence CVE CVE-2024-26837 https://www.cve.org/CVERecord?id=CVE-2024-26837 Référence CVE CVE-2024-26840 https://www.cve.org/CVERecord?id=CVE-2024-26840 Référence CVE CVE-2024-26842 https://www.cve.org/CVERecord?id=CVE-2024-26842 Référence CVE CVE-2024-26843 https://www.cve.org/CVERecord?id=CVE-2024-26843 Référence CVE CVE-2024-26844 https://www.cve.org/CVERecord?id=CVE-2024-26844 Référence CVE CVE-2024-26852 https://www.cve.org/CVERecord?id=CVE-2024-26852 Référence CVE CVE-2024-26853 https://www.cve.org/CVERecord?id=CVE-2024-26853 Référence CVE CVE-2024-26870 https://www.cve.org/CVERecord?id=CVE-2024-26870 Référence CVE CVE-2024-26878 https://www.cve.org/CVERecord?id=CVE-2024-26878 Référence CVE CVE-2024-26921 https://www.cve.org/CVERecord?id=CVE-2024-26921 Référence CVE CVE-2024-26925 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26813 Référence CVE CVE-2024-26814 https://www.cve.org/CVERecord?id=CVE-2024-26814 Référence CVE CVE-2024-26815 https://www.cve.org/CVERecord?id=CVE-2024-26815 Référence CVE CVE-2024-26816 https://www.cve.org/CVERecord?id=CVE-2024-26816 Référence CVE CVE-2024-26822 https://www.cve.org/CVERecord?id=CVE-2024-26822 Référence CVE CVE-2024-26826 https://www.cve.org/CVERecord?id=CVE-2024-26826 Référence CVE CVE-2024-26830 https://www.cve.org/CVERecord?id=CVE-2024-26830 Référence CVE CVE-2024-26832 https://www.cve.org/CVERecord?id=CVE-2024-26832 Référence CVE CVE-2024-26836 https://www.cve.org/CVERecord?id=CVE-2024-26836 Référence CVE CVE-2024-26842 https://www.cve.org/CVERecord?id=CVE-2024-26842 Référence CVE CVE-2024-26844 https://www.cve.org/CVERecord?id=CVE-2024-26844 Référence CVE CVE-2024-26845 https://www.cve.org/CVERecord?id=CVE-2024-26845 Référence CVE CVE-2024-26846 https://www.cve.org/CVERecord?id=CVE-2024-26846 Référence CVE CVE-2024-26853 https://www.cve.org/CVERecord?id=CVE-2024-26853 Référence CVE CVE-2024-26854 https://www.cve.org/CVERecord?id=CVE-2024-26854 Référence CVE CVE-2024-26855 https://www.cve.org/CVERecord?id=CVE-2024-26855 Référence CVE CVE-2024-26856 https://www.cve.org/CVERecord?id=CVE-2024-26856 Référence CVE CVE-2024-26857 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26767 Référence CVE CVE-2024-26780 https://www.cve.org/CVERecord?id=CVE-2024-26780 Référence CVE CVE-2024-26785 https://www.cve.org/CVERecord?id=CVE-2024-26785 Référence CVE CVE-2024-26800 https://www.cve.org/CVERecord?id=CVE-2024-26800 Référence CVE CVE-2024-26802 https://www.cve.org/CVERecord?id=CVE-2024-26802 Référence CVE CVE-2024-26813 https://www.cve.org/CVERecord?id=CVE-2024-26813 Référence CVE CVE-2024-26814 https://www.cve.org/CVERecord?id=CVE-2024-26814 Référence CVE CVE-2024-26826 https://www.cve.org/CVERecord?id=CVE-2024-26826 Référence CVE CVE-2024-26830 https://www.cve.org/CVERecord?id=CVE-2024-26830 Référence CVE CVE-2024-26842 https://www.cve.org/CVERecord?id=CVE-2024-26842 Référence CVE CVE-2024-26845 https://www.cve.org/CVERecord?id=CVE-2024-26845 Référence CVE CVE-2024-26863 https://www.cve.org/CVERecord?id=CVE-2024-26863 Référence CVE CVE-2024-26880 https://www.cve.org/CVERecord?id=CVE-2024-26880 Référence CVE CVE-2024-26889 https://www.cve.org/CVERecord?id=CVE-2024-26889 Référence CVE CVE-2024-26920 https://www.cve.org/CVERecord?id=CVE-2024-26920 Référence CVE CVE-2024-26923 https://www.cve.org/CVERecord?id=CVE-2024-26923 Référence CVE CVE-2024-26924 https://www.cve.org/CVERecord?id=CVE-2024-26924 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26644 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26687 https://www.cve.org/CVERecord?id=CVE-2024-26687 Référence CVE CVE-2024-26720 https://www.cve.org/CVERecord?id=CVE-2024-26720 Référence CVE CVE-2024-26745 https://www.cve.org/CVERecord?id=CVE-2024-26745 Référence CVE CVE-2024-26766 https://www.cve.org/CVERecord?id=CVE-2024-26766 Référence CVE CVE-2024-26813 https://www.cve.org/CVERecord?id=CVE-2024-26813 Référence CVE CVE-2024-26822 https://www.cve.org/CVERecord?id=CVE-2024-26822 Référence CVE CVE-2024-26828 https://www.cve.org/CVERecord?id=CVE-2024-26828 Référence CVE CVE-2024-26842 https://www.cve.org/CVERecord?id=CVE-2024-26842 Référence CVE CVE-2024-26845 https://www.cve.org/CVERecord?id=CVE-2024-26845 Référence CVE CVE-2024-26852 https://www.cve.org/CVERecord?id=CVE-2024-26852 Référence CVE CVE-2024-26863 https://www.cve.org/CVERecord?id=CVE-2024-26863 Référence CVE CVE-2024-26894 https://www.cve.org/CVERecord?id=CVE-2024-26894 Référence CVE CVE-2024-26921 https://www.cve.org/CVERecord?id=CVE-2024-26921 Référence CVE CVE-2024-26923 https://www.cve.org/CVERecord?id=CVE-2024-26923 Référence CVE CVE-2024-26928 https://www.cve.org/CVERecord?id=CVE-2024-26928 Référence CVE CVE-2024-26930 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-020041Linux の 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.
Patch available
Affected
Linux: adf452611677d048203398f489e2175a9068f9f7 < 7ac9e18f5d66087cd22751c5c5bf0090eb0038fe, adf452611677d048203398f489e2175a9068f9f7 < a992425d18e5f7c48931121993c6c69426f2a8fb, adf452611677d048203398f489e2175a9068f9f7 < b513d30d59bb383a6a5d6b533afcab2cee99a8f8, 6.5
Fixed
Linux: < 6.5, 6.6.19 ≤ 6.6.*, 6.7.7 ≤ 6.7.*, 6.8 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 17 Apr 2024 · Last source change 11 May 2026, 20:05 UTC · CWE-787 · Out-of-bounds Write

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-24104
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD enriched

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
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-26842 · cve.blacktree.nl