CVE-2026-46289

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-08. a secondary CVSS source baseline 9.8; sources differ by 0.0.

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

A fix is available — apply it.

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

lib/scatterlist: fix length calculations in extract_kvec_to_sg

Patch series "Fix bugs in extract_iter_to_sg()", v3.

Fix bugs in the kvec and user variants of extract_iter_to_sg. This series is growing due to useful remarks made by sashiko.dev.

The main bugs are:

  • The length for an sglist entry when extracting from
a kvec can exceed the number of bytes in the page. This is obviously not intended.
  • When extracting a user buffer the sglist is temporarily
used as a scratch buffer for extracted page pointers. If the sglist already contains some elements this scratch buffer could overlap with existing entries in the sglist.

The series adds test cases to the kunit_iov_iter test that demonstrate all of these bugs. Additionally, there is a memory leak fix for the test itself.

The bugs were orignally introduced into kernel v6.3 where the function lived in fs/netfs/iterator.c. It was later moved to lib/scatterlist.c in v6.5. Thus the actual fix is only marked for backports to v6.5+.

This patch (of 5):

When extracting from a kvec to a scatterlist, do not cross page boundaries. The required length was already calculated but not used as intended.

Adjust the copied length if the loop runs out of sglist entries without extracting everything.

While there, return immediately from extract_iter_to_sg if there are no sglist entries at all.

A subsequent commit will add kunit test cases that demonstrate that the patch is necessary.

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

Published

June 8, 2026

Last Modified

July 23, 2026

Advisory Details (5)

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

lib/scatterlist: fix length calculations in extract_kvec_to_sg - kernel/git/stable/linux.git - Linux kernel stable tree

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

lib/scatterlist: fix length calculations in extract_kvec_to_sg - kernel/git/stable/linux.git - Linux kernel stable tree

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

lib/scatterlist: fix length calculations in extract_kvec_to_sg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8fbba6829057979149d1b37d65690c037f3ddf4d
generic

lib/scatterlist: fix length calculations in extract_kvec_to_sg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f17500e86d730c76db638bb3ae52f9b5e496c76
generic

lib/scatterlist: fix length calculations in extract_kvec_to_sg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/07b7d66e65d9cfe6b9c2c34aa22cfcaac37a5c45

Vendor Advisories for CVE-2026-46289(2)

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

Patch Availability(17)

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(18)

Data Freshness Timeline

(refreshed 22× in last 7d / 164× 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 289 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46289?
CVE-2026-46289 is a critical vulnerability published on June 8, 2026. In the Linux kernel, the following vulnerability has been resolved: lib/scatterlist: fix length calculations in extractkvecto_sg Patch series "Fix bugs in extractiterto_sg()", v3. Fix bugs in the kvec and user variants of extractiterto_sg. This series is growing due to useful remarks made by…
When was CVE-2026-46289 disclosed?
CVE-2026-46289 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46289 actively exploited?
CVE-2026-46289 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 62.8% of all scored CVEs.
What is the CVSS score of CVE-2026-46289?
CVE-2026-46289 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-46289?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46289, 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-46289

Explore →

Is Your Infrastructure Affected by CVE-2026-46289?

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