CVE-2026-22976

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2026-01-21. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-3689 (ENISA EUVD) · GHSA-f4fv-h3x5-8339 (GitHub Security Advisories)Source: ENISA EUVD

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_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset

qfq_class->leaf_qdisc->q.qlen > 0 does not imply that the class itself is active.

Two qfq_class objects may point to the same leaf_qdisc. This happens when:

  • one QFQ qdisc is attached to the dev as the root qdisc, and
  • another QFQ qdisc is temporarily referenced (e.g., via qdisc_get()
/ qdisc_put()) and is pending to be destroyed, as in function tc_new_tfilter.

When packets are enqueued through the root QFQ qdisc, the shared leaf_qdisc->q.qlen increases. At the same time, the second QFQ qdisc triggers qdisc_put and qdisc_destroy: the qdisc enters qfq_reset() with its own q->q.qlen == 0, but its class's leaf qdisc->q.qlen > 0. Therefore, the qfq_reset would wrongly deactivate an inactive aggregate and trigger a null-deref in qfq_deactivate_agg:

[ 0.903172] BUG: kernel NULL pointer dereference, address: 0000000000000000 [ 0.903571] #PF: supervisor write access in kernel mode [ 0.903860] #PF: error_code(0x0002) - not-present page [ 0.904177] PGD 10299b067 P4D 10299b067 PUD 10299c067 PMD 0 [ 0.904502] Oops: Oops: 0002 [#1] SMP NOPTI [ 0.904737] CPU: 0 UID: 0 PID: 135 Comm: exploit Not tainted 6.19.0-rc3+ #2 NONE [ 0.905157] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014 [ 0.905754] RIP: 0010:qfq_deactivate_agg (include/linux/list.h:992 (discriminator 2) include/linux/list.h:1006 (discriminator 2) net/sched/sch_qfq.c:1367 (discriminator 2) net/sched/sch_qfq.c:1393 (discriminator 2)) [ 0.906046] Code: 0f 84 4d 01 00 00 48 89 70 18 8b 4b 10 48 c7 c2 ff ff ff ff 48 8b 78 08 48 d3 e2 48 21 f2 48 2b 13 48 8b 30 48 d3 ea 8b 4b 18 0

Code starting with the faulting instruction =========================================== 0: 0f 84 4d 01 00 00 je 0x153 6: 48 89 70 18 mov %rsi,0x18(%rax) a: 8b 4b 10 mov 0x10(%rbx),%ecx d: 48 c7 c2 ff ff ff ff mov $0xffffffffffffffff,%rdx 14: 48 8b 78 08 mov 0x8(%rax),%rdi 18: 48 d3 e2 shl %cl,%rdx 1b: 48 21 f2 and %rsi,%rdx 1e: 48 2b 13 sub (%rbx),%rdx 21: 48 8b 30 mov (%rax),%rsi 24: 48 d3 ea shr %cl,%rdx 27: 8b 4b 18 mov 0x18(%rbx),%ecx ... [ 0.907095] RSP: 0018:ffffc900004a39a0 EFLAGS: 00010246 [ 0.907368] RAX: ffff8881043a0880 RBX: ffff888102953340 RCX: 0000000000000000 [ 0.907723] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 [ 0.908100] RBP: ffff888102952180 R08: 0000000000000000 R09: 0000000000000000 [ 0.908451] R10: ffff8881043a0000 R11: 0000000000000000 R12: ffff888102952000 [ 0.908804] R13: ffff888102952180 R14: ffff8881043a0ad8 R15: ffff8881043a0880 [ 0.909179] FS: 000000002a1a0380(0000) GS:ffff888196d8d000(0000) knlGS:0000000000000000 [ 0.909572] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 0.909857] CR2: 0000000000000000 CR3: 0000000102993002 CR4: 0000000000772ef0 [ 0.910247] PKRU: 55555554 [ 0.910391] Call Trace: [ 0.910527] [ 0.910638] qfq_reset_qdisc (net/sched/sch_qfq.c:357 net/sched/sch_qfq.c:1485) [ 0.910826] qdisc_reset (include/linux/skbuff.h:2195 include/linux/skbuff.h:2501 include/linux/skbuff.h:3424 include/linux/skbuff.h:3430 net/sched/sch_generic.c:1036) [ 0.911040] __qdisc_destroy (net/sched/sch_generic.c:1076) [ 0.911236] tc_new_tfilter (net/sched/cls_api.c:2447) [ 0.911447] rtnetlink_rcv_msg (net/core/rtnetlink.c:6958) [ 0.911663] ? __pfx_rtnetlink_rcv_msg (net/core/rtnetlink.c:6861) [ 0.911894] netlink_rcv_skb (net/netlink/af_netlink.c:2550) [ 0.912100] netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344) [ 0.912296] ? __alloc_skb (net/core/skbuff.c:706) [ 0.912484] netlink_sendmsg (net/netlink/af ---truncated---

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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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
7th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

January 21, 2026

Last Modified

October 19, 2026

Advisory Details (8)

Auto-updated Aug 8, 2026
Patch available.
Web page

SSA-253495

https://cert-portal.siemens.com/productcert/html/ssa-253495.html
Web page

net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6116a83ec167d3ab1390cded854d237481f41b63
Web page

net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51ffd447bc37bf1a5776b85523f51d2bc69977f6
Web page

net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/43497313d0da3e12b5cfcd97aa17bf48ee663f95
Web page

net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/11bf9134613f6c71fc0ff36c5d8d33856f6ae3bb
Web page

net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0809c4bc06c9c961222df29f2eccfd449304056f

Vendor Advisories for CVE-2026-22976(2)

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

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-10-19ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.17.0-1018.20~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1019.19~24.04.3+1) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1031.31) @ noble2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-10-19ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1102.106) @ jammy2026-10-19ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1030.30) @ noble2026-10-19ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1099.98) @ jammy2026-10-19ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1103.93) @ jammy2026-10-19ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1051.52~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1044.46) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-10-19ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1094.98) @ jammy2026-10-19ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-10-19ubuntu
linuxKernel @ 5.10.248 (fixes >=3.0.0)—osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (48 versions)
  • every version up to 5.10.249-1: fixed in 5.10.249-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.159-1~deb11u1 (14 versions)
  • every version up to 6.1.162-1~deb11u1: fixed in 6.1.162-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)
  • every version up to 6.1.162-1: fixed in 6.1.162-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)
  • every version up to 6.12.69-1: fixed in 6.12.69-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (97 versions)
  • every version up to 6.18.8-1: fixed in 6.18.8-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 42× 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 207 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 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-22976?
CVE-2026-22976 is a medium-severity vulnerability; its CVE record was published on January 21, 2026. In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset qfq_class->leaf_qdisc->q.qlen > 0 does not imply that the class itself is active. Two qfq_class objects may point to the same leaf_qdisc. This…
When was the CVE record for CVE-2026-22976 published?
The CVE record for CVE-2026-22976 was published on January 21, 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 19, 2026; the record at its source may have been updated since.
Is CVE-2026-22976 actively exploited?
CVE-2026-22976 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-22976?
CVE-2026-22976 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-22976?
A fix for CVE-2026-22976 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-22976 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-22976

Explore →

Is Your Infrastructure Affected by CVE-2026-22976?

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

Book a Demo →Browse All CVEs