CVE-2026-63926

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
8.4EG
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.4Exploit: None knownExposed: 0

A fix is available — apply it.

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

bpf: sockmap: fix tail fragment offset in bpf_msg_push_data

When bpf_msg_push_data() inserts data in the middle of a scatterlist entry, it splits the original entry into a left fragment and a right fragment.

The right fragment offset is page-local, but the code advances it with start, which is the message-global insertion point. For inserts into a non-first SG entry, this over-advances the offset and leaves the split layout inconsistent.

Advance the right fragment offset by the fragment-local delta, start - offset, which matches the length removed from the front of the original entry.

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

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

bpf: sockmap: fix tail fragment offset in bpf_msg_push_data - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: sockmap: fix tail fragment offset in bpf_msg_push_data - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: sockmap: fix tail fragment offset in bpf_msg_push_data - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: sockmap: fix tail fragment offset in bpf_msg_push_data - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: sockmap: fix tail fragment offset in bpf_msg_push_data - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96b72672ce849a1402730238e64d9b20bf06a96d
generic

bpf: sockmap: fix tail fragment offset in bpf_msg_push_data - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/63f64a510c7917658ddf4d073ece73914ee25346
generic

bpf: sockmap: fix tail fragment offset in bpf_msg_push_data - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5e19028667963fb371ebb00cecc2a473ef92056b
generic

bpf: sockmap: fix tail fragment offset in bpf_msg_push_data - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3075c21d2d76c0067f4a382765b43d6cc10470f1

Vendor Advisories for CVE-2026-63926(1)

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

Patch Availability(5)

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
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 29× in last 7d / 161× 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 211 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63926?
CVE-2026-63926 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: sockmap: fix tail fragment offset in bpfmsgpush_data When bpfmsgpush_data() inserts data in the middle of a scatterlist entry, it splits the original entry into a left fragment and a right fragment. The right fragment offset…
When was CVE-2026-63926 disclosed?
CVE-2026-63926 was first published in the National Vulnerability Database on July 19, 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-63926 actively exploited?
CVE-2026-63926 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 91.9% of all scored CVEs.
What is the CVSS score of CVE-2026-63926?
CVE-2026-63926 has a CVSS v4.0 base score of 8.4 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63926?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63926, 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-63926

Explore →

Is Your Infrastructure Affected by CVE-2026-63926?

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