CVE-2026-31494

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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 the current queue number for stats

There's a potential mismatch between the memory reserved for statistics and the amount of memory written.

gem_get_sset_count() correctly computes the number of stats based on the active queues, whereas gem_get_ethtool_stats() indiscriminately copies data using the maximum number of queues, and in the case the number of active queues is less than MACB_MAX_QUEUES, this results in a OOB write as observed in the KASAN splat.

================================================================== BUG: KASAN: vmalloc-out-of-bounds in gem_get_ethtool_stats+0x54/0x78 [macb] Write of size 760 at addr ffff80008080b000 by task ethtool/1027

CPU: [...] Tainted: [E]=UNSIGNED_MODULE Hardware name: raspberrypi rpi/rpi, BIOS 2025.10 10/01/2025 Call trace: show_stack+0x20/0x38 (C) dump_stack_lvl+0x80/0xf8 print_report+0x384/0x5e0 kasan_report+0xa0/0xf0 kasan_check_range+0xe8/0x190 __asan_memcpy+0x54/0x98 gem_get_ethtool_stats+0x54/0x78 [macb 926c13f3af83b0c6fe64badb21ec87d5e93fcf65] dev_ethtool+0x1220/0x38c0 dev_ioctl+0x4ac/0xca8 sock_do_ioctl+0x170/0x1d8 sock_ioctl+0x484/0x5d8 __arm64_sys_ioctl+0x12c/0x1b8 invoke_syscall+0xd4/0x258 el0_svc_common.constprop.0+0xb4/0x240 do_el0_svc+0x48/0x68 el0_svc+0x40/0xf8 el0t_64_sync_handler+0xa0/0xe8 el0t_64_sync+0x1b0/0x1b8

The buggy address belongs to a 1-page vmalloc region starting at 0xffff80008080b000 allocated at dev_ethtool+0x11f0/0x38c0 The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff00000a333000 pfn:0xa333 flags: 0x7fffc000000000(node=0|zone=0|lastcpupid=0x1ffff) raw: 007fffc000000000 0000000000000000 dead000000000122 0000000000000000 raw: ffff00000a333000 0000000000000000 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff80008080b080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff80008080b100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff80008080b180: 00 00 00 00 00 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ^ ffff80008080b200: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ffff80008080b280: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ==================================================================

Fix it by making sure the copied size only considers the active number of queues.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 22, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

net: macb: use the current queue number for stats - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: macb: use the current queue number for stats - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9d74d10e4e26672e139a8bcf8bf95957bf2d160f
generic

net: macb: use the current queue number for stats - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9738be665544281aa624842812c2fbfed6f88226
generic

net: macb: use the current queue number for stats - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9596759a84e1dbf2670518d85e969208960041f9
generic

net: macb: use the current queue number for stats - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95246341945163ad9a250a87ca5bd1c1252777ae
generic

net: macb: use the current queue number for stats - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ff87da099210856cbfe2f2f7f52ddfa57af4f0c
generic

net: macb: use the current queue number for stats - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72d96e4e24bbefdcfbc68bdb9341a05d8f5cb6e5
generic

net: macb: use the current queue number for stats - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/240c5302eed83e34e98db18f6795ee5f40814024

Vendor Advisories for CVE-2026-31494(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 @ 5.10.253—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 rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
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—

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 6× in last 7d / 61× 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 240 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31494?
CVE-2026-31494 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: net: macb: use the current queue number for stats There's a potential mismatch between the memory reserved for statistics and the amount of memory written. gemgetsset_count() correctly computes the number of stats based on the…
When was CVE-2026-31494 disclosed?
CVE-2026-31494 was first published in the National Vulnerability Database on April 22, 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-31494 actively exploited?
CVE-2026-31494 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-31494?
CVE-2026-31494 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31494?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31494, 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-31494

Explore →

Is Your Infrastructure Affected by CVE-2026-31494?

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

Start Free Scan →Browse All CVEs