Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-53090 — kernel

🟠 CVSS 7.8 — High ✅ No Known Exploit NVD
7.8
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

bpf: Fix ld_{abs,ind} failure path analysis in subprogs

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.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2026-53090 is recorded against 2 packages.

  • kernel (from 6.19.0 up to 7.0.10)
  • linux-kernel (from 5.10 up to 7.0.10)

Timeline and source

Published on 24 June 2026 and last revised on 20 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
security.access.redhat.com (Web)
access.redhat.com (Advisory)
github.com (Advisory)
nvd.nist.gov (Advisory)
bugzilla.redhat.com (Report)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

Details

Severity High
CVSS Score 7.8
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2026-06-24
Updated 2026-08-20
Modified 2026-08-20

Affected Packages

Software From version Fixed in
kernel 6.19.0 7.0.10
linux-kernel 5.10 7.0.10

References

Similar Threats

Site Security Check

Is kernel part of your stack?

CVE-2026-53090 is rated CVSS 7.8 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026
✓