Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-37797: net_sched: hfsc: Fix a UAF vulnerability in class handling

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.22% (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 20d584a33e480ae80d105f43e0e7b56784da41b9, 28b09a067831f7317c3841812276022d6c940677, 39b9095dd3b55d9b2743df038c32138efa34a9de; 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 20d584a33e480ae80d105f43e0e7b56784da41b9, 28b09a067831f7317c3841812276022d6c940677, 39b9095dd3b55d9b2743df038c32138efa34a9de; 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: hfsc: Fix a UAF vulnerability in class handling This patch fixes a Use-After-Free vulnerability in the HFSC qdisc class handling. The issue occurs due to a time-of-check/time-of-use condition in hfsc_change_class() when working with certain child qdiscs like netem or codel. The vulnerability works as follows: 1. hfsc_change_class() checks if a class has packets (q.qlen != 0) 2. It then calls qdisc_peek_len(), which for certain qdiscs (e.g., codel, netem) might drop packets and empty the queue 3. The code continues assuming the queue is still non-empty, adding the class to vttree 4. This breaks HFSC scheduler assumptions that only non-empty classes are in vttree 5. Later, when the class is destroyed, this can lead to a Use-After-Free The fix adds a second queue length check after qdisc_peek_len() to verify the queue wasn't emptied.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 2, 2025
Updated
Aug 5, 2026
EPSS
0.2% · 13th 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.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

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

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.

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.237
  • linux linux kernel5.11 and later · before 5.15.181
  • linux linux kernel5.16 and later · before 6.1.136
  • linux linux kernel6.2 and later · before 6.6.89
  • linux linux kernel4.14.1 and later · before 5.4.293
  • linux linux kernel6.13 and later · before 6.14.5
  • linux linux kernel6.7 and later · before 6.12.26
  • linux linux kernel4.14
  • linux linux kernel6.15

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.14affected
    • 21f4d5cc25ec0e6e8eb8420dd2c399e6d2fc7d14 and later · before 28b09a067831f7317c3841812276022d6c940677affected · git
    • 21f4d5cc25ec0e6e8eb8420dd2c399e6d2fc7d14 and later · before 39b9095dd3b55d9b2743df038c32138efa34a9deaffected · git
    • 21f4d5cc25ec0e6e8eb8420dd2c399e6d2fc7d14 and later · before fcc8ede663569c704fb00a702973bd6c00373283affected · git
    • 21f4d5cc25ec0e6e8eb8420dd2c399e6d2fc7d14 and later · before 20d584a33e480ae80d105f43e0e7b56784da41b9affected · git
    • 21f4d5cc25ec0e6e8eb8420dd2c399e6d2fc7d14 and later · before 3aa852e3605000d5c47035c3fc3a986d14ccfa9faffected · git
    • 21f4d5cc25ec0e6e8eb8420dd2c399e6d2fc7d14 and later · before 86cd4641c713455a4f1c8e54c370c598c2b1cee0affected · git
    • 21f4d5cc25ec0e6e8eb8420dd2c399e6d2fc7d14 and later · before bb583c88d23b72d8d16453d24856c99bd93dadf5affected · git
    • 21f4d5cc25ec0e6e8eb8420dd2c399e6d2fc7d14 and later · before 3df275ef0a6ae181e8428a6589ef5d5231e58b5caffected · git
    • before 4.14not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-55.24.1.el10_06.12.0-55.24.1.el10_0
AlmaLinux:10kernel-docbefore 6.12.0-55.24.1.el10_06.12.0-55.24.1.el10_0
AlmaLinux:8bpftoolbefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.77.1.el8_104.18.0-553.77.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.77.1.rt7.418.el8_104.18.0-553.77.1.rt7.418.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.77.1.rt7.418.el8_104.18.0-553.77.1.rt7.418.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.77.1.rt7.418.el8_104.18.0-553.77.1.rt7.418.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.77.1.rt7.418.el8_104.18.0-553.77.1.rt7.418.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.77.1.rt7.418.el8_104.18.0-553.77.1.rt7.418.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.77.1.rt7.418.el8_104.18.0-553.77.1.rt7.418.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.77.1.rt7.418.el8_104.18.0-553.77.1.rt7.418.el8_10

+96

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-2022-49892May 1, 2025 · ftrace: Fix use-after-free for dynamic ftrace_ops
    31Monitor
  • ← EarlierCVE-2022-49905May 1, 2025 · net/smc: Fix possible leaked pernet namespace in smc_init()
    22Monitor
  • Later →CVE-2022-49932May 2, 2025 · KVM: VMX: Do _all_ initialization before exposing /dev/kvm to userspace
    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 Linux20d584a33e480ae80d105f43e0e7b56784da41b9Vendor (CNA)
Linux Linux28b09a067831f7317c3841812276022d6c940677Vendor (CNA)
Linux Linux39b9095dd3b55d9b2743df038c32138efa34a9deVendor (CNA)
Linux Linux3aa852e3605000d5c47035c3fc3a986d14ccfa9fVendor (CNA)
Linux Linux3df275ef0a6ae181e8428a6589ef5d5231e58b5cVendor (CNA)
Linux Linux86cd4641c713455a4f1c8e54c370c598c2b1cee0Vendor (CNA)
Linux Linuxbb583c88d23b72d8d16453d24856c99bd93dadf5Vendor (CNA)
Linux Linuxfcc8ede663569c704fb00a702973bd6c00373283Vendor (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)
almalinux:kernel5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-abi-stablelists6.12.0-55.24.1.el10_0 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-doc6.12.0-55.24.1.el10_0 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.137-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)

+19

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.

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

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

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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