CyberSecBulletin
CVE-2026-31739NVD status: Modified

Linux: Reachable Assertion

Published Updated By the CyberSecBulletin desk

CVE-2026-31739 is a high-severity reachable assertion vulnerability in Linux, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions bdbf027a4504b4a86740de6beb6d18a957331839, 3aea268b6d5cde3b087df9eeecc3bc620aa09513, 429d05565eb19ee545d8a8395991372adbe4daf3 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.41% 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 bdbf027a4504b4a86740de6beb6d18a957331839 or 3aea268b6d5cde3b087df9eeecc3bc620aa09513 or 429d05565eb19ee545d8a8395991372adbe4daf3 or 4b56770d345524fc2acc143a2b85539cf7d74bc1, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.12.81 or 6.18.22 or 6.19.12, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 up to, but not including, bdbf027a4504b4a86740de6beb6d18a957331839; 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 up to, but not including, 3aea268b6d5cde3b087df9eeecc3bc620aa09513; 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 up to, but not including, 429d05565eb19ee545d8a8395991372adbe4daf3; 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 up to, but not including, 4b56770d345524fc2acc143a2b85539cf7d74bc1; 6.10bdbf027a4504b4a86740de6beb6d18a957331839, 3aea268b6d5cde3b087df9eeecc3bc620aa09513, 429d05565eb19ee545d8a8395991372adbe4daf3, 4b56770d345524fc2acc143a2b85539cf7d74bc1
LinuxLinux Kernel6.10 up to, but not including, 6.12.81; 6.13 up to, but not including, 6.18.22; 6.19 up to, but not including, 6.19.12; 7.06.12.81, 6.18.22, 6.19.12

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
NetworkCan be exploited remotely over a network, including the internet.
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:N/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: crypto: tegra - Add missing CRYPTO_ALG_ASYNC The tegra crypto driver failed to set the CRYPTO_ALG_ASYNC on its asynchronous algorithms, causing the crypto API to select them for users that request only synchronous algorithms. This causes crashes (at least). Fix this by adding the flag like what the other drivers do. Also remove the unnecessary CRYPTO_ALG_TYPE_* flags, since those just get ignored and overridden by the registration function anyway.

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

The underlying weakness: Reachable Assertion

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

How developers prevent this class of flaw

  • If the assertion statement is required (e.g., for security or reliability), change the invoking code to avoid the conditions that trigger the assertion.
  • Consider changing the assertion to some other less fatal error. This might not be easy to implement, since other code may be needed to handle the error.
  • Make sensitive open/close operations non-reachable from directly user-controlled data (e.g. open/close resources)

More Reachable Assertion vulnerabilities (CWE-617)

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 Reachable Assertion vulnerabilities

Spotted an error? Tell us.