CyberSecBulletin
CVE-2026-63847NVD status: Modified

Linux: Improper Check for Unusual or Exceptional Conditions

Published Updated By the CyberSecBulletin desk

CVE-2026-63847 is a high-severity improper check for unusual or exceptional conditions vulnerability in Linux, with a CVSS 3.1 base score of 7.8 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 c9e367e6e630e1655184ca886a9290bfe8cb30a9, 63691e396105611173072ad548fc2b68831ecf23, 4d96e3cbfc66e4d66ea0096bde858e28ab62da00 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.18% 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 c9e367e6e630e1655184ca886a9290bfe8cb30a9 or 63691e396105611173072ad548fc2b68831ecf23 or 4d96e3cbfc66e4d66ea0096bde858e28ab62da00 or 3a96fee676fc0caf08f03ad915bec6fcd144d551, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.141 or 6.12.91 or 6.18.33 or 7.0.10, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux14f43e8f88c57bbeaed3d05f13efab733f5e2338 up to, but not including, c9e367e6e630e1655184ca886a9290bfe8cb30a9; 14f43e8f88c57bbeaed3d05f13efab733f5e2338 up to, but not including, 63691e396105611173072ad548fc2b68831ecf23; 14f43e8f88c57bbeaed3d05f13efab733f5e2338 up to, but not including, 4d96e3cbfc66e4d66ea0096bde858e28ab62da00; 14f43e8f88c57bbeaed3d05f13efab733f5e2338 up to, but not including, 3a96fee676fc0caf08f03ad915bec6fcd144d551; 14f43e8f88c57bbeaed3d05f13efab733f5e2338 up to, but not including, 694fe016969c5e5a24b9e0ef7c1307eedec8ddf8; 14f43e8f88c57bbeaed3d05f13efab733f5e2338 up to, but not including, 79405e774ede411c6b47ed41c651e40b92de64a2; 5.6c9e367e6e630e1655184ca886a9290bfe8cb30a9, 63691e396105611173072ad548fc2b68831ecf23, 4d96e3cbfc66e4d66ea0096bde858e28ab62da00, 3a96fee676fc0caf08f03ad915bec6fcd144d551, 694fe016969c5e5a24b9e0ef7c1307eedec8ddf8, 79405e774ede411c6b47ed41c651e40b92de64a2
LinuxLinux Kernel5.6 up to, but not including, 6.6.141; 6.7 up to, but not including, 6.12.91; 6.13 up to, but not including, 6.18.33; 6.19 up to, but not including, 7.0.10; 7.16.6.141, 6.12.91, 6.18.33, 7.0.10

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
HighData or code can be modified at will.
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:H/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences. (cherry picked from commit 3216a7f4e2642bda5fd14f57586e835ae9202587)

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: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Check for Unusual or Exceptional Conditions vulnerabilities

Spotted an error? Tell us.