Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64012: net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked

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.12% (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 1b9bc71153b01dbde8045b9edede4240f4f5520e, 1e70274d3b81de28973bcdbce40a512bcb181ff9, 6c153d97c100f5b282c424101d8ff63122306997.

Low priority for now. Upgrade to Linux Linux 1b9bc71153b01dbde8045b9edede4240f4f5520e, 1e70274d3b81de28973bcdbce40a512bcb181ff9, 6c153d97c100f5b282c424101d8ff63122306997 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: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked When sfb has children (eg qfq qdisc) whose peek() callback is qdisc_peek_dequeued(), we could get a kernel panic. When the parent of such qdiscs (eg illustrated in patch #3 as tbf) wants to retrieve an skb from its child (sfb in this case), it will do the following: 1a. do a peek() - and when sensing there's an skb the child can offer, then - the child in this case(sfb) calls its child's (qfq) peek. qfq does the right thing and will return the gso_skb queue packet. Note: if there wasnt a gso_skb entry then qfq will store it there. 1b. invoke a dequeue() on the child (sfb). And herein lies the problem. - sfb will call the child's dequeue() which will essentially just try to grab something of qfq's queue. [ 127.594489][ T453] KASAN: null-ptr-deref in range [0x0000000000000048-0x000000000000004f] [ 127.594741][ T453] CPU: 2 UID: 0 PID: 453 Comm: ping Not tainted 7.1.0-rc1-00035-gac961974495b-dirty #793 PREEMPT(full) [ 127.595059][ T453] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 [ 127.595254][ T453] RIP: 0010:qfq_dequeue+0x35c/0x1650 [sch_qfq] [ 127.595461][ T453] Code: 00 fc ff df 80 3c 02 00 0f 85 17 0e 00 00 4c 8d 73 48 48 89 9d b8 02 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f 85 76 0c 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b [ 127.596081][ T453] RSP: 0018:ffff88810e5af440 EFLAGS: 00010216 [ 127.596337][ T453] RAX: dffffc0000000000 RBX: 0000000000000000 RCX: dffffc0000000000 [ 127.596623][ T453] RDX: 0000000000000009 RSI: 0000001880000000 RDI: ffff888104fd82b0 [ 127.596917][ T453] RBP: ffff888104fd8000 R08: ffff888104fd8280 R09: 1ffff110211893a3 [ 127.597165][ T453] R10: 1ffff110211893a6 R11: 1ffff110211893a7 R12: 0000001880000000 [ 127.597404][ T453] R13: ffff888104fd82b8 R14: 0000000000000048 R15: 0000000040000000 [ 127.597644][ T453] FS: 00007fc380cbfc40(0000) GS:ffff88816f2a8000(0000) knlGS:0000000000000000 [ 127.597956][ T453] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 127.598160][ T453] CR2: 00005610aa9890a8 CR3: 000000010369e000 CR4: 0000000000750ef0 [ 127.598390][ T453] PKRU: 55555554 [ 127.598509][ T453] Call Trace: [ 127.598629][ T453] <TASK> [ 127.598718][ T453] ? mark_held_locks+0x40/0x70 [ 127.598890][ T453] ? srso_alias_return_thunk+0x5/0xfbef5 [ 127.599053][ T453] sfb_dequeue+0x88/0x4d0 [ 127.599174][ T453] ? ktime_get+0x137/0x230 [ 127.599328][ T453] ? srso_alias_return_thunk+0x5/0xfbef5 [ 127.599480][ T453] ? qdisc_peek_dequeued+0x7b/0x350 [sch_qfq] [ 127.599670][ T453] ? srso_alias_return_thunk+0x5/0xfbef5 [ 127.599831][ T453] tbf_dequeue+0x6b1/0x1098 [sch_tbf] [ 127.599988][ T453] __qdisc_run+0x169/0x1900 The right thing to do in #1b is to grab the skb off gso_skb queue. This patchset fixes that issue by changing #1b to use qdisc_dequeue_peeked() method instead.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jul 19, 2026
Updated
Oct 13, 2026
EPSS
0.1% · 2th 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.1%

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

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

Affected versions

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

  • linux linux kernel2.6.39 and later · before 5.10.259
  • linux linux kernel5.11 and later · before 5.15.210
  • linux linux kernel5.16 and later · before 6.1.176
  • linux linux kernel6.2 and later · before 6.6.143
  • linux linux kernel6.7 and later · before 6.12.93
  • linux linux kernel6.13 and later · before 6.18.35
  • linux linux kernel6.19 and later · before 7.0.12
  • linux linux kernel7.1

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.39affected
    • e13e02a3c68d899169c78d9a18689bd73491d59a and later · before e5ea51e5f3fbba41d50cd84a530f33bc1c8f4d57affected · git
    • e13e02a3c68d899169c78d9a18689bd73491d59a and later · before 1e70274d3b81de28973bcdbce40a512bcb181ff9affected · git
    • e13e02a3c68d899169c78d9a18689bd73491d59a and later · before e125f5980b730c67c92a30cf150ec8c3d6777318affected · git
    • e13e02a3c68d899169c78d9a18689bd73491d59a and later · before 6c153d97c100f5b282c424101d8ff63122306997affected · git
    • e13e02a3c68d899169c78d9a18689bd73491d59a and later · before 84bfbfc0c48731bcce74cdf4f9c497547ec525e0affected · git
    • e13e02a3c68d899169c78d9a18689bd73491d59a and later · before dbc560858da8b77dd9e4ef0cd93d421e0e4d7e0eaffected · git
    • e13e02a3c68d899169c78d9a18689bd73491d59a and later · before 9ad3288632c859cf84183199832d822e7a70bdaeaffected · git
    • e13e02a3c68d899169c78d9a18689bd73491d59a and later · before 1b9bc71153b01dbde8045b9edede4240f4f5520eaffected · git
    • before 2.6.39not 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.176-16.1.176-1
Debian:13linuxbefore 6.12.94-16.12.94-1
Debian:14linuxbefore 7.0.12-17.0.12-1
openSUSE:Leap 16.0dtb-aarch64before 6.12.0-160000.40.16.12.0-160000.40.1
openSUSE:Leap 16.0kernel-64kbbefore 6.12.0-160000.40.16.12.0-160000.40.1
openSUSE:Leap 16.0kernel-azurebefore 6.12.0-160000.40.16.12.0-160000.40.1
openSUSE:Leap 16.0kernel-defaultbefore 6.12.0-160000.40.16.12.0-160000.40.1
openSUSE:Leap 16.0kernel-default-basebefore 6.12.0-160000.40.1.160000.2.296.12.0-160000.40.1.160000.2.29
openSUSE:Leap 16.0kernel-docsbefore 6.12.0-160000.40.16.12.0-160000.40.1
openSUSE:Leap 16.0kernel-kvmsmallbefore 6.12.0-160000.40.16.12.0-160000.40.1
openSUSE:Leap 16.0kernel-obs-buildbefore 6.12.0-160000.40.16.12.0-160000.40.1
openSUSE:Leap 16.0kernel-obs-qabefore 6.12.0-160000.40.16.12.0-160000.40.1
openSUSE:Leap 16.0kernel-rtbefore 6.12.0-160000.40.16.12.0-160000.40.1
openSUSE:Leap 16.0kernel-sourcebefore 6.12.0-160000.40.16.12.0-160000.40.1
openSUSE:Leap 16.0kernel-symsbefore 6.12.0-160000.40.16.12.0-160000.40.1
openSUSE:Leap 16.0kernel-zfcpdumpbefore 6.12.0-160000.40.16.12.0-160000.40.1
SUSE:Linux Enterprise Live Patching 12 SP5kernel-defaultbefore 4.12.14-122.336.14.12.14-122.336.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_89before 1-8.3.11-8.3.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-sourcebefore 4.12.14-122.336.14.12.14-122.336.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-symsbefore 4.12.14-122.336.14.12.14-122.336.1

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-2026-64010Jul 19, 2026 · nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc()
    35Monitor
  • ← EarlierCVE-2026-64011Jul 19, 2026 · nfc: llcp: Fix use-after-free in llcp_sock_release()
    31Monitor
  • Later →CVE-2026-64013Jul 19, 2026 · ACPI: button: Fix ACPI GPE handler leak during removal
    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 Linux1b9bc71153b01dbde8045b9edede4240f4f5520eVendor (CNA)
Linux Linux1e70274d3b81de28973bcdbce40a512bcb181ff9Vendor (CNA)
Linux Linux6c153d97c100f5b282c424101d8ff63122306997Vendor (CNA)
Linux Linux84bfbfc0c48731bcce74cdf4f9c497547ec525e0Vendor (CNA)
Linux Linux9ad3288632c859cf84183199832d822e7a70bdaeVendor (CNA)
Linux Linuxdbc560858da8b77dd9e4ef0cd93d421e0e4d7e0eVendor (CNA)
Linux Linuxe125f5980b730c67c92a30cf150ec8c3d6777318Vendor (CNA)
Linux Linuxe5ea51e5f3fbba41d50cd84a530f33bc1c8f4d57Vendor (CNA)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.12.0-160000.40.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-64kb6.12.0-160000.40.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-azure6.12.0-160000.40.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default6.12.0-160000.40.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default-base6.12.0-160000.40.1.160000.2.29 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-docs6.12.0-160000.40.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-kvmsmall6.12.0-160000.40.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-build6.12.0-160000.40.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-qa6.12.0-160000.40.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-rt6.12.0-160000.40.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-source6.12.0-160000.40.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-syms6.12.0-160000.40.1 · openSUSE:Leap 16.0Package registry (OSV)
suse:kernel-default4.12.14-122.336.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kernel-source4.12.14-122.336.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kernel-syms4.12.14-122.336.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_891-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package 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

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

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. CVSS— → 5.5
  2. Severity— → medium
  3. Fix✗ → ✓

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

References

All records