CyberSecBulletin
CVE-2024-35785NVD status: Modified

Linux: Improper Check for Unusual or Exceptional Conditions

Published Updated By the CyberSecBulletin desk

CVE-2024-35785 is a high-severity improper check for unusual or exceptional conditions vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions bc40ded92af55760d12bec8222d4108de725dbe4, 4b12ff5edd141926d49c9ace4791adf3a4902fe7, e5b5948c769aa1ebf962dddfb972f87d8f166f95 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.23% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to bc40ded92af55760d12bec8222d4108de725dbe4 or 4b12ff5edd141926d49c9ace4791adf3a4902fe7 or e5b5948c769aa1ebf962dddfb972f87d8f166f95 or 520f79c110ff712b391b3d87fcacf03c74bc56ee, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.215 or 5.15.154 or 6.1.84 or 6.6.24, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxa953e45ebeae9a5ce342c012f7eb2a92cc8af89b up to, but not including, bc40ded92af55760d12bec8222d4108de725dbe4; 01c13d8a95e0909f0081d6e3e8a891761992371b up to, but not including, 4b12ff5edd141926d49c9ace4791adf3a4902fe7; 1c9561b438cbe61e78515fc7b16dc7fb8cf0b763 up to, but not including, e5b5948c769aa1ebf962dddfb972f87d8f166f95; d3c4786b01aad8c377718f92d6d9b15906ee0a2a up to, but not including, 520f79c110ff712b391b3d87fcacf03c74bc56ee; 7269cba53d906cf257c139d3b3a53ad272176bca up to, but not including, bfa344afbe472a9be08f78551fa2190c1a07d7d3; 7269cba53d906cf257c139d3b3a53ad272176bca up to, but not including, 95915ba4b987cf2b222b0f251280228a1ff977ac; 5.10.204 up to, but not including, 5.10.215; 5.15.143 up to, but not including, 5.15.154; and 3 more rangesbc40ded92af55760d12bec8222d4108de725dbe4, 4b12ff5edd141926d49c9ace4791adf3a4902fe7, e5b5948c769aa1ebf962dddfb972f87d8f166f95, 520f79c110ff712b391b3d87fcacf03c74bc56ee, bfa344afbe472a9be08f78551fa2190c1a07d7d3, 95915ba4b987cf2b222b0f251280228a1ff977ac
LinuxLinux Kernel5.10.204 up to, but not including, 5.10.215; 5.15.143 up to, but not including, 5.15.154; 6.1.68 up to, but not including, 6.1.84; 6.6.7 up to, but not including, 6.6.24; 6.7.1 up to, but not including, 6.7.12; 6.7; 6.85.10.215, 5.15.154, 6.1.84, 6.6.24, 6.7.12
DebianDebian Linux10.0Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.17.1HighNVD

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: 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.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Choose languages with features such as exception handling that force the programmer to anticipate unusual conditions that may generate exceptions. Custom exceptions may need to be developed to handle unusual business-logic conditions. Be careful not to pass sensitive exceptions back to the user (CWE-209, CWE-248).
  • Check the results of all functions that return a value and verify that the value is expected.
  • If using exception handling, catch and throw specific exceptions instead of overly-general exceptions (CWE-396, CWE-397). Catch and handle exceptions as locally as possible so that exceptions do not propagate too far up the call stack (CWE-705). Avoid unchecked or uncaught exceptions where feasible (CWE-248).

More Improper Check for Unusual or Exceptional Conditions vulnerabilities (CWE-754)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Recent Improper Check for Unusual or Exceptional Conditions vulnerabilities

Spotted an error? Tell us.