Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53090: bpf: Fix ld_{abs,ind} failure path analysis in subprogs

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 37ad2bb11e9de92cb7b94548705eeedd87f7d392, 8674e2db06cff6b50f2216eed9a761d15425bb34, 8a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbe.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 37ad2bb11e9de92cb7b94548705eeedd87f7d392, 8674e2db06cff6b50f2216eed9a761d15425bb34, 8a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbe or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jun 24, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-53090

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.10affected
    • 09b28d76eac48e922dc293da1aa2b2b85c32aeee and later · before 928d354ae3557e8f755a227e67be88034eb3cd7faffected · git
    • 09b28d76eac48e922dc293da1aa2b2b85c32aeee and later · before 8a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbeaffected · git
    • 09b28d76eac48e922dc293da1aa2b2b85c32aeee and later · before de1055e7f9e67af32b1f3376066272b04e5223c0affected · git
    • 09b28d76eac48e922dc293da1aa2b2b85c32aeee and later · before 37ad2bb11e9de92cb7b94548705eeedd87f7d392affected · git
    • 09b28d76eac48e922dc293da1aa2b2b85c32aeee and later · before 8674e2db06cff6b50f2216eed9a761d15425bb34affected · git
    • 09b28d76eac48e922dc293da1aa2b2b85c32aeee and later · before ce01a4e5cfac7adbe0be565f90cd32ecbb2f8337affected · git
    • 09b28d76eac48e922dc293da1aa2b2b85c32aeee and later · before d846d83bdacbd8f14fc45c63b8c1d22608452e1caffected · git
    • 09b28d76eac48e922dc293da1aa2b2b85c32aeee and later · before ee861486e377edc55361c08dcbceab3f6b6577bdaffected · git
    • before 5.10not affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.10 and later · before 7.0.10

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.101-1~deb12u16.12.101-1~deb12u1
Debian:13linuxbefore 6.12.101-16.12.101-1
Debian:14linuxbefore 7.0.10-17.0.10-1
SUSE:Linux Micro 6.1kernel-rtbefore 6.4.0-159998.53.16.4.0-159998.53.1
SUSE:Linux Micro 6.1kernel-source-rtbefore 6.4.0-159998.53.16.4.0-159998.53.1
SUSE:Linux Micro 6.2podmanbefore 5.4.2-160000.6.15.4.2-160000.6.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53088Jun 24, 2026 · net: bcmgenet: fix off-by-one in bcmgenet_put_txcb
    39Monitor
  • ← EarlierCVE-2026-53089Jun 24, 2026 · bpf: Fix use-after-free in offloaded map/prog info fill
    31Monitor
  • Later →CVE-2026-53091Jun 24, 2026 · net: pull headers in qdisc_pkt_len_segs_init()
    33Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux37ad2bb11e9de92cb7b94548705eeedd87f7d392Vendor (CNA)
Linux Linux8674e2db06cff6b50f2216eed9a761d15425bb34Vendor (CNA)
Linux Linux8a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbeVendor (CNA)
Linux Linux928d354ae3557e8f755a227e67be88034eb3cd7fVendor (CNA)
Linux Linuxce01a4e5cfac7adbe0be565f90cd32ecbb2f8337Vendor (CNA)
Linux Linuxd846d83bdacbd8f14fc45c63b8c1d22608452e1cVendor (CNA)
Linux Linuxde1055e7f9e67af32b1f3376066272b04e5223c0Vendor (CNA)
Linux Linuxee861486e377edc55361c08dcbceab3f6b6577bdVendor (CNA)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.101-1~deb12u1 · Debian:12Package registry (OSV)
suse:kernel-rt6.4.0-159998.53.1 · SUSE:Linux Micro 6.1Package registry (OSV)
suse:kernel-source-rt6.4.0-159998.53.1 · SUSE:Linux Micro 6.1Package registry (OSV)
suse:podman5.4.2-160000.6.1 · SUSE:Linux Micro 6.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records