Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38637: net_sched: skbprio: Remove overly strict queue assertions

Noroxi assessment

Priority: Monitor (action score 22/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.32% (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 034b293bf17c124fec0f0e663f81203b00aa7a50, 1284733bab736e598341f1d3f3b94e2a322864a8, 1dcc144c322a8d526b791135604c0663f1af9d85; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.

Low priority for now. Upgrade to Linux Linux 034b293bf17c124fec0f0e663f81203b00aa7a50, 1284733bab736e598341f1d3f3b94e2a322864a8, 1dcc144c322a8d526b791135604c0663f1af9d85; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 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: skbprio: Remove overly strict queue assertions In the current implementation, skbprio enqueue/dequeue contains an assertion that fails under certain conditions when SKBPRIO is used as a child qdisc under TBF with specific parameters. The failure occurs because TBF sometimes peeks at packets in the child qdisc without actually dequeuing them when tokens are unavailable. This peek operation creates a discrepancy between the parent and child qdisc queue length counters. When TBF later receives a high-priority packet, SKBPRIO's queue length may show a different value than what's reflected in its internal priority queue tracking, triggering the assertion. The fix removes this overly strict assertions in SKBPRIO, they are not necessary at all.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 18, 2025
Updated
Jun 17, 2026
EPSS
0.3% · 26th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

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-2025-38637

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.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

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

  • debian debian linux11.0
  • linux linux kernel5.5 and later · before 5.10.236
  • linux linux kernel5.11 and later · before 5.15.180
  • linux linux kernel5.16 and later · before 6.1.134
  • linux linux kernel4.19 and later · before 5.4.292
  • linux linux kernel6.7 and later · before 6.12.23
  • linux linux kernel6.13 and later · before 6.13.11
  • linux linux kernel6.14 and later · before 6.14.2
  • linux linux kernel6.2 and later · before 6.6.87

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.19affected
    • aea5f654e6b78a0c976f7a25950155932c77a53f and later · before 7abc8318ce0712182bf0783dcfdd9a6a8331160eaffected · git
    • aea5f654e6b78a0c976f7a25950155932c77a53f and later · before 1284733bab736e598341f1d3f3b94e2a322864a8affected · git
    • aea5f654e6b78a0c976f7a25950155932c77a53f and later · before 32ee79682315e6d3c99947b3f38b078a09a66919affected · git
    • aea5f654e6b78a0c976f7a25950155932c77a53f and later · before 1dcc144c322a8d526b791135604c0663f1af9d85affected · git
    • aea5f654e6b78a0c976f7a25950155932c77a53f and later · before 864ca690ff135078d374bd565b9872f161c614bcaffected · git
    • aea5f654e6b78a0c976f7a25950155932c77a53f and later · before 2f35b7673a3aa3d09b3eb05811669622ebaa98caaffected · git
    • aea5f654e6b78a0c976f7a25950155932c77a53f and later · before 2286770b07cb5268c03d11274b8efd43dff0d380affected · git
    • aea5f654e6b78a0c976f7a25950155932c77a53f and later · before 034b293bf17c124fec0f0e663f81203b00aa7a50affected · git
    • aea5f654e6b78a0c976f7a25950155932c77a53f and later · before ce8fe975fd99b49c29c42e50f2441ba53112b2e8affected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.135-16.1.135-1
Debian:13linuxbefore 6.12.25-16.12.25-1

Same product

linux: all records

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-2025-38479Apr 18, 2025 · dmaengine: fsl-edma: free irq correctly in remove path
    31Monitor
  • ← EarlierCVE-2025-38575Apr 18, 2025 · ksmbd: use aead_request_free to match aead_request_alloc
    22Monitor
  • Later →CVE-2025-39728Apr 18, 2025 · clk: samsung: Fix UBSAN panic in samsung_clk_init()
    22Monitor

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 Linux034b293bf17c124fec0f0e663f81203b00aa7a50Vendor (CNA)
Linux Linux1284733bab736e598341f1d3f3b94e2a322864a8Vendor (CNA)
Linux Linux1dcc144c322a8d526b791135604c0663f1af9d85Vendor (CNA)
Linux Linux2286770b07cb5268c03d11274b8efd43dff0d380Vendor (CNA)
Linux Linux2f35b7673a3aa3d09b3eb05811669622ebaa98caVendor (CNA)
Linux Linux32ee79682315e6d3c99947b3f38b078a09a66919Vendor (CNA)
Linux Linux7abc8318ce0712182bf0783dcfdd9a6a8331160eVendor (CNA)
Linux Linux864ca690ff135078d374bd565b9872f161c614bcVendor (CNA)
Linux Linuxce8fe975fd99b49c29c42e50f2441ba53112b2e8Vendor (CNA)
azl3 kernel 6.6.85.1-4 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.92.2-1 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.135-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.

No history yet (it accumulates with the daily EPSS job).

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.

  • CVE-2026-31739378 days apartcrypto: tegra - Add missing CRYPTO_ALG_ASYNC
    35Monitor
  • CVE-2026-52952432 days apartiommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset
    35Monitor
  • CVE-2025-39803150 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()
    31Monitor
  • CVE-2026-31398350 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios
    31Monitor
  • CVE-2023-52621388 days apartbpf: Check rcu_read_lock_trace_held() before calling bpf map helpers
    31Monitor
  • CVE-2026-46117405 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()
    31Monitor

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

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-617 · Reachable Assertion

CVSS vector

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

nvd-primary

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

Show all references (10 more)

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

All records