CVE-2026-31563

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

net: macb: Use dev_consume_skb_any() to free TX SKBs

The napi_consume_skb() function is not intended to be called in an IRQ disabled context. However, after commit 6bc8a5098bf4 ("net: macb: Fix tx_ptr_lock locking"), the freeing of TX SKBs is performed with IRQs disabled. To resolve the following call trace, use dev_consume_skb_any() for freeing TX SKBs: WARNING: kernel/softirq.c:430 at __local_bh_enable_ip+0x174/0x188, CPU#0: ksoftirqd/0/15 Modules linked in: CPU: 0 UID: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 7.0.0-rc4-next-20260319-yocto-standard-dirty #37 PREEMPT Hardware name: ZynqMP ZCU102 Rev1.1 (DT) pstate: 200000c5 (nzCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __local_bh_enable_ip+0x174/0x188 lr : local_bh_enable+0x24/0x38 sp : ffff800082b3bb10 x29: ffff800082b3bb10 x28: ffff0008031f3c00 x27: 000000000011ede0 x26: ffff000800a7ff00 x25: ffff800083937ce8 x24: 0000000000017a80 x23: ffff000803243a78 x22: 0000000000000040 x21: 0000000000000000 x20: ffff000800394c80 x19: 0000000000000200 x18: 0000000000000001 x17: 0000000000000001 x16: ffff000803240000 x15: 0000000000000000 x14: ffffffffffffffff x13: 0000000000000028 x12: ffff000800395650 x11: ffff8000821d1528 x10: ffff800081c2bc08 x9 : ffff800081c1e258 x8 : 0000000100000301 x7 : ffff8000810426ec x6 : 0000000000000000 x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000 x2 : 0000000000000008 x1 : 0000000000000200 x0 : ffff8000810428dc Call trace: __local_bh_enable_ip+0x174/0x188 (P) local_bh_enable+0x24/0x38 skb_attempt_defer_free+0x190/0x1d8 napi_consume_skb+0x58/0x108 macb_tx_poll+0x1a4/0x558 __napi_poll+0x50/0x198 net_rx_action+0x1f4/0x3d8 handle_softirqs+0x16c/0x560 run_ksoftirqd+0x44/0x80 smpboot_thread_fn+0x1d8/0x338 kthread+0x120/0x150 ret_from_fork+0x10/0x20 irq event stamp: 29751 hardirqs last enabled at (29750): [] _raw_spin_unlock_irqrestore+0x44/0x88 hardirqs last disabled at (29751): [] _raw_spin_lock_irqsave+0x38/0x98 softirqs last enabled at (29150): [] handle_softirqs+0x504/0x560 softirqs last disabled at (29153): [] run_ksoftirqd+0x44/0x80

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

April 24, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

net: macb: Use dev_consume_skb_any() to free TX SKBs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f4bc91398b579730284328322365afa77a9d568f
generic

net: macb: Use dev_consume_skb_any() to free TX SKBs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ca4d05afb4683d685bb2c6fccae4386c478f524a
generic

net: macb: Use dev_consume_skb_any() to free TX SKBs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/984350b37372f79f71d4f0a5264c640e40daf9ce
generic

net: macb: Use dev_consume_skb_any() to free TX SKBs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92e7081f0c79d9073087e54bab745bb184192c2e
generic

net: macb: Use dev_consume_skb_any() to free TX SKBs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78c8b090a3d5c1689dc989861b0163180db2b3f8
generic

net: macb: Use dev_consume_skb_any() to free TX SKBs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/647b8a2fe474474704110db6bd07f7a139e621eb

Vendor Advisories for CVE-2026-31563(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.168—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (121 versions)6.19.11-1—

Additional Vendor Advisories

(13)

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 / 69× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 254 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31563?
CVE-2026-31563 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: net: macb: Use devconsumeskb_any() to free TX SKBs The napiconsumeskb() function is not intended to be called in an IRQ disabled context. However, after commit 6bc8a5098bf4 ("net: macb: Fix txptrlock locking"), the freeing of TX…
When was CVE-2026-31563 disclosed?
CVE-2026-31563 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31563 actively exploited?
CVE-2026-31563 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 59.0% of all scored CVEs.
What is the CVSS score of CVE-2026-31563?
CVE-2026-31563 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31563?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31563, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-31563?

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

Start Free Scan →Browse All CVEs