CVE-2026-31494

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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)
EPSS
3.3%
KEV
Not listed

Published

April 22, 2026

Last Modified

July 14, 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 42× 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 159 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 July 14, 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 3.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31494?
CVE-2026-31494 has a CVSS v3 base score of 7.8 (NVD).
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

Explore the affected products and dependency analysis for 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