Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-90072: net/sched: sfq: clamp quantum to avoid signed overflow soft lockup

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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 2017c355a5a1af77736cd1739fe922f69b5652dc, 6581a82bf08ba5d4e2a6d4e3080df43315b296c4, 816e90057ab1879562a5b7cc688e35bb9027ae97.

Low priority for now. Upgrade to Linux Linux 2017c355a5a1af77736cd1739fe922f69b5652dc, 6581a82bf08ba5d4e2a6d4e3080df43315b296c4, 816e90057ab1879562a5b7cc688e35bb9027ae97 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: sfq: clamp quantum to avoid signed overflow soft lockup sfq_init() sets q->quantum = psched_mtu(qdisc_dev(sch)) (unsigned). A device with a huge MTU (e.g. dummy with max_mtu == 0 accepting MTU 2147483634) makes psched_mtu() return 0x80000000, so slot->allot = INT_MIN and INT_MIN + INT_MIN toggles between INT_MIN and 0 forever, spinning sfq_dequeue() under the qdisc lock. Clamp the quantum to [256, 1 << 20] so the refill loop terminates. The lower bound also covers q->quantum == 0 (psched_mtu() returning 0), which spins sfq_dequeue() identically. sfq_change() already rejects a negative quantum, so only the init path was exposed. Conditions to recreate the bug: a device whose MTU (plus hard_header_len) wraps psched_mtu() into the sign bit (e.g. a dummy device with max_mtu == 0 accepting MTU 2147483634). Requires CAP_NET_ADMIN in a user namespace.

—No exploit Fix available
Published
Sep 17, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 12th 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.2%

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

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.

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

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 86799499585af06a9431c9e7782658667bd62650affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2017c355a5a1af77736cd1739fe922f69b5652dcaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6581a82bf08ba5d4e2a6d4e3080df43315b296c4affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 9d782c662879c3adaaca30e05c36910ad11b9e54affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before d72dbdfaeb5b9b8d884e0e036c3442754379ef74affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before aeb8196ecb95146e3410f635628e6cd47352b3e5affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before da16c31517cd2c06bb2c78c73e91ae192c01c426affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 816e90057ab1879562a5b7cc688e35bb9027ae97affected · git
    • before 2.6.12not 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.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

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-90070Sep 17, 2026 · tpm: st33zp24: Return zero on status read failure
    0Monitor
  • ← EarlierCVE-2026-90071Sep 17, 2026 · net/sched: sch_teql: restore skb->dev on the slave failure path
    31Monitor
  • Later →CVE-2026-90073Sep 17, 2026 · net/sched: hhf: clamp quantum before hhf_change() to avoid overflow
    0Monitor

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 Linux2017c355a5a1af77736cd1739fe922f69b5652dcVendor (CNA)
Linux Linux6581a82bf08ba5d4e2a6d4e3080df43315b296c4Vendor (CNA)
Linux Linux816e90057ab1879562a5b7cc688e35bb9027ae97Vendor (CNA)
Linux Linux86799499585af06a9431c9e7782658667bd62650Vendor (CNA)
Linux Linux9d782c662879c3adaaca30e05c36910ad11b9e54Vendor (CNA)
Linux Linuxaeb8196ecb95146e3410f635628e6cd47352b3e5Vendor (CNA)
Linux Linuxd72dbdfaeb5b9b8d884e0e036c3442754379ef74Vendor (CNA)
Linux Linuxda16c31517cd2c06bb2c78c73e91ae192c01c426Vendor (CNA)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · 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.

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. Fix✗ → ✓

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

References

All records