CVE-2026-64547

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-27. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: 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: usb: net1080: validate packet_len before pad-byte access in rx_fixup

For an even packet_len, net1080_rx_fixup() reads the pad byte at skb->data[packet_len] before the skb->len != packet_len check further down, and packet_len is only bounded against NC_MAX_PACKET. A malicious NetChip 1080 device can send a short frame advertising a large even packet_len (e.g. 0x4000), so the pad-byte read lands past the end of the skb:

BUG: KASAN: slab-out-of-bounds in net1080_rx_fixup Read of size 1 at addr ffff8880106c83c6 by task ksoftirqd/0/14 ... net1080_rx_fixup (drivers/net/usb/net1080.c:384) usbnet_bh (drivers/net/usb/usbnet.c:1589) process_one_work (kernel/workqueue.c:3322) bh_worker (kernel/workqueue.c:3708) tasklet_action (kernel/softirq.c:965) handle_softirqs (kernel/softirq.c:622) ...

Reject the frame when packet_len >= skb->len before reading.

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

Published

July 27, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Jul 30, 2026
No patch confirmed yet.
generic

net: usb: net1080: validate packet_len before pad-byte access in rx_fixup - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: usb: net1080: validate packet_len before pad-byte access in rx_fixup - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: usb: net1080: validate packet_len before pad-byte access in rx_fixup - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: usb: net1080: validate packet_len before pad-byte access in rx_fixup - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: usb: net1080: validate packet_len before pad-byte access in rx_fixup - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: usb: net1080: validate packet_len before pad-byte access in rx_fixup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/685e92934f11d5e215dad58813e2f9955ac2f436
generic

net: usb: net1080: validate packet_len before pad-byte access in rx_fixup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4dc8484be3302d187274364820d3bef6c62bde32
generic

net: usb: net1080: validate packet_len before pad-byte access in rx_fixup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/03f384bc0cb8d4a1301d4f5b0baef2d980258383

Vendor Advisories for CVE-2026-64547(1)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (157 versions)7.1.5-1—

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 30× in last 7d / 152× 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 168 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64547?
CVE-2026-64547 is a high vulnerability published on July 27, 2026. In the Linux kernel, the following vulnerability has been resolved: net: usb: net1080: validate packetlen before pad-byte access in rxfixup For an even packetlen, net1080rx_fixup() reads the pad byte at skb->data[packetlen] before the skb->len != packetlen check further down, and packetlen is only…
When was CVE-2026-64547 disclosed?
CVE-2026-64547 was first published in the National Vulnerability Database on July 27, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64547 actively exploited?
CVE-2026-64547 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 80.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64547?
CVE-2026-64547 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-64547?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64547, 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-64547

Explore →

Is Your Infrastructure Affected by CVE-2026-64547?

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

Start Free Scan →Browse All CVEs