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

tee: optee: Fix kernel panic caused by incorrect error handling

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 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.23% 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.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.85-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.12-1Debian Security Tracker ↗Source updated 6 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-35785 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: tee: optee: Fix kernel panic caused by incorrect error handling
198 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel's Trusted Execution Environment (TEE) subsystem, specifically within the Open Portable Trusted Execution Environment (OP-TEE) component. Incorrect error handling in this component can lead to a kernel panic, resulting in a denial of service. A local attacker could potentially exploit this vulnerability.
Remediation
No remediation text is recorded.
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-35778

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: tee: optee: Fix kernel panic caused by incorrect error handling The error path while failing to register devices on the TEE bus has a bug leading to kernel panic as follows: [ 15.398930] Unable to handle kernel paging request at virtual address ffff07ed00626d7c [ 15.406913] Mem abort info: [ 15.409722] ESR = 0x0000000096000005 [ 15.413490] EC = 0x25: DABT (current EL), IL = 32 bits [ 15.418814] SET = 0, FnV = 0 [ 15.421878] EA = 0, S1PTW = 0 [ 15.425031] FSC = 0x05: level 1 translation fault [ 15.429922] Data abort info: [ 15.432813] ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 [ 15.438310] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 15.443372] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 15.448697] swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000d9e3e000 [ 15.455413] [ffff07ed00626d7c] pgd=1800000bffdf9003, p4d=1800000bffdf9003, pud=0000000000000000 [ 15.464146] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP Commit 7269cba53d90 ("tee: optee: Fix supplicant based device enumeration") lead to the introduction of this bug. So fix it appropriately.

What

In the Linux kernel, the following vulnerability has been resolved: tee: optee: Fix kernel panic caused by incorrect error handling The error path while failing to register devices on the TEE bus has a bug leading to kernel panic as follows: [ 15.398930] Unable to handle kernel paging request at virtual address ffff07ed00626d7c [ 15.406913] Mem abort info: [ 15.409722] ESR = 0x0000000096000005 [ 15.413490] EC = 0x25: DABT (current EL), IL = 32 bits [ 15.418814] SET = 0, FnV = 0 [ 15.421878] EA = 0, S1PTW = 0 [ 15.425031] FSC = 0x05: level 1 translation fault [ 15.429922] Data abort info: [ 15.432813] ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 [ 15.438310] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 15.443372] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 15.448697] swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000d9e3e000 [ 15.455413] [ffff07ed00626d7c] pgd=1800000bffdf9003, p4d=1800000bffdf9003, pud=0000000000000000 [ 15.464146] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP Commit 7269cba53d90 ("tee: optee: Fix supplicant based device enumeration") lead to the introduction of this bug. So fix it appropriately.

Why

The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.

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: tee: optee: Fix kernel panic caused by incorrect error handling The error path while failing to register devices on the TEE bus has a bug leading to kernel panic as follows: [ 15.398930] Unable to handle kernel paging request at virtual address ffff07ed00626d7c [ 15.406913] Mem abort info: [ 15.409722] ESR = 0x0000000096000005 [ 15.413490] EC = 0x25: DABT (current EL), IL = 32 bits [ 15.418814] SET = 0, FnV = 0 [ 15.421878] EA = 0, S1PTW = 0 [ 15.425031] FSC = 0x05: level 1 translation fault [ 15.429922] Data abort info: [ 15.432813] ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 [ 15.438310] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 15.443372] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 15.448697] swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000d9e3e000 [ 15.455413] [ffff07ed00626d7c] pgd=1800000bffdf9003, p4d=1800000bffdf9003, pud=0000000000000000 [ 15.464146] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP Commit 7269cba53d90 ("tee: optee: Fix supplicant based device enumeration") lead to the introduction of this bug. So fix it appropriately.

Why

The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.

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 → Improper Check for Unusual or Exceptional Conditions → 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-754 ↗

CWE-754: Improper Check for Unusual or Exceptional Conditions. The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.

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-754
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-1188Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240522Security Bulletin 22 May 2024

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

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

