Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-74382: net/sched: cls_bpf: prevent unbounded recursion in offload rollback

Noroxi assessment

Priority: Monitor (action score 0/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.19% (FIRST EPSS).
  • Fixed version: Linux Linux 10753da2d659dd425a6e620f47f86852d604f67f, 1387f252a242a51bfbb6eace29c8f8db21b457da, 27db54b90bcc7c37867fe664107fa25ea6a116e4.

Low priority for now. Upgrade to Linux Linux 10753da2d659dd425a6e620f47f86852d604f67f, 1387f252a242a51bfbb6eace29c8f8db21b457da, 27db54b90bcc7c37867fe664107fa25ea6a116e4 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: 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(). 2) 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

—No exploit Fix available
Published
Aug 15, 2026
Updated
Nov 6, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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-74382

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

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.

—

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

    • 4.15affected
    • 102740bd9436a3a6ba129af3a48271d794009fa5 and later · before a018f208ab7512380bd4cf670064d48cba00a1b1affected · git
    • 102740bd9436a3a6ba129af3a48271d794009fa5 and later · before 33373e1f378a501bc51aa73312f74295c84e3101affected · git
    • 102740bd9436a3a6ba129af3a48271d794009fa5 and later · before e2d3b7bab3748c811dc5750ce9a8d62bc7f90ed7affected · git
    • 102740bd9436a3a6ba129af3a48271d794009fa5 and later · before 4a76953c3ed043797e81529b9395e9ca6f4c7609affected · git
    • 102740bd9436a3a6ba129af3a48271d794009fa5 and later · before 1387f252a242a51bfbb6eace29c8f8db21b457daaffected · git
    • 102740bd9436a3a6ba129af3a48271d794009fa5 and later · before 10753da2d659dd425a6e620f47f86852d604f67faffected · git
    • 102740bd9436a3a6ba129af3a48271d794009fa5 and later · before 3fa6fb5d771c992ebedbfa7331c6bcc6f33f89b7affected · git
    • 102740bd9436a3a6ba129af3a48271d794009fa5 and later · before 27db54b90bcc7c37867fe664107fa25ea6a116e4affected · git
    • before 4.15not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-74379Aug 15, 2026 · dax/kmem: account for partial discontiguous resource upon removal
    0Monitor
  • ← EarlierCVE-2026-74380Aug 15, 2026 · gpu: host1x: Fix iommu_map_sgtable() return value check
    35Monitor
  • Later →CVE-2026-74384Aug 15, 2026 · nvme-multipath: fix flex array size in struct nvme_ns_head
    39Monitor

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 Linux10753da2d659dd425a6e620f47f86852d604f67fVendor (CNA)
Linux Linux1387f252a242a51bfbb6eace29c8f8db21b457daVendor (CNA)
Linux Linux27db54b90bcc7c37867fe664107fa25ea6a116e4Vendor (CNA)
Linux Linux33373e1f378a501bc51aa73312f74295c84e3101Vendor (CNA)
Linux Linux3fa6fb5d771c992ebedbfa7331c6bcc6f33f89b7Vendor (CNA)
Linux Linux4a76953c3ed043797e81529b9395e9ca6f4c7609Vendor (CNA)
Linux Linuxa018f208ab7512380bd4cf670064d48cba00a1b1Vendor (CNA)
Linux Linuxe2d3b7bab3748c811dc5750ce9a8d62bc7f90ed7Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records