CVE-2026-90013

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

tracing: Take trace_array reference when opening options file

The options files do not take the trace_array reference for the options they represent. This could cause a use-after-free kernel crash if one of these files is opened by one task and another task removes the instance that the option is for. Because it doesn't take a reference upon opening, it will not stop the removal which will free the options descriptor that is being used.

As the options are somewhat dynamic in their creation at boot up, each file represents a flag in the trace_array. The trace_array has an array of indexes to represent each of these flags that is stored in the trace_flags_index array. The address of the index array element is used to pass to the inode->i_private pointer. Then that element is read which holds the index (which represents the flag) and then the index is used to calculate the trace_array descriptor from its trace_flags_index array.

One issue is that the index element can not be referenced until the trace_array's reference is taken. To handle this, create a new helper function called: trace_array_options_get() that will iterate all the existing trace_arrays in the ftrace_trace_arrays list (under the trace_types_lock), and compare the passed in address of the index element with the entire array of the trace_array's trace_flags_index array. If it matches, then up the corresponding trace_array's reference and return.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 16, 2026

Last Modified

October 3, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

tracing: Take trace_array reference when opening options file - kernel/git/stable/linux.git - Linux kernel stable tree

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

tracing: Take trace_array reference when opening options file - kernel/git/stable/linux.git - Linux kernel stable tree

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

tracing: Take trace_array reference when opening options file - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5

Vendor Advisories for CVE-2026-90013(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (183 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-90013?
CVE-2026-90013 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: tracing: Take trace_array reference when opening options file The options files do not take the trace_array reference for the options they represent. This could cause a use-after-free kernel crash if one of these files is opened by…
When was CVE-2026-90013 disclosed?
CVE-2026-90013 was first published on September 16, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90013 actively exploited?
CVE-2026-90013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90013?
CVE-2026-90013 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90013?
No fix for CVE-2026-90013 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90013 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-90013

Explore →

Is Your Infrastructure Affected by CVE-2026-90013?

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