d?id=CVE-2024-31076 Référence CVE CVE-2024-32936 https://www.cve.org/CVERecord?id=CVE-2024-32936 Référence CVE CVE-2024-33619 https://www.cve.org/CVERecord?id=CVE-2024-33619 Référence CVE CVE-2024-33621 https://www.cve.org/CVERecord?id=CVE-2024-33621 Référence CVE CVE-2024-33847 https://www.cve.org/CVERecord?id=CVE-2024-33847 Référence CVE CVE-2024-34027 https://www.cve.org/CVERecord?id=CVE-2024-34027 Référence CVE CVE-2024-34030 https://www.cve.org/CVERecord?id=CVE-2024-34030 Référence CVE CVE-2024-34777 https://www.cve.org/CVERecord?id=CVE-2024-34777 Référence CVE CVE-2024-35247 https://www.cve.org/CVERecord?id=CVE-2024-35247 Référence CVE CVE-2024-35785 https://www.cve.org/CVERecord?id=CVE-2024-35785 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35796 https://www.cve.org/CVERecord?id=CVE-2024-35796 Référence CVE CVE-2024-35804 https://www.cve.org/CVERecord?id=CVE-2024-35804 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27414 Référence CVE CVE-2024-27415 https://www.cve.org/CVERecord?id=CVE-2024-27415 Référence CVE CVE-2024-27416 https://www.cve.org/CVERecord?id=CVE-2024-27416 Référence CVE CVE-2024-27417 https://www.cve.org/CVERecord?id=CVE-2024-27417 Référence CVE CVE-2024-27419 https://www.cve.org/CVERecord?id=CVE-2024-27419 Référence CVE CVE-2024-27431 https://www.cve.org/CVERecord?id=CVE-2024-27431 Référence CVE CVE-2024-27432 https://www.cve.org/CVERecord?id=CVE-2024-27432 Référence CVE CVE-2024-27436 https://www.cve.org/CVERecord?id=CVE-2024-27436 Référence CVE CVE-2024-27437 https://www.cve.org/CVERecord?id=CVE-2024-27437 Référence CVE CVE-2024-35785 https://www.cve.org/CVERecord?id=CVE-2024-35785 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35796 https://www.cve.org/CVERecord?id=CVE-2024-35796 Référence CVE CVE-2024-35804 https://www.cve.org/CVERecord?id=CVE-2024-35804 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27078 Référence CVE CVE-2024-27388 https://www.cve.org/CVERecord?id=CVE-2024-27388 Référence CVE CVE-2024-27393 https://www.cve.org/CVERecord?id=CVE-2024-27393 Référence CVE CVE-2024-27395 https://www.cve.org/CVERecord?id=CVE-2024-27395 Référence CVE CVE-2024-27396 https://www.cve.org/CVERecord?id=CVE-2024-27396 Référence CVE CVE-2024-27416 https://www.cve.org/CVERecord?id=CVE-2024-27416 Référence CVE CVE-2024-27419 https://www.cve.org/CVERecord?id=CVE-2024-27419 Référence CVE CVE-2024-27436 https://www.cve.org/CVERecord?id=CVE-2024-27436 Référence CVE CVE-2024-27437 https://www.cve.org/CVERecord?id=CVE-2024-27437 Référence CVE CVE-2024-35785 https://www.cve.org/CVERecord?id=CVE-2024-35785 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35796 https://www.cve.org/CVERecord?id=CVE-2024-35796 Référence CVE CVE-2024-35804 https://www.cve.org/CVERecord?id=CVE-2024-35804 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27078 Référence CVE CVE-2024-27388 https://www.cve.org/CVERecord?id=CVE-2024-27388 Référence CVE CVE-2024-27393 https://www.cve.org/CVERecord?id=CVE-2024-27393 Référence CVE CVE-2024-27395 https://www.cve.org/CVERecord?id=CVE-2024-27395 Référence CVE CVE-2024-27396 https://www.cve.org/CVERecord?id=CVE-2024-27396 Référence CVE CVE-2024-27416 https://www.cve.org/CVERecord?id=CVE-2024-27416 Référence CVE CVE-2024-27419 https://www.cve.org/CVERecord?id=CVE-2024-27419 Référence CVE CVE-2024-27436 https://www.cve.org/CVERecord?id=CVE-2024-27436 Référence CVE CVE-2024-27437 https://www.cve.org/CVERecord?id=CVE-2024-27437 Référence CVE CVE-2024-35785 https://www.cve.org/CVERecord?id=CVE-2024-35785 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35796 https://www.cve.org/CVERecord?id=CVE-2024-35796 Référence CVE CVE-2024-35804 https://www.cve.org/CVERecord?id=CVE-2024-35804 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27414 Référence CVE CVE-2024-27416 https://www.cve.org/CVERecord?id=CVE-2024-27416 Référence CVE CVE-2024-27417 https://www.cve.org/CVERecord?id=CVE-2024-27417 Référence CVE CVE-2024-27419 https://www.cve.org/CVERecord?id=CVE-2024-27419 Référence CVE CVE-2024-27431 https://www.cve.org/CVERecord?id=CVE-2024-27431 Référence CVE CVE-2024-27436 https://www.cve.org/CVERecord?id=CVE-2024-27436 Référence CVE CVE-2024-27437 https://www.cve.org/CVERecord?id=CVE-2024-27437 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-33621 https://www.cve.org/CVERecord?id=CVE-2024-33621 Référence CVE CVE-2024-35785 https://www.cve.org/CVERecord?id=CVE-2024-35785 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35796 https://www.cve.org/CVERecord?id=CVE-2024-35796 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35811 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-030012Debian等の複数ベンダの製品における例外的な状態のチェックに関する脆弱性

