CyberSecBulletin
CVE-2026-53090NVD status: Modified

Linux: Incorrect Check of Function Return Value

Published Updated By the CyberSecBulletin desk

CVE-2026-53090 is a high-severity incorrect check of function return value 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 928d354ae3557e8f755a227e67be88034eb3cd7f, 8a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbe, de1055e7f9e67af32b1f3376066272b04e5223c0 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.14% 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 928d354ae3557e8f755a227e67be88034eb3cd7f or 8a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbe or de1055e7f9e67af32b1f3376066272b04e5223c0 or 37ad2bb11e9de92cb7b94548705eeedd87f7d392, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 7.0.10 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux09b28d76eac48e922dc293da1aa2b2b85c32aeee up to, but not including, 928d354ae3557e8f755a227e67be88034eb3cd7f; 09b28d76eac48e922dc293da1aa2b2b85c32aeee up to, but not including, 8a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbe; 09b28d76eac48e922dc293da1aa2b2b85c32aeee up to, but not including, de1055e7f9e67af32b1f3376066272b04e5223c0; 09b28d76eac48e922dc293da1aa2b2b85c32aeee up to, but not including, 37ad2bb11e9de92cb7b94548705eeedd87f7d392; 09b28d76eac48e922dc293da1aa2b2b85c32aeee up to, but not including, 8674e2db06cff6b50f2216eed9a761d15425bb34; 09b28d76eac48e922dc293da1aa2b2b85c32aeee up to, but not including, ce01a4e5cfac7adbe0be565f90cd32ecbb2f8337; 09b28d76eac48e922dc293da1aa2b2b85c32aeee up to, but not including, d846d83bdacbd8f14fc45c63b8c1d22608452e1c; 09b28d76eac48e922dc293da1aa2b2b85c32aeee up to, but not including, ee861486e377edc55361c08dcbceab3f6b6577bd; and 1 more ranges928d354ae3557e8f755a227e67be88034eb3cd7f, 8a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbe, de1055e7f9e67af32b1f3376066272b04e5223c0, 37ad2bb11e9de92cb7b94548705eeedd87f7d392, 8674e2db06cff6b50f2216eed9a761d15425bb34, ce01a4e5cfac7adbe0be565f90cd32ecbb2f8337
Red HatRed Hat Enterprise Linux 10Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 6Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 7Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
LinuxLinux Kernel5.10 up to, but not including, 7.0.107.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.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.16.4MediumCNA

Official description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix ld_{abs,ind} failure path analysis in subprogs Usage of ld_{abs,ind} instructions got extended into subprogs some time ago via commit 09b28d76eac4 ("bpf: Add abnormal return checks."). These are only allowed in subprograms when the latter are BTF annotated and have scalar return types. The code generator in bpf_gen_ld_abs() has an abnormal exit path (r0=0 + exit) from legacy cBPF times. While the enforcement is on scalar return types, the verifier must also simulate the path of abnormal exit if the packet data load via ld_{abs,ind} failed. This is currently not the case. Fix it by having the verifier simulate both success and failure paths, and extend it in similar ways as we do for tail calls. The success path (r0=unknown, continue to next insn) is pushed onto stack for later validation and the r0=0 and return to the caller is done on the fall-through side.

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

The underlying weakness: Incorrect Check of Function Return Value

The product incorrectly checks a return value from a function, which prevents it from detecting errors or exceptional conditions.

How developers prevent this class of flaw

  • Use a language or compiler that uses exceptions and requires the catching of those exceptions.
  • Properly check all functions which return a value.
  • When designing any function make sure you return a value or throw an exception in case of an error.

More Incorrect Check of Function Return Value vulnerabilities (CWE-253)

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 Incorrect Check of Function Return Value vulnerabilities

Spotted an error? Tell us.