Skip to main content

Linux EUVDEUVD-2026-59529

| CVE-2026-74382
2026-08-15 Linux GHSA-v8p9-m6wc-2cv3
View
Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives. Why: No CVSS yet + weak signal (CWE or non-zero EPSS).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

In the Linux kernel, the following vulnerability has been resolved:

net/sched: cls_bpf: prevent unbounded recursion in offload rollback

Quan Sun reported [1] a stack overflow in cls_bpf_offload_cmd().

Reproducer on netdevsim: add a skip_sw cls_bpf filter, set the bpf_tc_accept debugfs knob to 0, then tc filter replace. The replace calls tc_setup_cb_replace() which fails. cls_bpf_offload_cmd() then swaps prog/oldprog and recursively calls itself to roll back. But bpf_tc_accept=0 makes the rollback fail too, which triggers yet another rollback frame with the same arguments, and so on until the stack is exhausted.

bpf_tc_accept is just a convenient knob for the reproducer. Any driver whose tc_setup_cb_replace() fails twice in a row can hit the same loop, so this is not a netdevsim-only issue.

Two ways to fix it:

  1. Have the rollback call tc_setup_cb_add() on oldprog instead of

re-entering cls_bpf_offload_cmd().

  1. Mark the rollback frame with a flag and skip a second-level

rollback from inside it.

Go with (2). It is the smaller change and keeps the original behaviour: the rollback still goes through tc_setup_cb_replace(), so the driver gets one real chance to restore its state. If that attempt also fails, we just return the original error instead of recursing.

[1]: https://lore.kernel.org/bpf/ce5a6005-3c5e-4696-9e05-eba9461dc860@std.uestc.edu.cn/T/#u

Affected VersionsENISA

Linux 102740bd9436a3a6ba129af3a48271d794009fa5 <e2d3b7bab3748c811dc5750ce9a8d62bc7f90ed7
Linux 102740bd9436a3a6ba129af3a48271d794009fa5 <10753da2d659dd425a6e620f47f86852d604f67f
Linux 102740bd9436a3a6ba129af3a48271d794009fa5 <4a76953c3ed043797e81529b9395e9ca6f4c7609
Linux patch: 5.15.212
Linux 4.15
Linux patch: 0
Linux 102740bd9436a3a6ba129af3a48271d794009fa5 <33373e1f378a501bc51aa73312f74295c84e3101
Linux patch: 6.1.178
Linux 102740bd9436a3a6ba129af3a48271d794009fa5 <1387f252a242a51bfbb6eace29c8f8db21b457da
Linux 102740bd9436a3a6ba129af3a48271d794009fa5 <3fa6fb5d771c992ebedbfa7331c6bcc6f33f89b7
Linux patch: 6.18.40
Linux patch: 6.12.97
Linux 102740bd9436a3a6ba129af3a48271d794009fa5 <a018f208ab7512380bd4cf670064d48cba00a1b1
Linux 102740bd9436a3a6ba129af3a48271d794009fa5 <27db54b90bcc7c37867fe664107fa25ea6a116e4
Linux patch: 7.1.5
Linux patch: 7.2-rc1
Linux patch: 5.10.261
Linux patch: 6.6.145

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Lifecycle Timeline

2
Patch available
Aug 15, 2026 - 07:19 EUVD
CVE Published
Aug 15, 2026 - 05:58 cve.org
UNKNOWN (no severity yet)

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Data Quality
1 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity Not scored yet
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
No CVSS yet + weak signal (CWE or non-zero EPSS)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy