CVE-2026-64012

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (11th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 5 sources updated this week
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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] [ 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.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
The EG Score, 5.5 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 19, 2026

Last Modified

October 13, 2026

Advisory Details (8)

Auto-updated Oct 13, 2026
Patch available.
Web page

net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e5ea51e5f3fbba41d50cd84a530f33bc1c8f4d57
Web page

net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e125f5980b730c67c92a30cf150ec8c3d6777318
Web page

net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dbc560858da8b77dd9e4ef0cd93d421e0e4d7e0e
Web page

net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9ad3288632c859cf84183199832d822e7a70bdae
Web page

net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/84bfbfc0c48731bcce74cdf4f9c497547ec525e0
Web page

net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6c153d97c100f5b282c424101d8ff63122306997
Web page

net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1e70274d3b81de28973bcdbce40a512bcb181ff9
Web page

net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b9bc71153b01dbde8045b9edede4240f4f5520e

Vendor Advisories for CVE-2026-64012(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(19)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)
  • every version up to 5.10.259-1: fixed in 5.10.259-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions)
  • every version up to 7.0.12-1: fixed in 7.0.12-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(19)

Data Freshness Timeline

(refreshed 15× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 126 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 27 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-13 14:08 UTCEG score recomputeFirst assessed: 5.5 MEDIUM
  3. 2026-10-13 14:08 UTCVendor advisory
  4. 2026-10-13 14:08 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  5. 2026-10-13 14:04 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  6. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-12 15:48 UTCEG score recompute
  8. 2026-10-11 19:33 UTCEG score recompute
  9. 2026-10-11 16:48 UTCEG score recompute
  10. 2026-10-11 14:09 UTCEG score recompute
  11. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-10-01 08:46 UTCEG score recompute
  22. 2026-10-01 08:46 UTCVendor advisory
  23. 2026-10-01 08:46 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
Show 74 more
  1. 2026-09-28 07:24 UTCVendor advisory
  2. 2026-09-28 07:24 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  3. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  5. 2026-09-23 02:02 UTCVendor advisory
  6. 2026-09-23 02:02 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  7. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-09-16 12:59 UTCVendor advisory
  11. 2026-09-16 12:59 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  12. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-09-11 18:47 UTCVendor advisory
  14. 2026-09-11 18:47 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  15. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-09-05 09:58 UTCVendor advisory
  22. 2026-09-05 09:58 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  23. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  26. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  27. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  28. 2026-08-30 02:52 UTCVendor advisory
  29. 2026-08-30 02:52 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  30. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  31. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  32. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  33. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  34. 2026-08-25 18:47 UTCVendor advisory
  35. 2026-08-25 18:47 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  36. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  37. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  38. 2026-08-22 20:25 UTCVendor advisory
  39. 2026-08-22 20:25 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  40. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  41. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  42. 2026-08-19 23:02 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  43. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  44. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  45. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  46. 2026-08-16 23:56 UTCVendor advisory
  47. 2026-08-16 23:56 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  48. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  49. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  50. 2026-08-14 02:33 UTCVendor advisory
  51. 2026-08-14 02:33 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  52. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  53. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  54. 2026-08-11 05:12 UTCVendor advisory
  55. 2026-08-11 05:12 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  56. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  57. 2026-08-09 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  58. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  59. 2026-08-08 07:50 UTCVendor advisory
  60. 2026-08-08 07:50 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  61. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  62. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  63. 2026-08-05 10:28 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  64. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  65. 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  66. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  67. 2026-08-02 12:52 UTCVendor advisory
  68. 2026-08-02 12:52 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3
  69. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  70. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  71. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  72. 2026-07-30 15:29 UTCEG score recompute
  73. 2026-07-30 15:29 UTCVendor advisory
  74. 2026-07-30 15:29 UTCGHSA enrichmentGHSA-r9v4-xqjf-v9m3

Frequently asked(5)

What is CVE-2026-64012?
CVE-2026-64012 is a medium-severity vulnerability; its CVE record was published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: net/sched: schsfb: Replace direct dequeue call with peek and qdiscdequeue_peeked When sfb has children (eg qfq qdisc) whose peek() callback is qdiscpeekdequeued(), we could get a kernel panic. When the parent of such qdiscs (eg…
When was the CVE record for CVE-2026-64012 published?
The CVE record for CVE-2026-64012 was published on July 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
Is CVE-2026-64012 actively exploited?
CVE-2026-64012 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64012?
CVE-2026-64012 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64012?
A fix for CVE-2026-64012 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64012 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64012

Explore →

Is Your Infrastructure Affected by CVE-2026-64012?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.