CVE-2026-89902

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:

LoongArch: Avoid preempt count underflow without probe

LoongArch uses break 11 for the breakpoint placed after an instruction that Kprobes executes out of line. Since userspace can issue the same break instruction, do_bp() can reach kprobe_singlestep_handler() when there is no current probe.

The handler actually returns false in this case, but it first calls preempt_enable_no_resched(). The corresponding preempt_disable() is done by kprobe_breakpoint_handler() on a real Kprobe hit, so it has not run here. As a result, an ordinary userspace breakpoint (code 11) underflows the current task's preempt count.

This also makes in_interrupt() return true until the task schedules. One visible consequence is the socket cgroup attribution: cgroup_sk_alloc() treats the allocation as interrupt context and assigns the socket to the root cgroup. A socket opened from the SIGTRAP handler can then avoid a BPF_CGROUP_INET_SOCK_CREATE policy attached to the task's own cgroup.

Return as soon as kprobe_running() reports no active probe.

The same check has appeared in [PATCH v10 2/4] of the original LoongArch Kprobes series, but was dropped before the feature reached mainline.

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
6th
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

September 16, 2026

Advisory Details (5)

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

LoongArch: Avoid preempt count underflow without probe - kernel/git/stable/linux.git - Linux kernel stable tree

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

LoongArch: Avoid preempt count underflow without probe - kernel/git/stable/linux.git - Linux kernel stable tree

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

LoongArch: Avoid preempt count underflow without probe - kernel/git/stable/linux.git - Linux kernel stable tree

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

LoongArch: Avoid preempt count underflow without probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/76395109a051b53860faaec96522ef08ae9e8e27
generic

LoongArch: Avoid preempt count underflow without probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72ce4b24676e8b3b75376c4c559dd81c1ac52d5a

Vendor Advisories for CVE-2026-89902(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
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
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 38× in last 7d / 108× 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 108 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-89902?
CVE-2026-89902 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: LoongArch: Avoid preempt count underflow without probe LoongArch uses break 11 for the breakpoint placed after an instruction that Kprobes executes out of line. Since userspace can issue the same break instruction, dobp() can reach…
When was CVE-2026-89902 disclosed?
CVE-2026-89902 was first published on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89902 actively exploited?
CVE-2026-89902 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89902?
CVE-2026-89902 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-89902?
No fix for CVE-2026-89902 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-89902 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-89902

Explore →

Is Your Infrastructure Affected by CVE-2026-89902?

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