Linuxカーネルにおいて、次の脆弱性が修正されました:tee: opteeにおける不適切なエラー処理によるカーネルパニックの問題です。TEEバス上でデバイス登録に失敗した際のエラー処理経路にバグが存在し、次のようなカーネルパニックが発生していました:[ 15.398930] 仮想アドレス ffff07ed00626d7c にてカーネルページングリクエストを処理できませんでした。[ 15.406913] メモリアボート情報:[ 15.409722] ESR = 0x0000000096000005 [ 15.413490] EC = 0x25: DABT (current EL)、IL = 32ビット [ 15.418814] SET = 0、FnV = 0 [ 15.421878] EA = 0、S1PTW = 0 [ 15.425031] FSC = 0x05: レベル1変換フォルト [ 15.429922] データアボート情報:[ 15.432813] ISV = 0、ISS = 0x00000005、ISS2 = 0x00000000 [ 15.438310] CM = 0、WnR = 0、TnD = 0、TagAccess = 0 [ 15.443372] GCS = 0、Overlay = 0、DirtyBit = 0、Xs = 0 [ 15.448697] スワッパーpgtableは4kページ、48ビットVA、pgdp=00000000d9e3e000です。[ 15.455413] [ffff07ed00626d7c] pgd=1800000bffdf9003、p4d=1800000bffdf9003、pud=0000000000000000 [ 15.464146] 内部エラーが発生しました:Oops: 0000000096000005 [#1]。このバグはコミット7269cba53d90("tee: optee: Fix supplicant based device enumeration")で導入されました。したがって、この問題を適切に修正しました。

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: a953e45ebeae9a5ce342c012f7eb2a92cc8af89b < bc40ded92af55760d12bec8222d4108de725dbe4, 01c13d8a95e0909f0081d6e3e8a891761992371b < 4b12ff5edd141926d49c9ace4791adf3a4902fe7, 1c9561b438cbe61e78515fc7b16dc7fb8cf0b763 < e5b5948c769aa1ebf962dddfb972f87d8f166f95, d3c4786b01aad8c377718f92d6d9b15906ee0a2a < 520f79c110ff712b391b3d87fcacf03c74bc56ee, 7269cba53d906cf257c139d3b3a53ad272176bca < bfa344afbe472a9be08f78551fa2190c1a07d7d3, 7269cba53d906cf257c139d3b3a53ad272176bca < 95915ba4b987cf2b222b0f251280228a1ff977ac, 5.10.204 < 5.10.215, 5.15.143 < 5.15.154, 6.1.68 < 6.1.84, 6.6.7 < 6.6.24, 6.7
Fixed
Linux: < 6.7, 5.10.215 ≤ 5.10.*, 5.15.154 ≤ 5.15.*, 6.1.84 ≤ 6.1.*, 6.6.24 ≤ 6.6.*, 6.7.12 ≤ 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 May 2024 · Last source change 5 Aug 2026, 11:29 UTC · CWE-754 · Improper Check for Unusual or Exceptional Conditions

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-35778
Product sourceCNA
Remediation sourceCVE/CNA references
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
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-35785 · cve.blacktree.nl